1. 04 3月, 2015 2 次提交
    • F
      mfd: Add support for the MediaTek MT6397 PMIC · 6df8dd5c
      Flora Fu 提交于
      This adds support for the MediaTek MT6397 PMIC. This is a
      multifunction device with the following sub modules:
      
      - Regulator
      - RTC
      - Audio codec
      - GPIO
      - Clock
      
      It is interfaced to the host controller using SPI interface by a proprietary
      hardware called PMIC wrapper or pwrap. MT6397 MFD is a child device of the
      pwrap.
      
      Signed-off-by: Flora Fu, MediaTek
      Signed-off-by: NSascha Hauer <s.hauer@pengutronix.de>
      Signed-off-by: NLee Jones <lee.jones@linaro.org>
      6df8dd5c
    • M
      mfd: rtsx: Remove LCTLR defination · 19f3bd54
      Micky Ching 提交于
      To enable/disable ASPM we should find LINK CONTROL register
      in PCI config space. All old chip use 0x80 address, but new
      chip may use another address, so we using pci_find_capability()
      to get LINK CONTROL address.
      
      rtsx_gops.c was removed, we consider to put some common operations
      to this file, but the actual thing is, only a group of chips
      are in common ops1, and another group of chips in common ops2,
      it is hard to decide put which ops into generic ops file.
      Signed-off-by: NMicky Ching <micky_ching@realsil.com.cn>
      Signed-off-by: NLee Jones <lee.jones@linaro.org>
      19f3bd54
  2. 23 1月, 2015 1 次提交
  3. 22 1月, 2015 2 次提交
  4. 26 11月, 2014 2 次提交
  5. 11 11月, 2014 1 次提交
    • O
      mfd: Add support for Diolan DLN-2 devices · 338a1281
      Octavian Purdila 提交于
      This patch implements the USB part of the Diolan USB-I2C/SPI/GPIO
      Master Adapter DLN-2. Details about the device can be found here:
      
      https://www.diolan.com/i2c/i2c_interface.html.
      
      Information about the USB protocol can be found in the Programmer's
      Reference Manual [1], see section 1.7.
      
      Because the hardware has a single transmit endpoint and a single
      receive endpoint the communication between the various DLN2 drivers
      and the hardware will be muxed/demuxed by this driver.
      
      Each DLN2 module will be identified by the handle field within the DLN2
      message header. If a DLN2 module issues multiple commands in parallel
      they will be identified by the echo counter field in the message header.
      
      The DLN2 modules can use the dln2_transfer() function to issue a
      command and wait for its response. They can also register a callback
      that is going to be called when a specific event id is generated by
      the device (e.g. GPIO interrupts). The device uses handle 0 for
      sending events.
      
      [1] https://www.diolan.com/downloads/dln-api-manual.pdfSigned-off-by: NOctavian Purdila <octavian.purdila@intel.com>
      Reviewed-by: NJohan Hovold <johan@kernel.org>
      Signed-off-by: NLee Jones <lee.jones@linaro.org>
      338a1281
  6. 26 9月, 2014 4 次提交
  7. 24 9月, 2014 1 次提交
  8. 21 7月, 2014 1 次提交
  9. 17 6月, 2014 2 次提交
  10. 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
  12. 19 3月, 2014 5 次提交
  13. 18 3月, 2014 1 次提交
  14. 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
  15. 23 10月, 2013 2 次提交
  16. 20 8月, 2013 2 次提交
  17. 24 6月, 2013 1 次提交
  18. 18 6月, 2013 1 次提交
  19. 12 6月, 2013 1 次提交
  20. 20 4月, 2013 2 次提交
  21. 17 4月, 2013 1 次提交
  22. 05 4月, 2013 1 次提交