From: Martin Kurbanov <mmkurbanov@sberdevices.ru>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Pavel Machek <pavel@ucw.cz>, Lee Jones <lee@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
<linux-leds@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<kernel@sberdevices.ru>, <devicetree@vger.kernel.org>
Subject: Re: [PATCH v3 2/2] leds: add aw20xx driver
Date: Tue, 14 Mar 2023 15:12:29 +0300 [thread overview]
Message-ID: <3b920b9e-07dc-7bda-4fe1-d15d07e708cc@sberdevices.ru> (raw)
In-Reply-To: <20230314120252.48263-3-mmkurbanov@sberdevices.ru>
Hello Andy. Thank you for review.
I have fixed most of your comments. Please take a look below.
On 2023-03-01 00:51, Andy Shevchenko wrote:
>> + /* The output current of each LED (see p.14 of datasheet for formula) */
>> + return (duty * global_imax_microamp) / 1000U;
>
> units.h ?
These constants are needed to improve the accuracy of calculations.
units.h doesn’t have any helpful definitions to use here.
>> +static int aw200xx_set_imax(const struct aw200xx *const chip,
>> + u32 led_imax_microamp)
>> +{
>> + struct imax_global {
>> + u32 regval;
>> + u32 microamp;
>> + } imaxs[] = {
>> + { 8, 3300 },
>> + { 9, 6700 },
>> + { 0, 10000 },
>> + { 11, 13300 },
>> + { 1, 20000 },
>> + { 13, 26700 },
>> + { 2, 30000 },
>> + { 3, 40000 },
>> + { 15, 53300 },
>> + { 4, 60000 },
>> + { 5, 80000 },
>> + { 6, 120000 },
>> + { 7, 160000 },
>
> This looks a bit random. Is there any pattern on how value is
> connected to the register value?
There is no ability to create any pattern here, because this table data
doesn’t have any regularity.
--
Best Regards,
Kurbanov Martin
next prev parent reply other threads:[~2023-03-14 12:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 12:02 [PATCH v3 0/2] " Martin Kurbanov
2023-03-14 12:02 ` [PATCH v3 1/2] dt-bindings: leds: add binding for aw200xx Martin Kurbanov
2023-03-16 7:11 ` Krzysztof Kozlowski
2023-03-16 16:40 ` Lee Jones
2023-03-16 19:54 ` Martin Kurbanov
2023-03-17 8:09 ` Lee Jones
2023-03-14 12:02 ` [PATCH v3 2/2] leds: add aw20xx driver Martin Kurbanov
2023-03-14 12:12 ` Martin Kurbanov [this message]
2023-03-14 16:22 ` Andy Shevchenko
2023-03-14 16:49 ` Andy Shevchenko
2023-03-14 16:44 ` Andy Shevchenko
2023-03-15 9:59 ` kernel test robot
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=3b920b9e-07dc-7bda-4fe1-d15d07e708cc@sberdevices.ru \
--to=mmkurbanov@sberdevices.ru \
--cc=andy.shevchenko@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@sberdevices.ru \
--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+dt@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®