From: Dan Murphy <dmurphy@ti.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: <robh+dt@kernel.org>, <jacek.anaszewski@gmail.com>,
<lee.jones@linaro.org>, <tony@atomide.com>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-leds@vger.kernel.org>
Subject: Re: [PATCH v3 2/9] dt-bindings: ti-lmu: Remove LM3697
Date: Thu, 11 Oct 2018 13:34:51 -0500 [thread overview]
Message-ID: <4fcb91c7-b2b2-798d-8a41-fa1b475086e0@ti.com> (raw)
In-Reply-To: <20181011182734.GA7973@amd>
Pavel
On 10/11/2018 01:27 PM, Pavel Machek wrote:
> On Thu 2018-10-11 11:51:16, Dan Murphy wrote:
>> Remove support for the LM3697 LED device
>> from the ti-lmu. The LM3697 will be supported
>> via a stand alone LED driver.
>>
>> Signed-off-by: Dan Murphy <dmurphy@ti.com>
>
> NAK.
Thanks for the NAK.
This NAK was NAK'd by other maintainer in the V2 RFC patchset
https://lore.kernel.org/patchwork/patch/993171/
>
> Pavel
>
>> index c885cf89b8ce..920f910be4e9 100644
>> --- a/Documentation/devicetree/bindings/mfd/ti-lmu.txt
>> +++ b/Documentation/devicetree/bindings/mfd/ti-lmu.txt
>> @@ -9,7 +9,6 @@ TI LMU driver supports lighting devices below.
>> LM3632 Backlight and regulator
>> LM3633 Backlight, LED and fault monitor
>> LM3695 Backlight
>> - LM3697 Backlight and fault monitor
>>
>> Required properties:
>> - compatible: Should be one of:
>> @@ -18,11 +17,10 @@ Required properties:
>> "ti,lm3632"
>> "ti,lm3633"
>> "ti,lm3695"
>> - "ti,lm3697"
>> - reg: I2C slave address.
>> 0x11 for LM3632
>> 0x29 for LM3631
>> - 0x36 for LM3633, LM3697
>> + 0x36 for LM3633
>> 0x38 for LM3532
>> 0x63 for LM3695
>>
>> @@ -38,7 +36,6 @@ Optional nodes:
>> Required properties:
>> - compatible: Should be one of:
>> "ti,lm3633-fault-monitor"
>> - "ti,lm3697-fault-monitor"
>> - leds: LED properties for LM3633. Please refer to [2].
>> - regulators: Regulator properties for LM3631 and LM3632.
>> Please refer to [3].
>> @@ -220,24 +217,3 @@ lm3695@63 {
>> };
>> };
>> };
>> -
>> -lm3697@36 {
>> - compatible = "ti,lm3697";
>> - reg = <0x36>;
>> -
>> - enable-gpios = <&pioC 2 GPIO_ACTIVE_HIGH>;
>> -
>> - backlight {
>> - compatible = "ti,lm3697-backlight";
>> -
>> - lcd {
>> - led-sources = <0 1 2>;
>> - ramp-up-msec = <200>;
>> - ramp-down-msec = <200>;
>> - };
>> - };
>> -
>> - fault-monitor {
>> - compatible = "ti,lm3697-fault-monitor";
>> - };
>> -};
>
--
------------------
Dan Murphy
next prev parent reply other threads:[~2018-10-11 18:35 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 16:51 [PATCH v3 0/9] TI LMU common Framework Dan Murphy
2018-10-11 16:51 ` [PATCH v3 1/9] leds: add TI LMU backlight driver Dan Murphy
2018-10-11 16:51 ` [PATCH v3 2/9] dt-bindings: ti-lmu: Remove LM3697 Dan Murphy
2018-10-11 18:27 ` Pavel Machek
2018-10-11 18:34 ` Dan Murphy [this message]
2018-10-11 19:38 ` Jacek Anaszewski
2018-10-12 16:26 ` Rob Herring
2018-10-12 18:03 ` Pavel Machek
2018-10-13 18:45 ` Jacek Anaszewski
2018-10-15 0:56 ` Rob Herring
2018-10-15 19:13 ` Jacek Anaszewski
2018-10-15 19:14 ` Dan Murphy
2018-10-15 21:45 ` Pavel Machek
2018-10-16 13:25 ` Dan Murphy
2018-10-18 22:10 ` Pavel Machek
2018-10-19 11:42 ` Dan Murphy
2018-10-19 14:58 ` Tony Lindgren
2018-10-24 8:55 ` Pavel Machek
2018-10-12 9:07 ` Lee Jones
2018-10-11 16:51 ` [PATCH v3 3/9] mfd: ti-lmu: Remove support for LM3697 Dan Murphy
2018-10-11 16:51 ` [PATCH v3 4/9] dt-bindings: leds: Add bindings for lm3697 driver Dan Murphy
2018-10-12 16:27 ` Rob Herring
2018-10-19 11:47 ` Dan Murphy
2018-10-11 16:51 ` [PATCH v3 5/9] leds: lm3697: Introduce the " Dan Murphy
2018-10-11 16:51 ` [PATCH v3 6/9] dt-bindings: ti-lmu: Remove LM3633 Dan Murphy
2018-10-11 16:51 ` [PATCH v3 7/9] mfd: ti-lmu: Remove support for LM3633 Dan Murphy
2018-10-11 16:51 ` [PATCH v3 8/9] dt-bindings: leds: Add support for the LM3633 Dan Murphy
2018-10-11 16:51 ` [PATCH v3 9/9] leds: lm3633: Introduce the lm3633 driver Dan Murphy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4fcb91c7-b2b2-798d-8a41-fa1b475086e0@ti.com \
--to=dmurphy@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=jacek.anaszewski@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.org \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).