1. 27 4月, 2017 1 次提交
  2. 16 11月, 2016 1 次提交
    • L
      mfd: stmpe: Fix RESET regression on STMPE2401 · f4058420
      Linus Walleij 提交于
      Since commit c4dd1ba3
      ("mfd: stmpe: Add reset support for all STMPE variant")
      we're resetting the STMPE expanders before use.
      
      This caused a regression on the STMP2401 on the Nomadik
      NHK8815:
      
      stmpe-i2c 0-0043: stmpe2401 detected, chip id: 0x101
      nmk-i2c 101f8000.i2c0: write to slave 0x43 timed out
      nmk-i2c 101f8000.i2c0: no ack received after address transmission
      stmpe-i2c 0-0044: stmpe2401 detected, chip id: 0x101
      nmk-i2c 101f8000.i2c0: write to slave 0x44 timed out
      nmk-i2c 101f8000.i2c0: no ack received after address transmission
      
      It turns out that we start to poll for the reset bit to
      go low again too quickly: the STMPE2401 is not yet online and
      ready to be asked for the status of the RESET bit.
      
      By introducing a 10ms delay before starting to hammer
      the register for information, we get back to normal:
      
      stmpe-i2c 0-0043: stmpe2401 detected, chip id: 0x101
      stmpe-i2c 0-0044: stmpe2401 detected, chip id: 0x101
      
      Cc: stable@vger.kernel.org
      Cc: Amelie Delaunay <amelie.delaunay@st.com>
      Fixes: c4dd1ba3 ("mfd: stmpe: Add reset support for all STMPE variant")
      Signed-off-by: NLinus Walleij <linus.walleij@linaro.org>
      Acked-by: NPatrice Chotard <patrice.chotard@st.com>
      Signed-off-by: NLee Jones <lee.jones@linaro.org>
      f4058420
  3. 10 8月, 2016 5 次提交
  4. 29 6月, 2016 1 次提交
  5. 16 3月, 2016 1 次提交
  6. 26 10月, 2015 1 次提交
  7. 11 8月, 2015 1 次提交
    • R
      mfd: Kill off set_irq_flags usage · 9bd09f34
      Rob Herring 提交于
      set_irq_flags is ARM specific with custom flags which have genirq
      equivalents. Convert drivers to use the genirq interfaces directly, so we
      can kill off set_irq_flags. The translation of flags is as follows:
      
      IRQF_VALID -> !IRQ_NOREQUEST
      IRQF_PROBE -> !IRQ_NOPROBE
      IRQF_NOAUTOEN -> IRQ_NOAUTOEN
      
      For IRQs managed by an irqdomain, the irqdomain core code handles clearing
      and setting IRQ_NOREQUEST already, so there is no need to do this in
      .map() functions and we can simply remove the set_irq_flags calls. Some
      users also modify IRQ_NOPROBE and this has been maintained although it
      is not clear that is really needed. There appears to be a great deal of
      blind copy and paste of this code.
      Signed-off-by: NRob Herring <robh@kernel.org>
      Acked-by: NLinus Walleij <linus.walleij@linaro.org>
      Signed-off-by: NLee Jones <lee.jones@linaro.org>
      9bd09f34
  8. 22 6月, 2015 1 次提交
  9. 16 12月, 2014 1 次提交
  10. 26 9月, 2014 2 次提交
  11. 09 7月, 2014 1 次提交
  12. 23 5月, 2014 1 次提交
  13. 09 5月, 2014 2 次提交
  14. 19 3月, 2014 1 次提交
  15. 06 1月, 2014 1 次提交
  16. 31 7月, 2013 1 次提交
  17. 25 6月, 2013 1 次提交
  18. 09 4月, 2013 1 次提交
  19. 06 4月, 2013 2 次提交
  20. 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
  21. 10 12月, 2012 1 次提交
  22. 02 12月, 2012 1 次提交
  23. 30 11月, 2012 1 次提交
  24. 27 11月, 2012 1 次提交
  25. 26 11月, 2012 1 次提交
  26. 24 11月, 2012 1 次提交
  27. 23 11月, 2012 2 次提交
  28. 12 11月, 2012 4 次提交
  29. 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