[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a3a5bd94-5bb7-4c65-85b6-d7876dca74b8@lunn.ch>
Date: Fri, 14 Feb 2025 19:06:22 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Dimitri Fedrau <dima.fedrau@...il.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>,
Niklas Söderlund <niklas.soderlund+renesas@...natech.se>,
Gregor Herburger <gregor.herburger@...tq-group.com>,
Stefan Eichenberger <eichest@...il.com>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next 3/3] net: phy: marvell-88q2xxx: enable
temperature sensor in mv88q2xxx_config_init
On Fri, Feb 14, 2025 at 05:32:05PM +0100, Dimitri Fedrau wrote:
> Temperature sensor gets enabled for 88Q222X devices in
> mv88q222x_config_init. Move enabling to mv88q2xxx_config_init because
> all 88Q2XXX devices support the temperature sensor.
>
> Signed-off-by: Dimitri Fedrau <dima.fedrau@...il.com>
The change itself looks fine:
Reviewed-by: Andrew Lunn <andrew@...n.ch>
but is the sensor actually usable if the PHY has not yet been
configured?
Architecturally, it seems odd to register the HWMON in probe, and then
enable it in config_init.
Andrew
Powered by blists - more mailing lists