From: Abdel Alkuor <alkuor@gmail.com>
To: Lee Jones <lee@kernel.org>
Cc: "Pavel Machek" <pavel@ucw.cz>, "Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Alice Chen" <alice_chen@richtek.com>,
"Jean-Jacques Hiblot" <jjhiblot@traphandler.com>,
"ChiYuan Huang" <cy_huang@richtek.com>,
"ChiaEn Wu" <chiaen_wu@richtek.com>,
"Lukas Bulwahn" <lukas.bulwahn@gmail.com>,
"André Apitzsch" <git@apitzsch.eu>,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] leds: Add NCP5623 multi-led driver
Date: Mon, 4 Mar 2024 22:29:41 -0500 [thread overview]
Message-ID: <ZeaRpSrkeFKAXIlq@abdel> (raw)
In-Reply-To: <20240301085046.GE1209090@google.com>
On Fri, Mar 01, 2024 at 08:50:46AM +0000, Lee Jones wrote:
Hi Lee,
> > +#define NCP5623_REG(x) ((x) << 0x5)
>
> What's 0x5? Probably worth defining.
This is a function offset. I'll add a define.
>
> > + guard(mutex)(&ncp->lock);
>
> Are these self-unlocking?
Correct. Here is a short introduction about it
https://www.marcusfolkesson.se/blog/mutex-guards-in-the-linux-kernel/
>
> > + ncp->old_brightness = brightness;
>
> The nomenclature is confusing here.
>
> For the most part, this will carry the present value, no?
>
Yes, I'll change it to current_brightness instead
> > + ret = ncp5623_write(ncp->client,
> > + NCP5623_DIMMING_TIME_REG, pattern[0].delta_t / 8);
>
> Why 8? Magic numbers should be replaced with #defines.
>
This is dim step in ms. I'll add a define for it.
> > +static int ncp5623_pattern_clear(struct led_classdev *led_cdev)
> > +{
> > + return 0;
> > +}
>
> Not sure I see the point in this.
>
> Is the .pattern_clear() compulsorily?
>
Unfortunately, it is. For example, in pattern_trig_store_patterns, when
hw pattern is used, it is expected to have pattern_clear implemented.
static ssize_t pattern_trig_store_patterns(struct led_classdev *led_cdev,
const char *buf, const u32 *buf_int,
size_t count, bool hw_pattern)
{
...
if (data->is_hw_pattern)
led_cdev->pattern_clear(led_cdev);
...
}
> > + init_data.fwnode = mc_node;
> > +
> > + ncp->mc_dev.led_cdev.max_brightness = NCP5623_MAX_BRIGHTNESS;
> > + ncp->mc_dev.subled_info = subled_info;
> > + ncp->mc_dev.led_cdev.brightness_set_blocking = ncp5623_brightness_set;
> > + ncp->mc_dev.led_cdev.pattern_set = ncp5623_pattern_set;
> > + ncp->mc_dev.led_cdev.pattern_clear = ncp5623_pattern_clear;
> > + ncp->mc_dev.led_cdev.default_trigger = "pattern";
> > +
> > + mutex_init(&ncp->lock);
> > + i2c_set_clientdata(client, ncp);
> > +
> > + ret = led_classdev_multicolor_register_ext(dev, &ncp->mc_dev, &init_data);
> > + if (ret)
> > + goto destroy_lock;
> > +
> > + fwnode_handle_put(mc_node);
>
> Didn't you just store this ~16 lines up?
>
Ops! I'll remove it.
Thanks,
Abdel
next prev parent reply other threads:[~2024-03-05 3:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-17 23:09 [PATCH v2 1/2] dt-bindings: leds: Add NCP5623 multi-LED Controller Abdel Alkuor
2024-02-17 23:09 ` [PATCH v2 2/2] leds: Add NCP5623 multi-led driver Abdel Alkuor
2024-03-01 8:50 ` Lee Jones
2024-03-05 3:29 ` Abdel Alkuor [this message]
2024-03-05 9:04 ` Lee Jones
2024-02-20 10:03 ` [PATCH v2 1/2] dt-bindings: leds: Add NCP5623 multi-LED Controller Krzysztof Kozlowski
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=ZeaRpSrkeFKAXIlq@abdel \
--to=alkuor@gmail.com \
--cc=alice_chen@richtek.com \
--cc=chiaen_wu@richtek.com \
--cc=conor+dt@kernel.org \
--cc=cy_huang@richtek.com \
--cc=devicetree@vger.kernel.org \
--cc=git@apitzsch.eu \
--cc=jjhiblot@traphandler.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).