From: Lee Jones <lee@kernel.org>
To: Heiner Kallweit <hkallweit1@gmail.com>
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 v2] leds: trigger: netdev: skip setting baseline state in activate if hw-controlled
Date: Thu, 21 Dec 2023 15:16:53 +0000 [thread overview]
Message-ID: <20231221151653.GK10102@google.com> (raw)
In-Reply-To: <91f7f2aa-b666-450a-b970-967b1b06fe9a@gmail.com>
On Mon, 18 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
"LED"
> to ON). In addition this path may schedule trigger_data->work what
s/what/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
> ---
> drivers/leds/trigger/ledtrig-netdev.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/leds/trigger/ledtrig-netdev.c b/drivers/leds/trigger/ledtrig-netdev.c
> index 7ed2d0b64..b58396600 100644
> --- a/drivers/leds/trigger/ledtrig-netdev.c
> +++ b/drivers/leds/trigger/ledtrig-netdev.c
> @@ -251,7 +251,11 @@ 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 */
Nit: Sentences start with an uppercase char.
> + if (!trigger_data->hw_control ||
> + led_get_trigger_data(trigger_data->led_cdev))
Nit: Place this all on a single line.
> + set_baseline_state(trigger_data);
> +
> mutex_unlock(&trigger_data->lock);
> rtnl_unlock();
>
> @@ -568,8 +572,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
>
>
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2023-12-21 15:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 16:01 [PATCH v2] leds: trigger: netdev: skip setting baseline state in activate if hw-controlled Heiner Kallweit
2023-12-21 15:16 ` Lee Jones [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=20231221151653.GK10102@google.com \
--to=lee@kernel.org \
--cc=andrew@lunn.ch \
--cc=ansuelsmth@gmail.com \
--cc=hkallweit1@gmail.com \
--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 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 read-only IMAP folder(s) and NNTP newsgroup(s).