All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiner Kallweit <hkallweit1@gmail.com>
To: Lee Jones <lee@kernel.org>
Cc: Pavel Machek <pavel@ucw.cz>,
	"linux-leds@vger.kernel.org" <linux-leds@vger.kernel.org>,
	Andrew Lunn <andrew@lunn.ch>,
	Christian Marangi <ansuelsmth@gmail.com>
Subject: Re: [PATCH v3] leds: trigger: netdev: skip setting baseline state in activate if hw-controlled
Date: Thu, 21 Dec 2023 18:26:47 +0100	[thread overview]
Message-ID: <ec4b2852-9b76-4f0a-b296-cc5577ca4647@gmail.com> (raw)
In-Reply-To: <20231221162731.GQ10102@google.com>

On 21.12.2023 17:27, Lee Jones wrote:
> On Thu, 21 Dec 2023, Heiner Kallweit wrote:
> 
>> The current codes uses the sw_control path in set_baseline_state() when
>> called from netdev_trig_activate() even if we're hw-controlled. This
>> may result in errors when led_set_brightness() is called because we may
>> not have set_brightness led ops (if hw doesn't support setting a "LED"
>> to ON). In addition this path may schedule trigger_data->work which
>> doesn't make sense when being hw-controlled.
>>
>> Therefore set trigger_data->hw_control = true before calling
>> set_device_name() from netdev_trig_activate(). In this call chain we
>> have to prevent set_baseline_state() from being called, because this
>> would call hw_control_set(). Use led_cdev->trigger_data == NULL as
>> indicator for being called from netdev_trig_activate().
>>
>> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
>> ---
>> v2:
>> - improve commit message
>> v3:
>> - spelling and style fixes
>> ---
>>  drivers/leds/trigger/ledtrig-netdev.c | 7 +++++--
>>  1 file changed, 5 insertions(+), 2 deletions(-)
> 
> Doesn't apply.  Please rebase it on top of the LEDs repo.
> 
It's because fe2b1226656a ("leds: trigger: netdev: fix RTNL handling to
prevent potential deadlock") was applied via the netdev tree.
I'll rebase on top of for-leds-next.

> https://git.kernel.org/pub/scm/linux/kernel/git/lee/leds.git/
> 
>> diff --git a/drivers/leds/trigger/ledtrig-netdev.c b/drivers/leds/trigger/ledtrig-netdev.c
>> index 09e75fd9f..6cbba44dd 100644
>> --- a/drivers/leds/trigger/ledtrig-netdev.c
>> +++ b/drivers/leds/trigger/ledtrig-netdev.c
>> @@ -267,7 +267,10 @@ static int set_device_name(struct led_netdev_data *trigger_data,
>>  
>>  	trigger_data->last_activity = 0;
>>  
>> -	set_baseline_state(trigger_data);
>> +	/* Skip if we're called from netdev_trig_activate() and hw_control is true */
>> +	if (!trigger_data->hw_control || led_get_trigger_data(trigger_data->led_cdev))
>> +		set_baseline_state(trigger_data);
>> +
>>  	mutex_unlock(&trigger_data->lock);
>>  	rtnl_unlock();
>>  
>> @@ -602,8 +605,8 @@ static int netdev_trig_activate(struct led_classdev *led_cdev)
>>  		if (dev) {
>>  			const char *name = dev_name(dev);
>>  
>> -			set_device_name(trigger_data, name, strlen(name));
>>  			trigger_data->hw_control = true;
>> +			set_device_name(trigger_data, name, strlen(name));
>>  
>>  			rc = led_cdev->hw_control_get(led_cdev, &mode);
>>  			if (!rc)
>> -- 
>> 2.43.0
> 


      reply	other threads:[~2023-12-21 17:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-21 15:43 [PATCH v3] leds: trigger: netdev: skip setting baseline state in activate if hw-controlled Heiner Kallweit
2023-12-21 16:27 ` Lee Jones
2023-12-21 17:26   ` Heiner Kallweit [this message]

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=ec4b2852-9b76-4f0a-b296-cc5577ca4647@gmail.com \
    --to=hkallweit1@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=ansuelsmth@gmail.com \
    --cc=lee@kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.