Revision 0848c94fb4a5cc213a7fb0fb3a5721ad6e16f096 authored by Mark Brown on 11 September 2012, 07:16:36 UTC, committed by Samuel Ortiz on 15 September 2012, 21:22:04 UTC
Currently the MFD core supports remapping MFD cell interrupts using an
irqdomain but only if the MFD is being instantiated using device tree
and only if the device tree bindings use the pattern of registering IPs
in the device tree with compatible properties.  This will be actively
harmful for drivers which support non-DT platforms and use this pattern
for their DT bindings as it will mean that the core will silently change
remapping behaviour and it is also limiting for drivers which don't do
DT with this particular pattern.  There is also a potential fragility if
there are interrupts not associated with MFD cells and all the cells are
omitted from the device tree for some reason.

Instead change the code to take an IRQ domain as an optional argument,
allowing drivers to take the decision about the parent domain for their
interrupts.  The one current user of this feature is ab8500-core, it has
the domain lookup pushed out into the driver.

Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
1 parent a0e3532
History
File Mode Size
configs
gxio
include
kernel
kvm
lib
mm
Kbuild -rw-r--r-- 31 bytes
Kconfig -rw-r--r-- 11.5 KB
Kconfig.debug -rw-r--r-- 1.0 KB
Makefile -rw-r--r-- 2.3 KB

back to top