Re: [PATCH v4 1/4] Documentation: dt-bindings: Describe SROMc configuration

W dniu 30.10.2015 o 19:43, Pavel Fedin pisze: > Hello! > >> Please, carefully look at: >> Documentation/devicetree/bindings/net/gpmc-eth.txt >> Documentation/devicetree/bindings/bus/ti-gpmc.txt >> >> 1. Try to re-use existing bindings. Although I see existing bank-width >> and gpmc,device-width

Re: [PATCH v4 5/6] ARM: dts: sunxi: Add Allwinner H3 DTSI

Hi, On Fri, Oct 30, 2015 at 03:33:05PM +0800, Chen-Yu Tsai wrote: > > + pll6: clk@01c20028 { > > + #clock-cells = <1>; > > + compatible = "allwinner,sun6i-a31-pll6-clk"; > > + reg = <0x01c20028 0x4>; > > +

Re: [PATCH v4 5/6] ARM: dts: sunxi: Add Allwinner H3 DTSI

Hi, On Tue, Oct 27, 2015 at 05:50:25PM +0100, Jens Kuske wrote: > + bus_gates: clk@01c20060 { > + #clock-cells = <1>; > + compatible = "allwinner,sun8i-h3-bus-gates-clk"; > + reg = <0x01c20060 0x14>; > +

Re: [PATCH] ARM: dts: sun4i: Enable audio codec on Olimex A20-SOM-EVB

Hi, On Sat, Oct 31, 2015 at 01:55:42PM +0100, Marcus Weseloh wrote: > Enable the on-chip audio codec on the Olimex A20-SOM-EVB > > Signed-off-by: Marcus Weseloh > --- > arch/arm/boot/dts/sun7i-a20-olimex-som-evb.dts | 4 > 1 file changed, 4 insertions(+) > > diff

Re: [PATCH v4 1/4] Documentation: dt-bindings: Describe SROMc configuration

W dniu 31.10.2015 o 02:15, Rob Herring pisze: > On Fri, Oct 30, 2015 at 2:23 AM, Krzysztof Kozlowski > wrote: >> On 30.10.2015 15:58, Pavel Fedin wrote: >>> Hello! >>> > Add documentation for new subnode properties, allowing bank configuration. > Based on u-boot

Re: [PATCH v4 2/6] clk: sunxi: Add H3 clocks support

Hi, On 30/10/15 09:28, Arnd Bergmann wrote: > On Tuesday 27 October 2015 17:50:22 Jens Kuske wrote: >> + of_property_read_string_index(node, "clock-output-names", >> + i, _name); >> + >> + if (index == 17 || (index >= 29 &&

Re: [linux-sunxi] Re: [PATCH v4 3/6] pinctrl: sunxi: Add H3 PIO controller support

On Sun, Nov 1, 2015 at 9:17 PM, Jens Kuske wrote: > On 30/10/15 09:08, Chen-Yu Tsai wrote: >> Hi, >> >> On Wed, Oct 28, 2015 at 12:50 AM, Jens Kuske wrote: >>> The H3 uses the same pin controller as previous SoC's from Allwinner. >>> Add support for the

Re: [PATCH 2/2] dma: add Qualcomm Technologies HIDMA channel driver

Also, if you waste CPU cycles for hundreds of milliseconds, it's unlikely that the function is so performance critical that it requires writel_relaxed(). Just use writel() here. ok, replaced writel_relaxed+wmb with writel. The issue is not writel_relaxed vs. writel. After I issue reset,

[PATCH] ARM: dts: sun7i: Enable audio codec on Wexler TAB7200 tablet.

Enable on-chip audio codec on the Wexler TAB7200 tablet. Signed-off-by: Aleksei Mamlin --- arch/arm/boot/dts/sun7i-a20-wexler-tab7200.dts | 7 +++ 1 file changed, 7 insertions(+) diff --git a/arch/arm/boot/dts/sun7i-a20-wexler-tab7200.dts

Please Read

Business Deal of 24.5M USD for you, reply williel...@gmail.com for more details if interested. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [PATCH 0/2] iio: Heart Rate Monitors

On 31/10/15 16:31, Andrew F. Davis wrote: > Hello all, > > This series adds the TI AFE4404 "Ultra-small, Integrated AFE for > Wearable, Optical Heart Rate Monitoring and Bio-Sensing". > > This work is based on previous work by Dan Murphy [0] who is working > on other tasks at the moment, so I

Re: [PATCH v4 5/6] ARM: dts: sunxi: Add Allwinner H3 DTSI

On Tue, Oct 27, 2015 at 05:50:25PM +0100, Jens Kuske wrote: > + timer { > + compatible = "arm,armv7-timer"; > + interrupts = IRQ_TYPE_LEVEL_LOW)>, > + IRQ_TYPE_LEVEL_LOW)>, > + IRQ_TYPE_LEVEL_LOW)>, > +

Re: [PATCH 09/19] drm: sun4i: Add DT bindings documentation

On Fri, Oct 30, 2015 at 12:37 PM, Thierry Reding wrote: > On Fri, Oct 30, 2015 at 11:40:03AM -0500, Rob Herring wrote: >> On Fri, Oct 30, 2015 at 9:20 AM, Maxime Ripard > [...] >> > +Optional properties: >> > + - allwinner,tv-encoder: phandle to the TV Encoder in our

Re: [PATCH v4 5/6] ARM: dts: sunxi: Add Allwinner H3 DTSI

Hi, On 30/10/15 08:33, Chen-Yu Tsai wrote: > Hi, > > On Wed, Oct 28, 2015 at 12:50 AM, Jens Kuske wrote: >> The Allwinner H3 is a home entertainment system oriented SoC with >> four Cortex-A7 cores and a Mali-400MP2 GPU. >> >> Signed-off-by: Jens Kuske

Re: [PATCH 1/2] Input: Add binding document for a generic ADC keypad

Hi Andrew, On Mon, Mar 30, 2015 at 1:56 AM, Andrew Bresticker wrote: >> I'd rather we have it defined explicitly in the binding, i.e. make it a >> required property? > > Sure, will do. Do you plan to send a v2 of the generic ADC keypad series? Thanks -- To unsubscribe

[RFC v2 2/2] drm/bridge: Add I2C based driver for ps8640 bridge

This patch adds drm_bridge driver for parade DSI to eDP bridge chip. Signed-off-by: Jitao Shi --- drivers/gpu/drm/bridge/Kconfig |9 + drivers/gpu/drm/bridge/Makefile|1 + drivers/gpu/drm/bridge/parade-ps8640.c | 479

[RFC v2 1/2] Documentation: bridge: Add documentation for ps8640 DT properties

Add documentation for DT properties supported by ps8640 DSI-eDP converter. Signed-off-by: Jitao Shi --- .../devicetree/bindings/display/bridge/ps8640.txt | 43 1 file changed, 43 insertions(+) create mode 100644

Re: [linux-sunxi] [PATCH 11/19] drm: sun4i: Add composite output

On 31 October 2015 at 01:20, Maxime Ripard wrote: > Some Allwinner SoCs have an IP called the TV encoder that is used to output > composite and VGA signals. In such a case, we need to use the second TCON > channel. > > Add support for that TV encoder. > >

Re: [PATCH] arm64: renesas: salvator-x: Setup ethernet0 alias for U-Boot

On Fri, Oct 30, 2015 at 03:37:26PM +0200, Laurent Pinchart wrote: > Hi Geert, > > On Friday 30 October 2015 14:16:03 Geert Uytterhoeven wrote: > > On Fri, Oct 30, 2015 at 2:06 PM, Laurent Pinchart wrote: > > > On Friday 30 October 2015 10:25:20 Geert Uytterhoeven wrote: > > >> Add an ethernet0

Re: [RFC v2 1/2] Documentation: bridge: Add documentation for ps8640 DT properties

On Mon, 2015-11-02 at 10:09 +0800, Jitao Shi wrote: > Add documentation for DT properties supported by > ps8640 DSI-eDP converter. > > Signed-off-by: Jitao Shi --- changes since v1: 1. changes power-gpios to sleep-gpios. 2. drop "ps8640-" in properties.

Re: [PATCH v8 1/5] Documentation: add sbsa-gwdt driver documentation

Hi Timur. On 31 October 2015 at 04:37, Timur Tabi wrote: > On 10/30/2015 02:05 PM, Mark Rutland wrote: >> >> I was only asking why the interrupt was optional, and it seems per the >> spec it's expected to be handed to an agent at a higher exception level. >> >> That implies

Re: [PATCH linux-next 0/4] mtd: spi-nor: fix Quad SPI memory support

On Friday, September 18, 2015 at 05:49:24 PM, Cyrille Pitchen wrote: > Hi all, Hi! > this series of patches fixes the QSPI support mostly for Micron and > Macronix memories. There are also some updates for Spansion memories. > There are also many comments to explain the implementation choices

Re: [RFC v2 2/2] drm/bridge: Add I2C based driver for ps8640 bridge

On Mon, 2015-11-02 at 10:09 +0800, Jitao Shi wrote: > This patch adds drm_bridge driver for parade DSI to eDP bridge chip. > > Signed-off-by: Jitao Shi --- changes since v1: 1. remove edid code 2. remove some wrong comments 3. tune some gpios name,

Re: [PATCH v8 1/5] Documentation: add sbsa-gwdt driver documentation

Hi Mark, Great thanks for your feedback. On 31 October 2015 at 03:05, Mark Rutland wrote: > On Fri, Oct 30, 2015 at 01:53:24PM -0500, Timur Tabi wrote: >> On 10/30/2015 01:35 PM, Fu Wei wrote: >> >>I think maybe Mark was asking why WS1 is optional, not the WS1 >> >My

Re: [PATCH v8 1/5] Documentation: add sbsa-gwdt driver documentation

Fu Wei wrote: In virtualization system, Linux kernel with KVM support as a Hypervisor, and guest are using a one of SBSA watchdog. WS0 is handled by guest OS, and WS1 will be handled by Hypervisor. I don't see how that would work, because the host kernel cannot reconfigure the behavior of

Re: [PATCH v8 1/5] Documentation: add sbsa-gwdt driver documentation

On 11/01/2015 11:06 PM, Timur Tabi wrote: > Fu Wei wrote: >> In virtualization system, Linux kernel with KVM support as a >> Hypervisor, and guest are using a one of SBSA watchdog. >> WS0 is handled by guest OS, and WS1 will be handled by Hypervisor. > > I don't see how that would work, because

Re: [PATCH 2/2] dma: add Qualcomm Technologies HIDMA channel driver

Sinan Kaya wrote: However, after issuing the command; I still need to wait some amount of time until hardware acknowledges the commands like reset/enable/disable. These are relatively faster operations happening in microseconds. That's why, I have mdelay there. Can you use

Re: [PATCH v4 1/6] clk: sunxi: Let divs clocks read the base factor clock name from devicetree

On 30/10/15 08:46, Chen-Yu Tsai wrote: > On Wed, Oct 28, 2015 at 12:50 AM, Jens Kuske wrote: [..] >> @@ -991,8 +985,30 @@ static void __init sunxi_divs_clk_setup(struct >> device_node *node, >> if (data->ndivs) >> ndivs = data->ndivs; >> >> + /*

Re: [PATCH v4 4/6] reset: sunxi: Add Allwinner H3 bus resets

Hi, On 30/10/15 09:27, Arnd Bergmann wrote: > On Tuesday 27 October 2015 17:50:24 Jens Kuske wrote: >> >> +static int sun8i_h3_bus_reset_xlate(struct reset_controller_dev *rcdev, >> + const struct of_phandle_args *reset_spec) >> +{ >> + unsigned int index =

Re: [PATCH v4 3/6] pinctrl: sunxi: Add H3 PIO controller support

On 30/10/15 09:08, Chen-Yu Tsai wrote: > Hi, > > On Wed, Oct 28, 2015 at 12:50 AM, Jens Kuske wrote: >> The H3 uses the same pin controller as previous SoC's from Allwinner. >> Add support for the pins controlled by the main PIO controller. >> >> Signed-off-by: Jens Kuske

Re: [PATCH 2/2] dma: add Qualcomm Technologies HIDMA channel driver

On 11/1/2015 3:21 PM, Timur Tabi wrote: Sinan Kaya wrote: However, after issuing the command; I still need to wait some amount of time until hardware acknowledges the commands like reset/enable/disable. These are relatively faster operations happening in microseconds. That's why, I have

Re: [PATCH v10 09/17] dt-bindings: add document for rockchip variant of analogix_dp

On 11/01/2015 02:37 AM, Rob Herring wrote: On Sat, Oct 31, 2015 at 1:42 AM, Yakir Yang wrote: Rockchip DP driver is a helper driver of analogix_dp coder driver, so most of the DT property should be descriped in analogix_dp document. Reviewed-by: Heiko Stuebner

Re: [PATCH 2/2] iio: health: Add driver for the TI AFE4404 heart monitor

On 31/10/15 16:31, Andrew F. Davis wrote: > Add driver for the TI AFE4404 heart rate monitor and pulse oximeter. > This device detects reflected LED light fluctuations and presents an ADC > value to the user space for further signal processing. > > Data sheet located here: >

[PATCH 01/16] Documentation: dt-bindings: mfd: add TI LMU device binding information

This patch describes overall binding for TI LMU MFD devices. Cc: devicetree@vger.kernel.org Cc: Lee Jones Cc: linux-ker...@vger.kernel.org Signed-off-by: Milo Kim --- Documentation/devicetree/bindings/mfd/ti-lmu.txt | 282 +++ 1 file

[PATCH 02/16] Documentation: dt-bindings: backlight: add TI LMU backlight binding information

LM3532, LM3631, LM3632, LM3633, LM3695 and LM3697 use common dt-bindings for describing device. Cc: devicetree@vger.kernel.org Cc: Jingoo Han Cc: Lee Jones Cc: linux-ker...@vger.kernel.org Signed-off-by: Milo Kim ---

[PATCH 04/16] Documentation: dt-bindings: leds: add LM3633 LED binding information

LM3633 LED device is one of TI LMU device list. Cc: devicetree@vger.kernel.org Cc: Jacek Anaszewski Cc: Lee Jones Cc: linux-ker...@vger.kernel.org Cc: linux-l...@vger.kernel.org Signed-off-by: Milo Kim ---

[PATCH RESEND 06/16] mfd: add TI LMU driver

TI LMU(Lighting Management Unit) driver supports lighting devices below. LM3532, LM3631, LM3632, LM3633, LM3695 and LM3697. LMU devices have common features. - I2C interface for accessing device registers - Hardware enable pin control - Backlight brightness control - Max current

[PATCH RESEND 03/16] Documentation: dt-bindings: hwmon: add TI LMU HWMON binding information

Hardware fault monitoring driver is used in LM3633 and LM3697 device. Just 'compatible' property is required to describe the driver. Cc: devicetree@vger.kernel.org Cc: Guenter Roeck Cc: Jean Delvare Cc: Lee Jones Cc:

RE: [PATCH v4 1/4] Documentation: dt-bindings: Describe SROMc configuration

Hello! > > --- cut exynos5410.dtsi --- > > sromc: sromc@1225 { > > #address-cells = <2>; > > #size-cells = <1>; > > ranges = <0 0 0x0400 0x2 > > 1 0 0x0500 0x2 > >

[PATCH 09/16] backlight: ti-lmu-backlight: add LM3631 driver

LM3631 has 2 backlight strings and 11 bit dimming is supported. PWM brightness control is also supported. Common backlight driver is controlled by TI LMU backlight driver. Only LM3631 specific code is implemented here. Cc: Jingoo Han Cc: Lee Jones

[PATCH 12/16] backlight: ti-lmu-backlight: add LM3695 driver

LM3695 has 2 backlight strings and 11 bit dimming is supported. Common backlight driver is controlled by TI LMU backlight driver. Only LM3695 specific code is implemented here. Cc: Jingoo Han Cc: Lee Jones Cc: linux-ker...@vger.kernel.org

[PATCH 06/16] mfd: add TI LMU driver

TI LMU(Lighting Management Unit) driver supports lighting devices below. LM3532, LM3631, LM3632, LM3633, LM3695 and LM3697. LMU devices have common features. - I2C interface for accessing device registers - Hardware enable pin control - Backlight brightness control - Max current

[PATCH 11/16] backlight: ti-lmu-backlight: add LM3633 driver

LM3633 has 3 backlight strings and 11 bit dimming is supported. PWM brightness control is also supported. LM3633 MFD has HWMON driver which monitors hardware fault detection. After this monitoring is done, LM3633 backlight device should be reinitialized. To enable this, 'hwmon_notifier_used' is

[PATCH RESEND 10/16] backlight: ti-lmu-backlight: add LM3632 driver

LM3632 has 2 backlight strings and 11 bit dimming is supported. PWM brightness control is also supported. Common backlight driver is controlled by TI LMU backlight driver. Only LM3632 specific code is implemented here. Cc: Jingoo Han Cc: Lee Jones

Re: [PATCH 00/16] Support TI LMU devices

My apologies for sending without no-chain-reply-to option. So, I've resent the patch-set named 'PATCH RESEND 00/16 .. 16/16'. Best regards, Milo On 11/2/2015 2:01 PM, Milo Kim wrote: TI LMU(Lighting Management Unit) driver supports lighting devices below. Enable pin Backlights

Re: [PATCH RESEND 08/16] backlight: ti-lmu-backlight: add LM3532 driver

Hi Milo, [auto build test ERROR on ljones-mfd/for-mfd-next -- if it's inappropriate base, please suggest rules for selecting the more suitable base] url: https://github.com/0day-ci/linux/commits/Milo-Kim/Support-TI-LMU-devices/20151102-130804 config: mips-allyesconfig (attached as .config)

Re: [PATCH RESEND 08/16] backlight: ti-lmu-backlight: add LM3532 driver

Ouch! The notifier.h must be included. I didn't notice this error in ARM architecture. Let me fix this error in next patch-set. Thanks a lot for catching this! Best regards, Milo diff --git a/include/linux/mfd/ti-lmu.h b/include/linux/mfd/ti-lmu.h index eeb6b9e..44268c7 100644 ---

Re: [RESEND PATCH 2/4] clk: rockchip: set an id for crypto clk

Hi Heiko, On 2015年10月30日 16:54, Heiko Stuebner wrote: > Hi Zain, > > Am Freitag, 30. Oktober 2015, 16:22:47 schrieb Zain Wang: >> set an id for crypto clk, so that it can be called in other part. >> >> Signed-off-by: Zain Wang >> --- >>

[PATCH 07/16] backlight: add TI LMU backlight common driver

TI LMU backlight driver provides common driver features. Chip specific configuration is handled by each backlight driver such like LM3532, LM3631, LM3632, LM3633, LM3695 and LM3697. It supports common features as below. - Backlight subsystem control - Consistent device control flow -

[PATCH 14/16] hwmon: add TI LMU hardware fault monitoring driver

LM3633 and LM3697 are TI LMU MFD device. Those device have hardware monitoring feature which detects opened or shorted circuit case. Attributes -- Two attributes are registered. open_fault: check backlight output channel is opened or not short_fault: check backlight output

[PATCH 03/16] Documentation: dt-bindings: hwmon: add TI LMU HWMON binding information

Hardware fault monitoring driver is used in LM3633 and LM3697 device. Just 'compatible' property is required to describe the driver. Cc: devicetree@vger.kernel.org Cc: Guenter Roeck Cc: Jean Delvare Cc: Lee Jones Cc:

[PATCH 08/16] backlight: ti-lmu-backlight: add LM3532 driver

LM3532 has 3 backlight strings and 8 bit dimming is supported. PWM brightness control is also supported. Common backlight driver is controlled by TI LMU backlight driver. Only LM3532 specific code is implemented here. Cc: Jingoo Han Cc: Lee Jones Cc:

[PATCH 10/16] backlight: ti-lmu-backlight: add LM3632 driver

LM3632 has 2 backlight strings and 11 bit dimming is supported. PWM brightness control is also supported. Common backlight driver is controlled by TI LMU backlight driver. Only LM3632 specific code is implemented here. Cc: Jingoo Han Cc: Lee Jones

[PATCH RESEND 00/16] Support TI LMU devices

TI LMU(Lighting Management Unit) driver supports lighting devices below. Enable pin Backlights HWMON LEDs Regulators -- -- - LM3532 o o x xx LM3631 o o x x5

[PATCH RESEND 04/16] Documentation: dt-bindings: leds: add LM3633 LED binding information

LM3633 LED device is one of TI LMU device list. Cc: devicetree@vger.kernel.org Cc: Jacek Anaszewski Cc: Lee Jones Cc: linux-ker...@vger.kernel.org Cc: linux-l...@vger.kernel.org Signed-off-by: Milo Kim ---

[PATCH RESEND 12/16] backlight: ti-lmu-backlight: add LM3695 driver

LM3695 has 2 backlight strings and 11 bit dimming is supported. Common backlight driver is controlled by TI LMU backlight driver. Only LM3695 specific code is implemented here. Cc: Jingoo Han Cc: Lee Jones Cc: linux-ker...@vger.kernel.org

[PATCH RESEND 05/16] Documentation: dt-bindings: regulator: add LM363x regulator binding information

This binding supports LM3631 and LM3632 regulator configuration. Cc: devicetree@vger.kernel.org Cc: Lee Jones Cc: Mark Brown Cc: linux-ker...@vger.kernel.org Signed-off-by: Milo Kim --- .../bindings/regulator/lm363x-regulator.txt

[PATCH RESEND 08/16] backlight: ti-lmu-backlight: add LM3532 driver

LM3532 has 3 backlight strings and 8 bit dimming is supported. PWM brightness control is also supported. Common backlight driver is controlled by TI LMU backlight driver. Only LM3532 specific code is implemented here. Cc: Jingoo Han Cc: Lee Jones Cc:

[PATCH RESEND 11/16] backlight: ti-lmu-backlight: add LM3633 driver

LM3633 has 3 backlight strings and 11 bit dimming is supported. PWM brightness control is also supported. LM3633 MFD has HWMON driver which monitors hardware fault detection. After this monitoring is done, LM3633 backlight device should be reinitialized. To enable this, 'hwmon_notifier_used' is

[PATCH RESEND 13/16] backlight: ti-lmu-backlight: add LM3697 driver

LM3697 has 3 backlight strings and 11 bit dimming is supported. PWM brightness control is also supported. LM3697 MFD has HWMON driver which monitors hardware fault detection. After this monitoring is done, LM3697 backlight device should be reinitialized. To enable this, 'hwmon_notifier_used' is

[PATCH RESEND 01/16] Documentation: dt-bindings: mfd: add TI LMU device binding information

This patch describes overall binding for TI LMU MFD devices. Cc: devicetree@vger.kernel.org Cc: Lee Jones Cc: linux-ker...@vger.kernel.org Signed-off-by: Milo Kim --- Documentation/devicetree/bindings/mfd/ti-lmu.txt | 282 +++ 1 file

[PATCH V2 1/3] dma: add Qualcomm Technologies HIDMA management driver

The Qualcomm Technologies HIDMA device has been designed to support virtualization technology. The driver has been divided into two to follow the hardware design. The management driver is executed in hypervisor context and is the main management entity for all channels provided by the device. The

[PATCH V2 3/3] dma: add Qualcomm Technologies HIDMA channel driver

This patch adds support for hidma engine. The driver consists of two logical blocks. The DMA engine interface and the low-level interface. The hardware only supports memcpy/memset and this driver only support memcpy interface. HW and driver doesn't support slave interface. Signed-off-by: Sinan

[PATCH 16/16] regulator: add LM363X driver

LM363X regulator driver supports LM3631 and LM3632. LM3631 has 5 regulators. LM3632 provides 3 regulators. One boost output and LDOs are used for the display module. Boost voltage is configurable but always on. Supported operations for LDOs are enabled/disabled and voltage change. Two LDOs of

[PATCH 15/16] leds: add LM3633 driver

LM3633 LED driver supports generic LED functions and pattern generation. Pattern is generated through the sysfs. ABI documentation is also added. Device creation from device tree LED channel name, LED string usage and max current settings are configured inside

[PATCH 05/16] Documentation: dt-bindings: regulator: add LM363x regulator binding information

This binding supports LM3631 and LM3632 regulator configuration. Cc: devicetree@vger.kernel.org Cc: Lee Jones Cc: Mark Brown Cc: linux-ker...@vger.kernel.org Signed-off-by: Milo Kim --- .../bindings/regulator/lm363x-regulator.txt

[PATCH 13/16] backlight: ti-lmu-backlight: add LM3697 driver

LM3697 has 3 backlight strings and 11 bit dimming is supported. PWM brightness control is also supported. LM3697 MFD has HWMON driver which monitors hardware fault detection. After this monitoring is done, LM3697 backlight device should be reinitialized. To enable this, 'hwmon_notifier_used' is

[PATCH RESEND 02/16] Documentation: dt-bindings: backlight: add TI LMU backlight binding information

LM3532, LM3631, LM3632, LM3633, LM3695 and LM3697 use common dt-bindings for describing device. Cc: devicetree@vger.kernel.org Cc: Jingoo Han Cc: Lee Jones Cc: linux-ker...@vger.kernel.org Signed-off-by: Milo Kim ---

[PATCH 00/16] Support TI LMU devices

TI LMU(Lighting Management Unit) driver supports lighting devices below. Enable pin Backlights HWMON LEDs Regulators -- -- - LM3532 o o x xx LM3631 o o x x5

[PATCH RESEND 15/16] leds: add LM3633 driver

LM3633 LED driver supports generic LED functions and pattern generation. Pattern is generated through the sysfs. ABI documentation is also added. Device creation from device tree LED channel name, LED string usage and max current settings are configured inside

[PATCH RESEND 16/16] regulator: add LM363X driver

LM363X regulator driver supports LM3631 and LM3632. LM3631 has 5 regulators. LM3632 provides 3 regulators. One boost output and LDOs are used for the display module. Boost voltage is configurable but always on. Supported operations for LDOs are enabled/disabled and voltage change. Two LDOs of

[PATCH RESEND 07/16] backlight: add TI LMU backlight common driver

TI LMU backlight driver provides common driver features. Chip specific configuration is handled by each backlight driver such like LM3532, LM3631, LM3632, LM3633, LM3695 and LM3697. It supports common features as below. - Backlight subsystem control - Consistent device control flow -

[PATCH RESEND 09/16] backlight: ti-lmu-backlight: add LM3631 driver

LM3631 has 2 backlight strings and 11 bit dimming is supported. PWM brightness control is also supported. Common backlight driver is controlled by TI LMU backlight driver. Only LM3631 specific code is implemented here. Cc: Jingoo Han Cc: Lee Jones

[PATCH RESEND 14/16] hwmon: add TI LMU hardware fault monitoring driver

LM3633 and LM3697 are TI LMU MFD device. Those device have hardware monitoring feature which detects opened or shorted circuit case. Attributes -- Two attributes are registered. open_fault: check backlight output channel is opened or not short_fault: check backlight output