path: root/Documentation/core-api
diff options
authorAndy Shevchenko <>2020-10-30 18:59:18 +0200
committerThomas Gleixner <>2020-11-07 11:33:46 +0100
commitb6e95788fde8c9bc9da729102085dd36a5a0cda6 (patch)
tree2b61e1df7e5e67e8da079c9842f1c0ebe689a9c5 /Documentation/core-api
parentc3a877fea962d9d0fb1e3747334699978f566930 (diff)
irqdomain: Introduce irq_domain_create_legacy() API
Introduce irq_domain_create_legacy() API which is functional equivalent to the existing irq_domain_add_legacy(), but takes a pointer to the struct fwnode_handle as a parameter. This is useful for non OF systems. Signed-off-by: Andy Shevchenko <> Signed-off-by: Thomas Gleixner <> Reviewed-by: Rafael J. Wysocki <> Link:
Diffstat (limited to 'Documentation/core-api')
1 files changed, 6 insertions, 0 deletions
diff --git a/Documentation/core-api/irq/irq-domain.rst b/Documentation/core-api/irq/irq-domain.rst
index 096db12f32d5..a77c24c27f7b 100644
--- a/Documentation/core-api/irq/irq-domain.rst
+++ b/Documentation/core-api/irq/irq-domain.rst
@@ -147,6 +147,7 @@ Legacy
+ irq_domain_create_legacy()
The Legacy mapping is a special case for drivers that already have a
range of irq_descs allocated for the hwirqs. It is used when the
@@ -185,6 +186,11 @@ that the driver using the simple domain call irq_create_mapping()
before any irq_find_mapping() since the latter will actually work
for the static IRQ assignment case.
+irq_domain_add_legacy() and irq_domain_create_legacy() are functionally
+equivalent, except for the first argument is different - the former
+accepts an Open Firmware specific 'struct device_node', while the latter
+accepts a more general abstraction 'struct fwnode_handle'.
Hierarchy IRQ domain