regmap: Convert regmap_irq to use irq_domain

This gets us up to date with the recommended current kernel infrastructure
and should transparently give us device tree interrupt bindings for any
devices using the framework. If an explicit IRQ mapping is passed in then
a legacy interrupt range is created, otherwise a simple linear mapping is
used. Previously a mapping was mandatory so existing drivers should not
be affected.

A function regmap_irq_get_virq() is provided to allow drivers to map
individual IRQs which should be used in preference to the existing
regmap_irq_chip_get_base() which is only valid if a legacy IRQ range is
provided.

Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>

1 files changed, 3 insertions, 0 deletions

diff --git a/drivers/mfd/Kconfig b/drivers/mfd/Kconfig
index 11e44386fa9b..697d686927f8 100644
--- a/drivers/mfd/Kconfig
+++ b/drivers/mfd/Kconfig
@@ -376,6 +376,7 @@ config PMIC_DA9052
 
 config MFD_DA9052_SPI
         bool "Support Dialog Semiconductor DA9052/53 PMIC variants with SPI"
+        select IRQ_DOMAIN
         select REGMAP_SPI
         select REGMAP_IRQ
         select PMIC_DA9052
@@ -388,6 +389,7 @@ config MFD_DA9052_SPI
 
 config MFD_DA9052_I2C
         bool "Support Dialog Semiconductor DA9052/53 PMIC variants with I2C"
+        select IRQ_DOMAIN
         select REGMAP_I2C
         select REGMAP_IRQ
         select PMIC_DA9052
@@ -558,6 +560,7 @@ config MFD_WM8994
         bool "Support Wolfson Microelectronics WM8994"
         select MFD_CORE
         select REGMAP_I2C
+        select IRQ_DOMAIN
         select REGMAP_IRQ
         depends on I2C=y && GENERIC_HARDIRQS
         help