search

zephyriot / zephyr-issues

0 stars 0 forks source link

document IRQ handling internals #597

Closed nashif closed 7 years ago

nashif commented 8 years ago

Reported by Andrew Boie:

I sent out a draft document explaining how interrupts work on X86:

https://lists.zephyrproject.org/archives/list/devel@lists.zephyrproject.org/thread/3OCS4M326UERBVV3AXDJ6437QYOCN6NW/

Clean this up, convert to ReST format, and commit to our in-tree documentation. Document how sw_isr_table works on ARC/ARM/Nios II as well.

(Imported from Jira ZEP-634)

nashif commented 8 years ago

by Anas Nashif:

is this WIP and will be in 1.6? please Accept issue in this case. if not, please move to 1.7

nashif commented 8 years ago

by Mark Linkmeyer:

Andrew Boie , please see Anas' comment above and act on this story accordingly. Thanks.

nashif commented 8 years ago

by Andrew Boie:

Blocked by GH-1057 as that will involve a major revision to the IRQ implementation on ARC/ARM/NIOS

nashif commented 7 years ago

by Mark Linkmeyer:

Andrew Boie , any update on this? Thx.

nashif commented 7 years ago

by Andrew Boie:

This is on hold as a major rewrite of IRQs is in progress for non-x86 arches see GH-1057, GH-943

nashif commented 7 years ago

by Andrew Boie:

Mark Linkmeyer can we move this to 1.8? If I write this now, work on GH-1057 and GH-943 will make it already obsolete?

nashif commented 7 years ago

by Mark Linkmeyer:

Anas Nashif , please answer Andrew's question above about whether this can moved out to 1.8. I assume it can because it's a Medium priority, but I'd like you to make the call. Thx. Andrew Boie , I'm thinking there's no harm in leaving it as targeted for 1.7 since it's a nice-to-have anyhow. If you can get it done in time, then good. If not, then it will automatically get pushed to 1.8. However, if you're 100% sure at this time that it can't be done in time for 1.7, then I see no issue with pushing it out now to 1.8, if Anas agrees.

nashif commented 7 years ago

by Andrew Boie:

I can start working on it once I get those other two JIRAs done. Since this is documentation I think I could send it out even past the merge window closing.

nashif commented 7 years ago

by Anas Nashif:

Andrew Boie yes, this documentation story can be submitted after merge window. so that is ok

nashif commented 7 years ago

by Mark Linkmeyer:

Fixing incorrect priority

nashif commented 7 years ago

by David Kinder:

Andrew Boie I can handle transcoding an approved version of the document you want into ReST -- is there something you can send me (or attach to this Jira)?

nashif commented 7 years ago

by Andrew Boie:

Not working on this -- preempted by runtime.io MCUBoot support and planning memory management stories for 1.8. Suggest punting this to "Future" given how short-handed we are at the moment.

nashif commented 7 years ago

by Andrew Boie:

I have a draft up in a personal branch: https://github.com/andrewboie/zephyr/tree/irq-docs

However I'm blocked due to GH-2020.

nashif commented 7 years ago

by Mark Linkmeyer:

Andrew Boie and Anas Nashif , since this is a documentation story I assume it can still go into 1.8 this week, if it's ready. Will it be ready? It would be nice to get this one off our radar, if possible.

nashif commented 7 years ago

by Andrew Boie:

It's in review and I got some feedback from David, will have a new patch set up tomorrow.