Sharing itself is no problem: if your request an IRQ with XN_ISR_SHARED
set but the nucleus is not able to actually assign it to more than onedriver, the second request will simply fail. I see no need to deny thefirst request or even break the driver build.
Problematic is only the handling of
Dmitry Adamushko wrote:
Sharing itself is no problem: if your request an IRQ with XN_ISR_SHARED
set but the nucleus is not able to actually assign it to more than one
driver, the second request will simply fail. I see no need to deny the
first request or even break the driver build.
On 06/09/06, Jan Kiszka [EMAIL PROTECTED] wrote:
If such a driver (that requires EDGE_SHARED) is a part of the mainline, then we may use Kconfig features either (1) to make it selectable only when XENO_OPT_SHIRQ_EDGE is on or (2) select XENO_OPT_SHIRQ_EDGE automatically
when the driver has been
Dmitry Adamushko wrote:
On 06/09/06, Jan Kiszka [EMAIL PROTECTED] wrote:
See attached patch: XENO_OPT_SHIRQ would just be a menu-enabler without
any affect outside kconfig. You could enabled it and leave the rest off
(makes no sense of course) - as long as there are no edge-triggered
users
On 06/09/06, Jan Kiszka [EMAIL PROTECTED] wrote:
Dmitry Adamushko wrote:
-menu Shared interrupts +menuconfig XENO_OPT_SHIRQ
+ bool Shared interrupts config XENO_OPT_SHIRQ_LEVEL bool Level-triggered interrupts - default n + depends on XENO_OPT_SHIRQ
+ default y help - + Enables support for
Dmitry Adamushko wrote:
On 06/09/06, Jan Kiszka [EMAIL PROTECTED] wrote:
Dmitry Adamushko wrote:
-menu Shared interrupts
+menuconfig XENO_OPT_SHIRQ
+ bool Shared interrupts
config XENO_OPT_SHIRQ_LEVEL
bool Level-triggered interrupts
- default n
+
Jan Kiszka wrote:
Hi Wolfgang,
in the process of preparing to merge rtdm_irq_enable into
rtdm_irq_request I would like to check if the attached patch is ok, thus
we could finally drop rtdm_irq_enable once the API is refactored. Please
check carefully when the first IRQs may happen and what the
Wolfgang Grandegger wrote:
Jan Kiszka wrote:
Hi Wolfgang,
in the process of preparing to merge rtdm_irq_enable into
rtdm_irq_request I would like to check if the attached patch is ok, thus
we could finally drop rtdm_irq_enable once the API is refactored. Please
check carefully when the
