summaryrefslogtreecommitdiff
path: root/fs/configfs
diff options
context:
space:
mode:
authorMarc Zyngier <marc.zyngier@arm.com>2019-02-20 11:59:23 +0300
committerMarc Zyngier <marc.zyngier@arm.com>2019-02-21 13:32:28 +0300
commit9f199dd34ce06f603df365ab18bd84eefc5f7c2b (patch)
treed0d7569dbdb9d4ebead9cefa5e21a8973cf4090e /fs/configfs
parentcc9f04f9a84f745949e325661550ed14bd0ff322 (diff)
downloadlinux-9f199dd34ce06f603df365ab18bd84eefc5f7c2b.tar.xz
irqdomain: Allow the default irq domain to be retrieved
The default irq domain allows legacy code to create irqdomain mappings without having to track the domain it is allocating from. Setting the default domain is a one shot, fire and forget operation, and no effort was made to be able to retrieve this information at a later point in time. Newer irqdomain APIs (the hierarchical stuff) relies on both the irqchip code to track the irqdomain it is allocating from, as well as some form of firmware abstraction to easily identify which piece of HW maps to which irq domain (DT, ACPI). For systems without such firmware (or legacy platform that are getting dragged into the 21st century), things are a bit harder. For these cases (and these cases only!), let's provide a way to retrieve the default domain, allowing the use of the v2 API without having to resort to platform-specific hacks. Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Diffstat (limited to 'fs/configfs')
0 files changed, 0 insertions, 0 deletions