From: "Michal Vokáč" <michal.vokac@ysoft.com>
To: Pavel Machek <pavel@ucw.cz>, Lee Jones <lee@kernel.org>
Cc: Dan Murphy <dmurphy@ti.com>,
Jacek Anaszewski <jacek.anaszewski@gmail.com>,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, Christian Marangi <ansuelsmth@gmail.com>
Subject: Re: [PATCH] leds: lp55xx: Fix check for invalid channel number
Date: Wed, 9 Oct 2024 11:56:31 +0200 [thread overview]
Message-ID: <cb3550f1-06c8-4e22-ae23-a738b61192fd@ysoft.com> (raw)
In-Reply-To: <1728464547-31722-1-git-send-email-michal.vokac@ysoft.com>
+Cc Christian Marangi as I see he contributed a lot to this driver recently.
I also see that Dan Murphy can not be reached on the ti.com e-mail as he
works for Abbott since 2021 according to linkedin..
On 09. 10. 24 11:02, Michal Vokáč wrote:
> Prior to commit 92a81562e695 ("leds: lp55xx: Add multicolor framework
> support to lp55xx") the reg property (chan_nr) was parsed and stored
> as it was. Then, in lp55xx_init_led() function, it was checked if it
> is within valid range. In case it was not, an error message was
> printed and the driver probe failed.
>
> With the mentioned commit the reg property is checked right after it
> is read from the device tree. Comparison to the upper range is not
> correct though. Valid reg values are 0 to (max_channel - 1). So in
> case the parsed value is out of this (wrong) range the probe just
> fails and no error message is shown.
>
> Fix it by using proper comparison and print a message in case of
> an error. The check that is done in lp55xx_init_led() function is now
> redundant and can be removed.
>
> Fixes: 92a81562e695 ("leds: lp55xx: Add multicolor framework support to lp55xx")
> Cc: <stable@vger.kernel.org>
> Signed-off-by: Michal Vokáč <michal.vokac@ysoft.com>
> ---
> drivers/leds/leds-lp55xx-common.c | 11 ++++-------
> 1 file changed, 4 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/leds/leds-lp55xx-common.c b/drivers/leds/leds-lp55xx-common.c
> index 5a2e259679cf..055ee77455f9 100644
> --- a/drivers/leds/leds-lp55xx-common.c
> +++ b/drivers/leds/leds-lp55xx-common.c
> @@ -512,12 +512,6 @@ static int lp55xx_init_led(struct lp55xx_led *led,
> led->max_current = pdata->led_config[chan].max_current;
> led->chan_nr = pdata->led_config[chan].chan_nr;
>
> - if (led->chan_nr >= max_channel) {
> - dev_err(dev, "Use channel numbers between 0 and %d\n",
> - max_channel - 1);
> - return -EINVAL;
> - }
> -
> if (pdata->led_config[chan].num_colors > 1)
> ret = devm_led_classdev_multicolor_register(dev, &led->mc_cdev);
> else
> @@ -1132,8 +1126,11 @@ static int lp55xx_parse_common_child(struct device_node *np,
> if (ret)
> return ret;
>
> - if (*chan_nr < 0 || *chan_nr > cfg->max_channel)
> + if (*chan_nr < 0 || *chan_nr >= cfg->max_channel) {
> + dev_err(dev, "Use channel numbers between 0 and %d\n",
> + cfg->max_channel - 1);
> return -EINVAL;
> + }
>
> return 0;
> }
next prev parent reply other threads:[~2024-10-09 9:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 9:02 [PATCH] leds: lp55xx: Fix check for invalid channel number Michal Vokáč
2024-10-09 9:56 ` Michal Vokáč [this message]
2024-10-10 6:00 ` kernel test robot
2024-10-10 7:16 ` Michal Vokáč
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=cb3550f1-06c8-4e22-ae23-a738b61192fd@ysoft.com \
--to=michal.vokac@ysoft.com \
--cc=ansuelsmth@gmail.com \
--cc=dmurphy@ti.com \
--cc=jacek.anaszewski@gmail.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=stable@vger.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