linux-leds.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nam Tran <trannamatk@gmail.com>
To: christophe.jaillet@wanadoo.fr
Cc: lee@kernel.org, pavel@kernel.org, krzk+dt@kernel.org,
	robh@kernel.org, conor+dt@kernel.org, corbet@lwn.net,
	linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v9 2/4] leds: add TI/National Semiconductor LP5812 LED Driver
Date: Wed, 18 Jun 2025 00:30:03 +0700	[thread overview]
Message-ID: <20250617173003.28933-1-trannamatk@gmail.com> (raw)
In-Reply-To: <42676fe3-8758-42ea-8e21-9c3955468c78@wanadoo.fr>

On Tue, 10 Jun 2025, Christophe JAILLET wrote:

> > +static struct lp5812_data *lp5812_of_populate_pdata(struct device *dev,
> > +						    struct device_node *np,
> > +						    struct lp5812_chip *chip)
> > +{
> > +	struct device_node *child;
> > +	struct lp5812_data *pdata;
> > +	struct lp5812_led_config *cfg;
> > +	int num_channels, i = 0, ret;
> > +
> > +	pdata = devm_kzalloc(dev, sizeof(*pdata), GFP_KERNEL);
> > +	if (!pdata)
> > +		return ERR_PTR(-ENOMEM);
> > +
> > +	num_channels = of_get_available_child_count(np);
> > +	if (num_channels == 0) {
> > +		dev_err(dev, "no LED channels\n");
> > +		return ERR_PTR(-EINVAL);
> > +	}
> > +
> > +	cfg = devm_kcalloc(dev, num_channels, sizeof(*cfg), GFP_KERNEL);
> > +	if (!cfg)
> > +		return ERR_PTR(-ENOMEM);
> > +
> > +	pdata->led_config = &cfg[0];
> > +	pdata->num_channels = num_channels;
> > +
> > +	for_each_available_child_of_node(np, child) {
> 
> Maybe for_each_available_child_of_node_scoped() to slihtly simplify the 
> code?

Thanks, I'll switch to for_each_available_child_of_node_scoped().

> > +static ssize_t lp5812_aeu_slope_time(struct device *dev,
> > +				     struct device_attribute *attr,
> > +				     enum slope_time_num slope_chan,
> > +				     const char *buf, size_t len)
> > +{
> > +	struct lp5812_led *led;
> > +	struct lp5812_chip *chip;
> > +	struct lp5812_led_config *led_cfg;
> > +	const char *name = dev->platform_data;
> > +	int val[LED_COLOR_ID_MAX];
> > +	u8 chan_nr = 0;
> > +	char *sub_str, *str = (char *)buf;
> > +	int i, ret, aeu;
> > +	union slope_time slope_time_val;
> > +	u16 reg;
> > +
> > +	if (strcmp(name, LP5812_SC_LED) == 0)
> > +		led = dev_to_lp5812_led(dev);
> > +	else
> > +		led = dev_to_lp5812_led_mc(dev);
> > +
> > +	chan_nr = led->chan_nr;
> > +	chip = led->chip;
> > +	led_cfg = &chip->pdata->led_config[chan_nr];
> > +
> > +	sub_str = strsep(&str, ":");
> > +	if (!sub_str)
> > +		return -EINVAL;
> > +	if (kstrtoint(&sub_str[3], 0, &aeu))
> > +		return -EINVAL;
> > +
> > +	pr_info("AEU = %d", aeu);
> > +
> > +	guard(mutex)(&chip->lock);
> > +	for (i = 0; i < led_cfg->num_colors; i++) {
> > +		sub_str = strsep(&str, " ");
> > +		if (!sub_str)
> > +			return -EINVAL;
> > +		if (kstrtoint(sub_str, 0, &val[i]))
> > +			return -EINVAL;
> > +		if (val[i] < 0 || val[i] > 15)
> > +			return -EINVAL;
> > +
> > +		reg = LP5812_AEU_SLOPE_TIME_ADDR(led_cfg->led_id[i], aeu, slope_chan);
> > +
> > +		/* get original value of slope time */
> > +		ret = lp5812_read(chip, reg, &slope_time_val.time_val);
> > +		if (ret)
> > +			return ret;
> > +
> > +		/* Update new value for slope time*/
> > +		if (slope_chan == LP5812_SLOPE_TIME_T1 || slope_chan == LP5812_SLOPE_TIME_T3)
> > +			slope_time_val.s_time.first = val[i];
> > +		if (slope_chan == LP5812_SLOPE_TIME_T2 || slope_chan == LP5812_SLOPE_TIME_T4)
> > +			slope_time_val.s_time.second = val[i];
> > +
> > +		/* Save updated value to hardware */
> > +		ret = lp5812_write(chip, reg, slope_time_val.time_val);
> 
> Should we do something if ret != 0?

Yes. I'll add a return check to handle possible write errors.

> > +static struct attribute *lp5812_led_attrs[] = {
> > +	&dev_attr_led_current.attr,
> > +	&dev_attr_max_current.attr,
> > +	&dev_attr_mode.attr,
> > +	&dev_attr_activate.attr,
> > +	&dev_attr_pwm_dimming_scale.attr,
> > +	&dev_attr_pwm_phase_align.attr,
> > +	&dev_attr_auto_time_pause_at_start.attr,
> > +	&dev_attr_auto_time_pause_at_stop.attr,
> > +	&dev_attr_auto_playback_eau_number.attr,
> > +	&dev_attr_auto_playback_time.attr,
> > +	&dev_attr_aeu_playback_time.attr,
> > +	&dev_attr_aeu_pwm1.attr,
> > +	&dev_attr_aeu_pwm2.attr,
> > +	&dev_attr_aeu_pwm3.attr,
> > +	&dev_attr_aeu_pwm4.attr,
> > +	&dev_attr_aeu_pwm5.attr,
> > +	&dev_attr_aeu_slop_time_t1.attr,
> > +	&dev_attr_aeu_slop_time_t2.attr,
> > +	&dev_attr_aeu_slop_time_t3.attr,
> > +	&dev_attr_aeu_slop_time_t4.attr,
> > +	&dev_attr_lod_lsd.attr,
> > +	NULL,
> 
> Unneeded trailing comma after a terminator.

I'll remove it.

> > +static int lp5812_init_led(struct lp5812_led *led, struct lp5812_chip *chip, int chan)
> > +{
> > +	struct lp5812_data *pdata = chip->pdata;
> > +	struct device *dev = &chip->i2c_cl->dev;
> > +	struct mc_subled *mc_led_info;
> > +	struct led_classdev *led_cdev;
> > +	char name[32];
> > +	int i, ret = 0;
> > +
> > +	if (pdata->led_config[chan].name) {
> > +		led->cdev.name = pdata->led_config[chan].name;
> > +	} else {
> > +		snprintf(name, sizeof(name), "%s:channel%d",
> > +			 pdata->label ? : chip->i2c_cl->name, chan);
> > +		led->cdev.name = name;
> 
> Is it fine below when 'name' is defined on the stack and is used...
> 
> > +	}
> > +
> > +	if (pdata->led_config[chan].is_sc_led == 0) {
> > +		mc_led_info = devm_kcalloc(dev,
> > +					   pdata->led_config[chan].num_colors,
> > +					   sizeof(*mc_led_info), GFP_KERNEL);
> > +		if (!mc_led_info)
> > +			return -ENOMEM;
> > +
> > +		led_cdev = &led->mc_cdev.led_cdev;
> > +		led_cdev->name = led->cdev.name;
> 
> ...here?

You're right, name was stack-allocated and unsafe to use after the function returns.
I'll replace it with a devm_kasprintf() allocation.

Appreciate your time and feedback.

Best regards,
Nam Tran

  reply	other threads:[~2025-06-17 17:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-10 17:43 [PATCH v9 0/4] leds: add new LED driver for TI LP5812 Nam Tran
2025-06-10 17:43 ` [PATCH v9 1/4] dt-bindings: leds: add TI/National Semiconductor LP5812 LED Driver Nam Tran
2025-06-11  8:24   ` Krzysztof Kozlowski
2025-06-17 16:29     ` Nam Tran
2025-06-10 17:43 ` [PATCH v5] test Nam Tran
2025-06-12 10:03   ` Lee Jones
2025-06-17 17:46     ` Nam Tran
2025-06-10 17:43 ` [PATCH v9 2/4] leds: add TI/National Semiconductor LP5812 LED Driver Nam Tran
2025-06-10 18:13   ` Randy Dunlap
2025-06-17 16:50     ` Nam Tran
2025-06-10 21:07   ` Christophe JAILLET
2025-06-17 17:30     ` Nam Tran [this message]
2025-06-16 18:37   ` kernel test robot
2025-06-10 17:43 ` [PATCH v9 3/4] docs: ABI: Document LP5812 LED sysfs interfaces Nam Tran
2025-06-10 17:43 ` [PATCH v9 4/4] docs: leds: Document TI LP5812 LED driver Nam Tran
2025-06-10 17:55 ` [PATCH v9 0/4] leds: add new LED driver for TI LP5812 Nam Tran
2025-06-11  6:59 ` Krzysztof Kozlowski
2025-06-17 15:40   ` Nam Tran

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=20250617173003.28933-1-trannamatk@gmail.com \
    --to=trannamatk@gmail.com \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=conor+dt@kernel.org \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=pavel@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).