[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <39d5d8af-0bac-4b91-85df-4e04a5835f53@lunn.ch>
Date: Fri, 23 May 2025 18:07:49 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Sky Huang <SkyLake.Huang@...iatek.com>
Cc: Heiner Kallweit <hkallweit1@...il.com>,
Russell King <linux@...linux.org.uk>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Daniel Golle <daniel@...rotopia.org>,
Qingfang Deng <dqfext@...il.com>,
Matthias Brugger <matthias.bgg@...il.com>,
AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org
Subject: Re: [PATCH net-next 2/2] net: phy: mtk-ge-soc: Fix LED behavior if
blinking is not set.
On Fri, May 23, 2025 at 07:36:01PM +0800, Sky Huang wrote:
> From: Sky Huang <skylake.huang@...iatek.com>
>
> If delay_on==0 and delay_off==0 are passed to
> mt798x_2p5ge_phy_led_blink_set() and mtk_phy_led_num_dly_cfg(),
> blinking is actually not set. So don't clean "LED on" status under
> this circumstance.
Actually, i think mtk_phy_led_num_dly_cfg() is wrong.
https://docs.kernel.org/leds/leds-class.html#hardware-accelerated-blink-of-leds
The blink_set() function should choose a user friendly blinking
value if it is called with *delay_on==0 && *delay_off==0
parameters. In this case the driver should give back the chosen
value through delay_on and delay_off parameters to the leds
subsystem.
That is not what mtk_phy_led_num_dly_cfg() does.
Andrew
---
pw-bot: cr
Powered by blists - more mailing lists