From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Rob Herring <robh@kernel.org>
Cc: Jacek Anaszewski <j.anaszewski@samsung.com>,
Jingoo Han <jingoohan1@gmail.com>,
Lee Jones <lee.jones@linaro.org>,
Linux LED Subsystem <linux-leds@vger.kernel.org>,
"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
Andrew Lunn <andrew@lunn.ch>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCHv4 3/3] devicetree: Add led-backlight binding
Date: Thu, 15 Oct 2015 12:17:37 +0000 [thread overview]
Message-ID: <561F9961.30008@ti.com> (raw)
In-Reply-To: <CAL_JsqJ+xYpX86DNHFCOEqV85FRh-Xzh1wg3p6guA0QeWG4+pg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2402 bytes --]
Hi Rob,
On 13/10/15 17:21, Rob Herring wrote:
> On Wed, Sep 30, 2015 at 4:32 AM, Tomi Valkeinen <tomi.valkeinen@ti.com> wrote:
>> Add DT binding for led-backlight.
>
> Please use get_maintainers.pl.
At some point I got feedback that the DT maintainers don't have time to
look at each individual driver binding, but rely on the subsystem
maintainers to handle them. Maybe I misunderstood that.
>> Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
>> Cc: devicetree@vger.kernel.org
>> ---
>> .../bindings/video/backlight/led-backlight.txt | 30 ++++++++++++++++++++++
>> 1 file changed, 30 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/video/backlight/led-backlight.txt
>>
>> diff --git a/Documentation/devicetree/bindings/video/backlight/led-backlight.txt b/Documentation/devicetree/bindings/video/backlight/led-backlight.txt
>> new file mode 100644
>> index 000000000000..d4621d7414bc
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/video/backlight/led-backlight.txt
>> @@ -0,0 +1,30 @@
>> +led-backlight bindings
>> +
>> +Required properties:
>> + - compatible: "led-backlight"
>> + - leds: phandle to a led OF node [0]
>
> Why do we need 2 levels of LED nodes?
Sorry, didn't get that. What do you mean with 2 levels?
>> + - brightness-levels: Array of distinct LED brightness levels. These
>> + are in the range from 0 to 255, passed to the LED class driver.
>> + - default-brightness-level: the default brightness level (index into the
>> + array defined by the "brightness-levels" property)
>> +
>> +Optional properties:
>> + - power-supply: regulator for supply voltage
>> + - enable-gpios: contains a single GPIO specifier for the GPIO which enables
>> + and disables the backlight (see GPIO binding[1])
>
> Why are all of these not part of the LED node pointed to by leds?
These are for the backlight, not for the LED chip. So "LED" here is a
chip that produces (most likely) a PWM signal, and "backlight" is the
collection of components that use the PWM to produce the backlight
itself, and use the power-supply and gpios.
> Describe the h/w, not what you want for a driver.
I think this describes the HW quite well. The LED chip works fine
without any of the properties here, and these are specific to the
backlight part of the board.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Rob Herring <robh@kernel.org>
Cc: Jacek Anaszewski <j.anaszewski@samsung.com>,
Jingoo Han <jingoohan1@gmail.com>,
Lee Jones <lee.jones@linaro.org>,
Linux LED Subsystem <linux-leds@vger.kernel.org>,
"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
Andrew Lunn <andrew@lunn.ch>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCHv4 3/3] devicetree: Add led-backlight binding
Date: Thu, 15 Oct 2015 15:17:37 +0300 [thread overview]
Message-ID: <561F9961.30008@ti.com> (raw)
In-Reply-To: <CAL_JsqJ+xYpX86DNHFCOEqV85FRh-Xzh1wg3p6guA0QeWG4+pg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2402 bytes --]
Hi Rob,
On 13/10/15 17:21, Rob Herring wrote:
> On Wed, Sep 30, 2015 at 4:32 AM, Tomi Valkeinen <tomi.valkeinen@ti.com> wrote:
>> Add DT binding for led-backlight.
>
> Please use get_maintainers.pl.
At some point I got feedback that the DT maintainers don't have time to
look at each individual driver binding, but rely on the subsystem
maintainers to handle them. Maybe I misunderstood that.
>> Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
>> Cc: devicetree@vger.kernel.org
>> ---
>> .../bindings/video/backlight/led-backlight.txt | 30 ++++++++++++++++++++++
>> 1 file changed, 30 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/video/backlight/led-backlight.txt
>>
>> diff --git a/Documentation/devicetree/bindings/video/backlight/led-backlight.txt b/Documentation/devicetree/bindings/video/backlight/led-backlight.txt
>> new file mode 100644
>> index 000000000000..d4621d7414bc
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/video/backlight/led-backlight.txt
>> @@ -0,0 +1,30 @@
>> +led-backlight bindings
>> +
>> +Required properties:
>> + - compatible: "led-backlight"
>> + - leds: phandle to a led OF node [0]
>
> Why do we need 2 levels of LED nodes?
Sorry, didn't get that. What do you mean with 2 levels?
>> + - brightness-levels: Array of distinct LED brightness levels. These
>> + are in the range from 0 to 255, passed to the LED class driver.
>> + - default-brightness-level: the default brightness level (index into the
>> + array defined by the "brightness-levels" property)
>> +
>> +Optional properties:
>> + - power-supply: regulator for supply voltage
>> + - enable-gpios: contains a single GPIO specifier for the GPIO which enables
>> + and disables the backlight (see GPIO binding[1])
>
> Why are all of these not part of the LED node pointed to by leds?
These are for the backlight, not for the LED chip. So "LED" here is a
chip that produces (most likely) a PWM signal, and "backlight" is the
collection of components that use the PWM to produce the backlight
itself, and use the power-supply and gpios.
> Describe the h/w, not what you want for a driver.
I think this describes the HW quite well. The LED chip works fine
without any of the properties here, and these are specific to the
backlight part of the board.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-10-15 12:17 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 9:31 [PATCHv4 0/3] backlight: led-backlight driver Tomi Valkeinen
2015-09-30 9:31 ` Tomi Valkeinen
2015-09-30 9:32 ` [PATCHv4 1/3] leds: Add of_led_get() and led_put() Tomi Valkeinen
2015-09-30 9:32 ` Tomi Valkeinen
2015-09-30 14:29 ` Jacek Anaszewski
2015-09-30 14:29 ` Jacek Anaszewski
2015-09-30 9:32 ` [PATCHv4 2/3] backlight: add led-backlight driver Tomi Valkeinen
2015-09-30 9:32 ` Tomi Valkeinen
2015-10-13 8:43 ` Lee Jones
2015-10-13 8:43 ` Lee Jones
2015-09-30 9:32 ` [PATCHv4 3/3] devicetree: Add led-backlight binding Tomi Valkeinen
2015-09-30 9:32 ` Tomi Valkeinen
2015-10-13 8:42 ` Lee Jones
2015-10-13 8:42 ` Lee Jones
2015-10-13 14:21 ` Rob Herring
2015-10-13 14:21 ` Rob Herring
2015-10-15 12:17 ` Tomi Valkeinen [this message]
2015-10-15 12:17 ` Tomi Valkeinen
2015-10-15 13:46 ` Rob Herring
2015-10-15 13:46 ` Rob Herring
2015-10-15 14:46 ` Tomi Valkeinen
2015-10-15 14:46 ` Tomi Valkeinen
2015-10-15 18:55 ` Rob Herring
2015-10-15 18:55 ` Rob Herring
2015-10-16 11:42 ` Tomi Valkeinen
2015-10-16 11:42 ` Tomi Valkeinen
2015-10-16 13:36 ` Rob Herring
2015-10-08 9:35 ` [PATCHv4 0/3] backlight: led-backlight driver Tomi Valkeinen
2015-10-08 9:35 ` Tomi Valkeinen
2015-10-08 10:09 ` Jacek Anaszewski
2015-10-08 10:09 ` Jacek Anaszewski
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=561F9961.30008@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=j.anaszewski@samsung.com \
--cc=jingoohan1@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=robh@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.