1. 20 12月, 2013 1 次提交
  2. 24 10月, 2013 1 次提交
  3. 23 10月, 2013 1 次提交
  4. 02 9月, 2013 1 次提交
  5. 31 7月, 2013 3 次提交
  6. 08 4月, 2013 1 次提交
  7. 04 1月, 2013 1 次提交
    • G
      Drivers: mfd: remove __dev* attributes. · 612b95cd
      Greg Kroah-Hartman 提交于
      CONFIG_HOTPLUG is going away as an option.  As a result, the __dev*
      markings need to be removed.
      
      This change removes the use of __devinit, __devexit_p, __devinitdata,
      __devinitconst, and __devexit from these drivers.
      
      Based on patches originally written by Bill Pemberton, but redone by me
      in order to handle some of the coding style issues better, by hand.
      
      Cc: Bill Pemberton <wfp5p@virginia.edu>
      Cc: Samuel Ortiz <sameo@linux.intel.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      612b95cd
  8. 21 11月, 2012 1 次提交
  9. 14 11月, 2012 6 次提交
  10. 19 9月, 2012 2 次提交
  11. 16 9月, 2012 1 次提交
    • M
      mfd: core: Push irqdomain mapping out into devices · 0848c94f
      Mark Brown 提交于
      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: NMark Brown <broonie@opensource.wolfsonmicro.com>
      Signed-off-by: NSamuel Ortiz <sameo@linux.intel.com>
      0848c94f
  12. 14 9月, 2012 1 次提交
    • M
      mfd: core: Push irqdomain mapping out into devices · 55692af5
      Mark Brown 提交于
      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: NMark Brown <broonie@opensource.wolfsonmicro.com>
      Signed-off-by: NSamuel Ortiz <sameo@linux.intel.com>
      55692af5
  13. 25 7月, 2012 1 次提交
  14. 16 7月, 2012 1 次提交
  15. 23 5月, 2012 1 次提交
    • S
      mfd: Fix twl6040 build failure · ca2cad6a
      Samuel Ortiz 提交于
      Without it we get:
      
       CC      drivers/mfd/twl6040-core.o
      drivers/mfd/twl6040-core.c: In function ‘twl6040_has_vibra’:
      drivers/mfd/twl6040-core.c:55:2: error: implicit declaration of function
      ‘of_find_node_by_name’ [-Werror=implicit-function-declaration]
      Signed-off-by: NSamuel Ortiz <sameo@linux.intel.com>
      ca2cad6a
  16. 20 5月, 2012 3 次提交
  17. 10 5月, 2012 1 次提交
  18. 09 5月, 2012 1 次提交
  19. 16 4月, 2012 1 次提交
  20. 04 2月, 2012 2 次提交
  21. 09 1月, 2012 2 次提交
  22. 12 10月, 2011 2 次提交
  23. 20 9月, 2011 3 次提交
  24. 07 7月, 2011 2 次提交