public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Astrid Rost <astridr@axis.com>,
	Astrid Rost <astrid.rost@axis.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Rob Herring <robh@kernel.org>, Pavel Machek <pavel@ucw.cz>,
	Lee Jones <lee@kernel.org>
Cc: kernel@axis.com, linux-leds@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] led: led-class: Read max-brightness from devicetree
Date: Mon, 3 Jul 2023 11:32:10 +0200	[thread overview]
Message-ID: <0d2dcb62-8475-8b2a-7ba9-bdabab3d0aa4@gmail.com> (raw)
In-Reply-To: <abcfb68b-b631-8a7b-e7cb-daefc58f3dde@axis.com>

Hi Astrid,

On 7/3/23 09:53, Astrid Rost wrote:
> Hello Jacek,
> 
> I am having problems with the PWM controller LP5024.
> 
> https://www.ti.com/product/LP5024
> 
> There is no such a calculation in the data-sheet like:
> max_brightness = max_current / constant.
> 
> I also assume it is depending on the type of LEDs and circuit, which are 
> connected.
> 
> It supports two current modes: 25,5 mA and and 35 mA, both is to high 
> for the LEDs I have.
> 
> For max_brightness seems to be everything inside the kernel, but reading 
> the value from devicetree. I first thought I could add it in the lp50xx
> driver, but Andy and Rob thought that I better put it into the general 
> parts. And of course drivers having led-max-microamp should better use it.
> 
> Please, let me know if you have a better suggestion.

OK, since this LED controller is PWM-driven then there is no current per
brightness level granulation. Bindings of leds-pwm driver also use
max-brightness DT property. So, yeah, let's make it a common property,
but state clearly that it is mainly for drivers like PWM ones, where it
is not possible to map brightness level to the amount of current.

-- 
Best regards,
Jacek Anaszewski

  reply	other threads:[~2023-07-03  9:32 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 ` [PATCH v2 1/2] led: led-class: Read max-brightness from devicetree Astrid Rost
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 [this message]
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=0d2dcb62-8475-8b2a-7ba9-bdabab3d0aa4@gmail.com \
    --to=jacek.anaszewski@gmail.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=astrid.rost@axis.com \
    --cc=astridr@axis.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