An error occurred fetching the project authors.
  1. 14 Dec, 2020 1 commit
  2. 05 Dec, 2020 1 commit
    • Daniel Palmer's avatar
      gpio: msc313: MStar MSC313 GPIO driver · 93224edf
      Daniel Palmer authored
      This adds a driver that supports the GPIO block found in
      MStar/SigmaStar ARMv7 SoCs.
      
      The controller seems to have enough register for 128 lines
      but where they are wired up differs between chips and
      no currently known chip uses anywhere near 128 lines so there
      needs to be some per-chip data to collect together what lines
      actually have physical pins attached and map the right names to them.
      
      The core peripherals seem to use the same lines on the
      currently known chips but the lines used for the sensor
      interface, lcd controller etc pins seem to be totally
      different between the infinity and mercury chips
      
      The code tries to collect all of the re-usable names,
      offsets etc together so that it's easy to build the extra
      per-chip data for other chips in the future.
      
      So far this only supports the MSC313 and MSC313E chips.
      
      Support for the SSC8336N (mercury5) is trivial to add once
      all of the lines have been mapped out.
      Signed-off-by: default avatarDaniel Palmer <daniel@0x0f.com>
      Link: https://lore.kernel.org/r/20201129110803.2461700-4-daniel@0x0f.comSigned-off-by: default avatarLinus Walleij <linus.walleij@linaro.org>
      93224edf
  3. 30 Sep, 2020 1 commit
  4. 17 Sep, 2020 1 commit
  5. 14 Sep, 2020 1 commit
  6. 16 Jul, 2020 1 commit
  7. 20 Jun, 2020 1 commit
  8. 03 Jun, 2020 1 commit
  9. 18 May, 2020 1 commit
  10. 09 Mar, 2020 1 commit
  11. 24 Jan, 2020 1 commit
    • Matti Vaittinen's avatar
      gpio: bd71828: Initial support for ROHM BD71828 PMIC GPIOs · c31f625d
      Matti Vaittinen authored
      ROHM BD71828 PMIC contains 4 pins which can be configured by OTP
      to be used for general purposes. First 3 can be used as outputs
      and 4.th pin can be used as input. Allow them to be controlled
      via GPIO framework.
      
      The driver assumes all of the pins are configured as GPIOs and
      trusts that the reserved pins in other OTP configurations are
      excluded from control using "gpio-reserved-ranges" device tree
      property (or left untouched by GPIO users).
      
      Typical use for 4.th pin (input) is to use it as HALL sensor
      input so that this pin state is toggled when HALL sensor detects
      LID position change (from close to open or open to close). PMIC
      HW implements some extra logic which allows PMIC to power-up the
      system when this pin is toggled. Please see the data sheet for
      details of GPIO options which can be selected by OTP settings.
      Signed-off-by: default avatarMatti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
      Reviewed-by: default avatarBartosz Golaszewski <bgolaszewski@baylibre.com>
      Reviewed-by: default avatarLinus Walleij <linus.walleij@linaro.org>
      Signed-off-by: default avatarLee Jones <lee.jones@linaro.org>
      c31f625d
  12. 20 Jan, 2020 1 commit
  13. 15 Jan, 2020 1 commit
  14. 13 Dec, 2019 2 commits
  15. 29 Oct, 2019 2 commits
  16. 30 Sep, 2019 1 commit
  17. 15 Aug, 2019 1 commit
  18. 14 Aug, 2019 1 commit
  19. 12 Aug, 2019 1 commit
  20. 10 Aug, 2019 1 commit
  21. 27 Jun, 2019 2 commits
  22. 08 May, 2019 1 commit
  23. 23 Apr, 2019 1 commit
    • Linus Walleij's avatar
      gpio: ixp4xx: Add driver for the IXP4xx GPIO · 813e7d36
      Linus Walleij authored
      This adds a driver for the IXP4xx GPIO block found in
      the Intel XScale IXP4xx systems.
      
      The GPIO part of this block is pretty straight-forward and
      just uses the generic MMIO GPIO library.
      
      The irqchip side of this driver is hierarchical where
      the main irqchip will receive a processed level trigger
      in response to the edge detector of the GPIO block,
      so for this reason the v2 version of the irqdomain API
      is used (as well as in the parent IXP4xx irqchip) and
      masking, unmasking and setting up the type on IRQ
      happens on several levels.
      
      Currently this GPIO controller will grab the parent
      irqdomain using a special function, but as the platform
      move toward device tree probing, this will not be needed:
      we can just look up the parent irqdomain from the device
      tree.
      
      Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>
      Signed-off-by: default avatarLinus Walleij <linus.walleij@linaro.org>
      813e7d36
  24. 26 Mar, 2019 1 commit
  25. 22 Feb, 2019 1 commit
  26. 09 Feb, 2019 1 commit
  27. 28 Jan, 2019 1 commit
  28. 21 Dec, 2018 2 commits
  29. 10 Oct, 2018 1 commit
  30. 28 Sep, 2018 1 commit
  31. 25 Sep, 2018 1 commit
  32. 29 Aug, 2018 1 commit
  33. 09 Jul, 2018 1 commit
  34. 05 Jun, 2018 1 commit
  35. 27 Mar, 2018 2 commits