From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: "Marek Behún" <kabel@kernel.org>, netdev@vger.kernel.org
Cc: linux-leds@vger.kernel.org, Pavel Machek <pavel@ucw.cz>,
Dan Murphy <dmurphy@ti.com>, Russell King <linux@armlinux.org.uk>,
Andrew Lunn <andrew@lunn.ch>,
Matthias Schiffer <matthias.schiffer@ew.tq-group.com>,
"David S. Miller" <davem@davemloft.net>,
Ben Whitten <ben.whitten@gmail.com>
Subject: Re: [PATCH RFC leds + net-next 2/7] leds: trigger: netdev: simplify the driver by using bit field members
Date: Fri, 30 Oct 2020 23:37:52 +0100 [thread overview]
Message-ID: <64419e33-ffcd-4082-01bd-3370dae86b4b@gmail.com> (raw)
In-Reply-To: <20201030114435.20169-3-kabel@kernel.org>
Hi Marek,
Bitops are guaranteed to be atomic and this was done for a reason.
On 10/30/20 12:44 PM, Marek Behún wrote:
> Use bit fields members in struct led_netdev_data instead of one mode
> member and set_bit/clear_bit/test_bit functions. These functions are
> suitable for longer or variable length bit arrays.
>
> Signed-off-by: Marek Behún <kabel@kernel.org>
> ---
> drivers/leds/trigger/ledtrig-netdev.c | 69 ++++++++++++---------------
> 1 file changed, 30 insertions(+), 39 deletions(-)
>
> diff --git a/drivers/leds/trigger/ledtrig-netdev.c b/drivers/leds/trigger/ledtrig-netdev.c
> index 4f6b73e3b491..8f013b6df4fa 100644
> --- a/drivers/leds/trigger/ledtrig-netdev.c
> +++ b/drivers/leds/trigger/ledtrig-netdev.c
> @@ -49,11 +49,11 @@ struct led_netdev_data {
> atomic_t interval;
> unsigned int last_activity;
>
> - unsigned long mode;
> -#define NETDEV_LED_LINK 0
> -#define NETDEV_LED_TX 1
> -#define NETDEV_LED_RX 2
> -#define NETDEV_LED_MODE_LINKUP 3
> + unsigned link:1;
> + unsigned tx:1;
> + unsigned rx:1;
> +
> + unsigned linkup:1;
> };
>
> enum netdev_led_attr {
> @@ -73,10 +73,10 @@ static void set_baseline_state(struct led_netdev_data *trigger_data)
> if (!led_cdev->blink_brightness)
> led_cdev->blink_brightness = led_cdev->max_brightness;
>
> - if (!test_bit(NETDEV_LED_MODE_LINKUP, &trigger_data->mode))
> + if (!trigger_data->linkup)
> led_set_brightness(led_cdev, LED_OFF);
[...]
--
Best regards,
Jacek Anaszewski
next prev parent reply other threads:[~2020-10-30 22:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 11:44 [PATCH RFC leds + net-next 0/7] netdev trigger offloading and LEDs on Marvell PHYs Marek Behún
2020-10-30 11:44 ` [PATCH RFC leds + net-next 1/7] leds: trigger: netdev: don't explicitly zero kzalloced data Marek Behún
2020-11-25 12:34 ` Pavel Machek
2020-10-30 11:44 ` [PATCH RFC leds + net-next 2/7] leds: trigger: netdev: simplify the driver by using bit field members Marek Behún
2020-10-30 22:37 ` Jacek Anaszewski [this message]
2020-10-30 23:45 ` Marek Behún
2020-11-01 16:40 ` Jacek Anaszewski
2021-03-01 10:30 ` Pavel Machek
2020-10-30 11:44 ` [PATCH RFC leds + net-next 3/7] leds: trigger: add API for HW offloading of triggers Marek Behún
2021-03-01 10:38 ` Pavel Machek
2020-10-30 11:44 ` [PATCH RFC leds + net-next 4/7] leds: trigger: netdev: support HW offloading Marek Behún
2020-11-05 14:44 ` Marek Behún
2021-03-01 10:44 ` Pavel Machek
2020-10-30 11:44 ` [PATCH RFC leds + net-next 5/7] net: phy: add simple incrementing phyindex member to phy_device struct Marek Behún
2021-03-01 10:46 ` Pavel Machek
2020-10-30 11:44 ` [PATCH RFC leds + net-next 6/7] net: phy: add support for LEDs connected to ethernet PHYs Marek Behún
2021-03-01 10:52 ` Pavel Machek
2020-10-30 11:44 ` [PATCH RFC leds + net-next 7/7] net: phy: marvell: support LEDs connected on Marvell PHYs Marek Behún
2020-10-30 15:04 ` kernel test robot
2020-10-30 16:04 ` kernel test robot
2020-11-25 12:38 ` Pavel Machek
2021-03-01 11:05 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2020-10-30 15:27 [PATCH RFC leds + net-next 2/7] leds: trigger: netdev: simplify the driver by using bit field members kernel test robot
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=64419e33-ffcd-4082-01bd-3370dae86b4b@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=andrew@lunn.ch \
--cc=ben.whitten@gmail.com \
--cc=davem@davemloft.net \
--cc=dmurphy@ti.com \
--cc=kabel@kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=matthias.schiffer@ew.tq-group.com \
--cc=netdev@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.