Hi Thomas,
I'll go with something extra like:
Add a function to allow the affinity of an interrupt be switched to
managed, such that interrupts allocated for platform devices may be
managed.
Could you please add a paragraph which explains the limitations of that
interface?
This new interface has certain limitations, and attempts to use it in
the following circumstances will fail:
- For when the kernel is configured for generic IRQ reservation mode (in
config GENERIC_IRQ_RESERVATION_MODE). The reason being that it could
conflict with managed vs. non-managed interrupt accounting there.
- The interrupt is already started, which should not be the case during init
- The interrupt is already configured as managed, which means double init
+/**
+ * irq_update_affinity_desc - Update affinity management for an interrupt
+ * @irq: The interrupt number to update
+ * @affinity: Pointer to the affinity descriptor
+ *
+ * This interface can be used to configure the affinity management of
+ * interrupts which have been allocated already.
/*
* There are certain limitations on when it may be used - attempts to
use it for when the kernel is configured for generic IRQ reservation
mode (in config GENERIC_IRQ_RESERVATION_MODE) will fail, as it may
conflict with managed/non-managed interrupt accounting. In addition,
attempts to use it on an interrupt which is already started or which has
already been configured as managed will also fail, as these mean invalid
init state or double init.
...
Let me know if not good, if not I'll post again soon.
Thanks,
John
