-
Notifications
You must be signed in to change notification settings - Fork 6.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
drivers: interrupt_controller: changes in shared irq #66427
drivers: interrupt_controller: changes in shared irq #66427
Conversation
Hm... this is going to be affecting everyone using this. Could you send out an email on the Zephyr dev mailing list to inform the community about the change? (to give them a heads up) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Please add an entry in the migration guide for v3.6.0 detailing the needed changes to downstream code using this API.
Hello @henrikbrixandersen |
@dcpleung i sent email to Zephyr dev mailing list and inforamed about changes. |
You need to include the migration guide changes in this PR. |
Hello henrik, |
Yes, please add a description of the API change that may require end-users to update their out-of-tree code to this file: https://github.com/zephyrproject-rtos/zephyr/blob/main/doc/releases/migration-guide-3.6.rst There are a few examples there already. |
4f6484d
to
e548f56
Compare
e548f56
to
45ceb89
Compare
|
Hello @henrikbrixandersen could you please review changes |
45ceb89
to
5c8c874
Compare
@MaureenHelm Could you please review this PR? |
@nbalabak Please be patient. We will get to it. If in doubt, please see the contributor expectations (particularly the section on review escalation) here: https://docs.zephyrproject.org/latest/contribute/contributor_expectations.html#pr-review-escalation |
sure Thank you @henrikbrixandersen. |
doc/releases/migration-guide-3.6.rst
Outdated
* Interrupt_controller shared_irq public API function :c:func:`shared_irq_isr_register()` | ||
has changed. The parameter ``isr_func`` function pointer's parameter has modified. | ||
An addition irq_number parameter added to ``isr_func`` function pointer. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* Interrupt_controller shared_irq public API function :c:func:`shared_irq_isr_register()` | |
has changed. The parameter ``isr_func`` function pointer's parameter has modified. | |
An addition irq_number parameter added to ``isr_func`` function pointer. | |
* The function signature of the ``isr_t`` callback function passed to the ``shared_irq`` interrupt controller driver API via :c:func:`shared_irq_isr_register()` has changed. The callback now takes an additional `irq_number` parameter. Out-of-tree users of this API will need to be updated. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@henrikbrixandersen updated file as per your suggestion.
Updated the shared IRQ handler function in the shared interrupt controller drivers to include support for the 'irq_number' parameter. When a single driver manages multiple shared IRQs, it becomes challenging to determine which IRQ line is invoking the handler. Therefore, I've introduced an option to share the IRQ number to address this issue. Signed-off-by: Navinkumar Balabakthan <navinkumar.balabakthan@intel.com>
shared_irq api changes updated in migration-guide-3.6. Signed-off-by: Navinkumar Balabakthan <navinkumar.balabakthan@intel.com>
5c8c874
to
0190ffa
Compare
Updated the shared IRQ handler function in the shared interrupt controller drivers to include support for the 'irq_number' parameter. When a single driver manages multiple shared IRQs, it becomes challenging to determine which IRQ line is invoking the handler. Therefore, I've introduced an option to share the IRQ number to address this issue.
Signed-off-by: Navinkumar Balabakthan navinkumar.balabakthan@intel.com