From: Jean-Jacques Hiblot <jjhiblot@ti.com>
To: <jacek.anaszewski@gmail.com>, <pavel@ucw.cz>,
<robh+dt@kernel.org>, <mark.rutland@arm.com>,
<lee.jones@linaro.org>, <daniel.thompson@linaro.org>,
<jingoohan1@gmail.com>
Cc: <dmurphy@ti.com>, <linux-leds@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <dri-devel@lists.freedesktop.org>,
<tomi.valkeinen@ti.com>, Jean-Jacques Hiblot <jjhiblot@ti.com>
Subject: [PATCH v4 3/4] dt-bindings: backlight: Add led-backlight binding
Date: Wed, 17 Jul 2019 16:15:13 +0200 [thread overview]
Message-ID: <20190717141514.21171-4-jjhiblot@ti.com> (raw)
In-Reply-To: <20190717141514.21171-1-jjhiblot@ti.com>
Add DT binding for led-backlight.
Signed-off-by: Jean-Jacques Hiblot <jjhiblot@ti.com>
---
.../bindings/leds/backlight/led-backlight.txt | 28 +++++++++++++++++++
1 file changed, 28 insertions(+)
create mode 100644 Documentation/devicetree/bindings/leds/backlight/led-backlight.txt
diff --git a/Documentation/devicetree/bindings/leds/backlight/led-backlight.txt b/Documentation/devicetree/bindings/leds/backlight/led-backlight.txt
new file mode 100644
index 000000000000..4c7dfbe7f67a
--- /dev/null
+++ b/Documentation/devicetree/bindings/leds/backlight/led-backlight.txt
@@ -0,0 +1,28 @@
+led-backlight bindings
+
+This binding is used to describe a basic backlight device made of LEDs.
+It can also be used to describe a backlight device controlled by the output of
+a LED driver.
+
+Required properties:
+ - compatible: "led-backlight"
+ - leds: a list of LEDs
+
+Optional properties:
+ - brightness-levels: Array of distinct brightness levels. The levels must be
+ in the range accepted by the underlying LED devices.
+ This is used to translate a backlight brightness level
+ into a LED brightness level. If it is not provided, the
+ identity mapping is used.
+
+ - default-brightness-level: The default brightness level.
+
+Example:
+
+ backlight {
+ compatible = "led-backlight";
+
+ leds = <&led1>, <&led2>;
+ brightness-levels = <0 4 8 16 32 64 128 255>;
+ default-brightness-level = <6>;
+ };
--
2.17.1
next prev parent reply other threads:[~2019-07-17 14:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-17 14:15 [PATCH v4 0/4] Add a generic driver for LED-based backlight Jean-Jacques Hiblot
2019-07-17 14:15 ` [PATCH v4 1/4] leds: Add of_led_get() and led_put() Jean-Jacques Hiblot
2019-07-30 11:02 ` Pavel Machek
2019-07-17 14:15 ` [PATCH v4 2/4] leds: Add managed API to get a LED from a device driver Jean-Jacques Hiblot
2019-07-31 13:23 ` Tomi Valkeinen
2019-07-17 14:15 ` Jean-Jacques Hiblot [this message]
2019-07-18 12:30 ` [PATCH v4 3/4] dt-bindings: backlight: Add led-backlight binding Jacek Anaszewski
2019-07-17 14:15 ` [PATCH v4 4/4] backlight: add led-backlight driver Jean-Jacques Hiblot
2019-09-09 9:53 ` Daniel Thompson
2019-07-18 13:19 ` [PATCH v4 0/4] Add a generic driver for LED-based backlight Jacek Anaszewski
2019-07-22 7:06 ` Lee Jones
2019-07-22 21:23 ` Jacek Anaszewski
2019-09-08 16:17 ` Jacek Anaszewski
2019-09-09 11:12 ` Daniel Thompson
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=20190717141514.21171-4-jjhiblot@ti.com \
--to=jjhiblot@ti.com \
--cc=daniel.thompson@linaro.org \
--cc=dmurphy@ti.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jacek.anaszewski@gmail.com \
--cc=jingoohan1@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.org \
--cc=tomi.valkeinen@ti.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).