[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <173444106208.1701236.11464150864495831064.b4-ty@kernel.org>
Date: Tue, 17 Dec 2024 13:11:02 +0000
From: Lee Jones <lee@...nel.org>
To: linux-leds@...r.kernel.org, Marek Vasut <marex@...x.de>
Cc: Andrew Lunn <andrew@...n.ch>,
Alexandre Torgue <alexandre.torgue@...s.st.com>,
Christian Marangi <ansuelsmth@...il.com>,
Christophe Roullier <christophe.roullier@...s.st.com>,
Daniel Golle <daniel@...rotopia.org>,
Heiner Kallweit <hkallweit1@...il.com>, Lee Jones <lee@...nel.org>,
Lukasz Majewski <lukma@...x.de>, Pavel Machek <pavel@....cz>,
kernel@...electronics.com, linux-stm32@...md-mailman.stormreply.com,
netdev@...r.kernel.org
Subject: Re: (subset) [PATCH v2] leds: trigger: netdev: Check offload
ability on interface up
On Mon, 16 Dec 2024 11:48:22 +0100, Marek Vasut wrote:
> The trigger_data->hw_control indicates whether the LED is controlled by HW
> offload, i.e. the PHY. The trigger_data->hw_control = can_hw_control() is
> currently called only from netdev_led_attr_store(), i.e. when writing any
> sysfs attribute of the netdev trigger instance associated with a PHY LED.
>
> The can_hw_control() calls validate_net_dev() which internally calls
> led_cdev->hw_control_get_device(), which is phy_led_hw_control_get_device()
> for PHY LEDs. The phy_led_hw_control_get_device() returns NULL if the PHY
> is not attached.
>
> [...]
Applied, thanks!
[1/1] leds: trigger: netdev: Check offload ability on interface up
commit: 0dfda50988c6805e8ab432e99866a021ea6ec46d
--
Lee Jones [李琼斯]
Powered by blists - more mailing lists