1. 29 Nov, 2016 1 commit
    • Arnd Bergmann's avatar
      mfd: tps65912: Move regmap config into core driver · 054814b8
      Arnd Bergmann authored
      When building with extra warnings enabled, most files including
      linux/mfd/tps65912.h warn about a static variable defined in the
      header:
      
      include/linux/mfd/tps65912.h:331:35: warning: 'tps65912_regmap_config' defined but not used [-Wunused-const-variable=]
      
      We also duplicate the data structure between the i2c and spi front-end
      drivers. Moving it into the driver code avoids the warning and
      the duplication.
      Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      Signed-off-by: default avatarLee Jones <lee.jones@linaro.org>
      054814b8
  2. 11 Feb, 2016 2 commits
  3. 19 Mar, 2014 1 commit
  4. 06 Jan, 2014 1 commit
  5. 31 Jul, 2013 1 commit
  6. 13 Jun, 2013 1 commit
  7. 12 Mar, 2013 1 commit
  8. 15 Sep, 2012 1 commit
    • Mark Brown's avatar
      mfd: core: Push irqdomain mapping out into devices · 0848c94f
      Mark Brown authored
      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: default avatarMark Brown <broonie@opensource.wolfsonmicro.com>
      Signed-off-by: default avatarSamuel Ortiz <sameo@linux.intel.com>
      0848c94f
  9. 14 Sep, 2012 1 commit
    • Mark Brown's avatar
      mfd: core: Push irqdomain mapping out into devices · 55692af5
      Mark Brown authored
      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: default avatarMark Brown <broonie@opensource.wolfsonmicro.com>
      Signed-off-by: default avatarSamuel Ortiz <sameo@linux.intel.com>
      55692af5
  10. 06 Mar, 2012 1 commit
  11. 23 Feb, 2012 1 commit
  12. 24 Oct, 2011 1 commit
  13. 31 Jul, 2011 2 commits