linux-kernel - Re: [PATCH net-next] net: phy: intel-xway: add support for PHY LEDs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <6f2cf2f0-08db-4b83-bfc9-0efab8324ac9@lunn.ch>
Date: Wed, 9 Oct 2024 14:38:16 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Daniel Golle <daniel@...rotopia.org>
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>,
	netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next] net: phy: intel-xway: add support for PHY LEDs

On Wed, Oct 09, 2024 at 01:32:20PM +0100, Daniel Golle wrote:
> On Wed, Oct 09, 2024 at 02:16:29PM +0200, Andrew Lunn wrote:
> > > +static int xway_gphy_led_polarity_set(struct phy_device *phydev, int index,
> > > +				      unsigned long modes)
> > > +{
> > > +	bool active_low = false;
> > > +	u32 mode;
> > > +
> > > +	if (index >= XWAY_GPHY_MAX_LEDS)
> > > +		return -EINVAL;
> > > +
> > > +	for_each_set_bit(mode, &modes, __PHY_LED_MODES_NUM) {
> > > +		switch (mode) {
> > > +		case PHY_LED_ACTIVE_LOW:
> > > +			active_low = true;
> > > +			break;
> > > +		case PHY_LED_ACTIVE_HIGH:
> > > +			break;
> > > +		default:
> > > +			return -EINVAL;
> > > +		}
> > > +	}
> > > +
> > > +	return phy_modify(phydev, XWAY_MDIO_LED, XWAY_GPHY_LED_INV(index),
> > > +			  active_low ? XWAY_GPHY_LED_INV(index) : 0);
> > 
> > This does not appear to implement the 'leave it alone' option.
> 
> The framework already implements that. The function is never called with
> modes == 0.

I was wondering about that.

But if this ever gets extended to support other properties, like HI-Z,
it is a bit of a trap waiting for somebody to fall into.

It is correct, so: Reviewed-by: Andrew Lunn <andrew@...n.ch> but it
would be nice if it was a bit more robust.

    Andrew