From: Astrid Rost <astrid.rost@axis.com>
To: Dan Murphy <dmurphy@ti.com>, Andrew Davis <afd@ti.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Pavel Machek <pavel@ucw.cz>, Lee Jones <lee@kernel.org>
Cc: <kernel@axis.com>, Astrid Rost <astrid.rost@axis.com>,
<linux-leds@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH v1 1/2] led: leds-lp50xx: Add max-brightness as in leds-pwm
Date: Thu, 29 Jun 2023 15:47:21 +0200 [thread overview]
Message-ID: <20230629134722.3908637-2-astrid.rost@axis.com> (raw)
In-Reply-To: <20230629134722.3908637-1-astrid.rost@axis.com>
Add max-brightness in order to reduce the current on the connected LEDs.
Normally, the maximum brightness is determined by the hardware, and this
property is not required. This property is used to set a software limit.
It could happen that an LED is made so bright that it gets damaged or
causes damage due to restrictions in a specific system, such as mounting
conditions.
Signed-off-by: Astrid Rost <astrid.rost@axis.com>
---
drivers/leds/leds-lp50xx.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/leds/leds-lp50xx.c b/drivers/leds/leds-lp50xx.c
index 28d6b39fa72d..1cb54c0524a1 100644
--- a/drivers/leds/leds-lp50xx.c
+++ b/drivers/leds/leds-lp50xx.c
@@ -502,6 +502,8 @@ static int lp50xx_probe_dt(struct lp50xx *priv)
led->mc_cdev.num_colors = num_colors;
led->mc_cdev.subled_info = mc_led_info;
led_cdev = &led->mc_cdev.led_cdev;
+ fwnode_property_read_u32(child, "max-brightness",
+ &led_cdev->max_brightness);
led_cdev->brightness_set_blocking = lp50xx_brightness_set;
ret = devm_led_classdev_multicolor_register_ext(priv->dev,
--
2.30.2
next parent reply other threads:[~2023-06-29 13:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230629134722.3908637-1-astrid.rost@axis.com>
2023-06-29 13:47 ` Astrid Rost [this message]
2023-06-29 13:55 ` [PATCH v1 1/2] led: leds-lp50xx: Add max-brightness as in leds-pwm Andy Shevchenko
2023-06-29 13:47 ` [PATCH v1 2/2] dt: bindings: lp50xx: " Astrid Rost
2023-06-29 17:59 ` Rob Herring
2023-06-30 7:23 ` Astrid Rost
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=20230629134722.3908637-2-astrid.rost@axis.com \
--to=astrid.rost@axis.com \
--cc=afd@ti.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dmurphy@ti.com \
--cc=kernel@axis.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
/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