mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Astrid Rost <astrid.rost@axis.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Rob Herring <robh@kernel.org>,
	"Jacek Anaszewski" <jacek.anaszewski@gmail.com>,
	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 v2 1/2] led: led-class: Read max-brightness from devicetree
Date: Fri, 30 Jun 2023 11:22:46 +0200	[thread overview]
Message-ID: <20230630092248.4146169-2-astrid.rost@axis.com> (raw)
In-Reply-To: <20230630092248.4146169-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. Note that led-max-microamp should be preferably used, if it
is supported by the controller.

Signed-off-by: Astrid Rost <astrid.rost@axis.com>
---
 drivers/leds/led-class.c | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/drivers/leds/led-class.c b/drivers/leds/led-class.c
index 9255bc11f99d..ce652abf9336 100644
--- a/drivers/leds/led-class.c
+++ b/drivers/leds/led-class.c
@@ -457,6 +457,10 @@ int led_classdev_register_ext(struct device *parent,
 			if (fwnode_property_present(init_data->fwnode,
 						    "retain-state-shutdown"))
 				led_cdev->flags |= LED_RETAIN_AT_SHUTDOWN;
+
+			fwnode_property_read_u32(init_data->fwnode,
+				"max-brightness",
+				&led_cdev->max_brightness);
 		}
 	} else {
 		proposed_name = led_cdev->name;
-- 
2.30.2


       reply	other threads:[~2023-06-30  9:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230630092248.4146169-1-astrid.rost@axis.com>
2023-06-30  9:22 ` Astrid Rost [this message]
2023-06-30 17:59   ` Andy Shevchenko
2023-07-01 11:09   ` Jacek Anaszewski
2023-07-03  7:53     ` Astrid Rost
2023-07-03  9:32       ` Jacek Anaszewski
2023-06-30  9:22 ` [PATCH v2 2/2] dt-bindings: leds: " Astrid Rost
2023-06-30 16:49   ` Rob Herring

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=20230630092248.4146169-2-astrid.rost@axis.com \
    --to=astrid.rost@axis.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=jacek.anaszewski@gmail.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 \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®