Skip to content

K
Kernel

openeuler / Kernel
1 年多 前同步成功

通知 8
Star 0
Fork 0
K
Kernel
切换分支/标签
  1. 26 9月, 2014 4 次提交
  3. 24 9月, 2014 1 次提交
  5. 21 7月, 2014 1 次提交
  7. 17 6月, 2014 2 次提交
  9. 03 6月, 2014 3 次提交
  11. 16 5月, 2014 2 次提交
    • P
      mfd: vexpress: Define the device as MFD cells · 974cc7b9
      由 Pawel Moll 提交于 
      This patch - finally, after over 6 months! :-( - addresses
Samuel's request to split the vexpress-sysreg driver into
smaller portions and define the device in a form of MFD
cells:

* LEDs code has been completely removed and replaced with
  "gpio-leds" nodes in the tree (referencing dedicated
  GPIO subnodes in sysreg - bindings documentation updated);
  this also better fits the reality as some variants of the
  motherboard don't have all the LEDs populated

* syscfg bridge code has been extracted into a separate
  driver (placed in drivers/misc for no better place)

* all the ID & MISC registers are defined as sysconf
  making them available for other drivers should they need
  to use them (and also to the user via /sys/kernel/debug/regmap
  which can be helpful in platform debugging)
Signed-off-by: NPawel Moll <pawel.moll@arm.com>
Acked-by: NLee Jones <lee.jones@linaro.org>
      974cc7b9
    • P
      mfd: vexpress: Convert custom func API to regmap · 3b9334ac
      由 Pawel Moll 提交于 
      Components of the Versatile Express platform (configuration
microcontrollers on motherboard and daughterboards in particular)
talk to each other over a custom configuration bus. They
provide miscellaneous functions (from clock generator control
to energy sensors) which are represented as platform devices
(and Device Tree nodes). The transactions on the bus can
be generated by different "bridges" in the system, some
of which are universal for the whole platform (for the price
of high transfer latencies), others restricted to a subsystem
(but much faster).

Until now drivers for such functions were using custom "func"
API, which is being replaced in this patch by regmap calls.
This required:

* a rework (and move to drivers/bus directory, as suggested
  by Samuel and Arnd) of the config bus core, which is much
  simpler now and uses device model infrastructure (class)
  to keep track of the bridges; non-DT case (soon to be
  retired anyway) is simply covered by a special device
  registration function

* the new config-bus driver also takes over device population,
  so there is no need for special matching table for
  of_platform_populate nor "simple-bus" hack in the arm64
  model dtsi file (relevant bindings documentation has
  been updated); this allows all the vexpress devices
  fit into normal device model, making it possible
  to remove plenty of early inits and other hacks in
  the near future

* adaptation of the syscfg bridge implementation in the
  sysreg driver, again making it much simpler; there is
  a special case of the "energy" function spanning two
  registers, where they should be both defined in the tree
  now, but backward compatibility is maintained in the code

* modification of the relevant drivers:

  * hwmon - just a straight-forward API change
  * power/reset driver - API change
  * regulator - API change plus error handling
    simplification
  * osc clock driver - this one required larger rework
    in order to turn in into a standard platform driver
Signed-off-by: NPawel Moll <pawel.moll@arm.com>
Acked-by: NMark Brown <broonie@linaro.org>
Acked-by: NLee Jones <lee.jones@linaro.org>
Acked-by: NGuenter Roeck <linux@roeck-us.net>
Acked-by: NMike Turquette <mturquette@linaro.org>
      3b9334ac
  13. 19 3月, 2014 5 次提交
  15. 18 3月, 2014 1 次提交
  17. 21 1月, 2014 2 次提交
    • M
      mfd: Add LP3943 MFD driver · 470eca47
      由 Milo Kim 提交于 
      LP3943 has 16 output pins which can be used as GPIO expander and PWM generator.

* Regmap I2C interface for R/W LP3943 registers

* Atomic operations for output pin assignment
  The driver should check whether requested pin is available or not.
  If the pin is already used, pin request returns as a failure.
  A driver data, 'pin_used' is checked when gpio_request() and
  pwm_request() are called. If the pin is available, then pin_used is set.
  And it is cleared when gpio_free() and pwm_free().

* Device tree support
  Compatible strings for GPIO and PWM driver.
  LP3943 platform data is PWM related, so parsing the device tree is
  implemented in the PWM driver.
Signed-off-by: NMilo Kim <milo.kim@ti.com>
Signed-off-by: NLee Jones <lee.jones@linaro.org>
      470eca47
    • C
      mfd: max14577: Add max14577 MFD driver core · 3008ddbe
      由 Chanwoo Choi 提交于 
      This patch adds max14577 core/irq driver to support MUIC(Micro USB IC)
device and charger device and support irq domain method to control
internal interrupt of max14577 device. Also, this patch supports DT
binding with max14577_i2c_parse_dt().

The MAXIM 14577 chip contains Micro-USB Interface Circuit and Li+ Battery
Charger. It contains accessory and USB charger detection logic. It supports
USB 2.0 Hi-Speed, UART and stereo audio signals over Micro-USB connector.

The battery charger is compliant with the USB Battery Charging Specification
Revision 1.1. It has also SFOUT LDO output for powering USB devices.
Reviewed-by: NMark Brown <broonie@linaro.org>
Signed-off-by: NChanwoo Choi <cw00.choi@samsung.com>
Signed-off-by: NKrzysztof Kozlowski <k.kozlowski@samsung.com>
Signed-off-by: NKyungmin Park <kyungmin.park@samsung.com>
Signed-off-by: NLee Jones <lee.jones@linaro.org>
      3008ddbe
  19. 23 10月, 2013 2 次提交
  21. 20 8月, 2013 2 次提交
  23. 24 6月, 2013 1 次提交
  25. 18 6月, 2013 1 次提交
  27. 12 6月, 2013 1 次提交
  29. 20 4月, 2013 2 次提交
  31. 17 4月, 2013 1 次提交
  33. 05 4月, 2013 3 次提交
  35. 29 3月, 2013 1 次提交
  37. 14 2月, 2013 1 次提交
  39. 23 11月, 2012 1 次提交
  41. 21 11月, 2012 2 次提交
  43. 20 11月, 2012 1 次提交