[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210301104404.GC31897@duo.ucw.cz>
Date: Mon, 1 Mar 2021 11:44:04 +0100
From: Pavel Machek <pavel@....cz>
To: Marek BehĂșn <kabel@...nel.org>
Cc: netdev@...r.kernel.org, linux-leds@...r.kernel.org,
Dan Murphy <dmurphy@...com>,
Russell King <linux@...linux.org.uk>,
Andrew Lunn <andrew@...n.ch>,
Matthias Schiffer <matthias.schiffer@...tq-group.com>,
"David S. Miller" <davem@...emloft.net>,
Jacek Anaszewski <jacek.anaszewski@...il.com>,
Ben Whitten <ben.whitten@...il.com>
Subject: Re: [PATCH RFC leds + net-next 4/7] leds: trigger: netdev: support
HW offloading
Hi!
> Add support for HW offloading of the netdev trigger.
>
> We need to change spinlock to mutex, because if spinlock is used, the
> trigger_offload() method cannot sleep, which can happen for ethernet
> PHYs.
Is that bugfix or just needed for offloading? Should be separate patch
in any case.
> Move struct led_trigger_data into global include directory, into file
> linux/ledtrig.h, so that drivers wanting to offload the trigger can
> access its settings.
Separate...
> @@ -327,12 +310,14 @@ static int netdev_trig_notify(struct notifier_block *nb,
> case NETDEV_CHANGE:
> if (netif_carrier_ok(dev))
> trigger_data->linkup = 1;
> + reset = !trigger_data->led_cdev->offloaded;
> break;
> }
>
> - set_baseline_state(trigger_data);
> + if (reset)
> + set_baseline_state(trigger_data);
>
> - spin_unlock_bh(&trigger_data->lock);
> + mutex_unlock(&trigger_data->lock);
>
> return NOTIFY_DONE;
> }
Is this the only thing it saves? Because.. that would not be worth
it.
Best regards,
Pavel
--
http://www.livejournal.com/~pavelmachek
Download attachment "signature.asc" of type "application/pgp-signature" (196 bytes)
Powered by blists - more mailing lists