linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dimitri Fedrau <dima.fedrau@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Heiner Kallweit <hkallweit1@gmail.com>,
	Russell King <linux@armlinux.org.uk>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: phy: dp83822: Add support for PHY LEDs on DP83822
Date: Wed, 18 Dec 2024 09:54:00 +0100	[thread overview]
Message-ID: <20241218085400.GA779107@debian> (raw)
In-Reply-To: <1a7513fd-c78f-47de-94d7-757c83e9b94c@lunn.ch>

Am Tue, Dec 17, 2024 at 06:13:25PM +0100 schrieb Andrew Lunn:
> > +static int dp83822_led_hw_control_set(struct phy_device *phydev, u8 index,
> > +				      unsigned long rules)
> > +{
> > +	int mode;
> > +
> > +	mode = dp83822_led_mode(index, rules);
> > +	if (mode < 0)
> > +		return mode;
> > +
> > +	if (index == DP83822_LED_INDEX_LED_0 || index == DP83822_LED_INDEX_COL_GPIO2)
> > +		return phy_modify_mmd(phydev, MDIO_MMD_VEND2,
> > +				      MII_DP83822_MLEDCR, DP83822_MLEDCR_CFG,
> > +				      FIELD_PREP(DP83822_MLEDCR_CFG, mode));
> > +	else if (index == DP83822_LED_INDEX_LED_1_GPIO1)
> > +		return phy_modify_mmd(phydev, MDIO_MMD_VEND2,
> > +				      MII_DP83822_LEDCFG1,
> > +				      DP83822_LEDCFG1_LED1_CTRL,
> > +				      FIELD_PREP(DP83822_LEDCFG1_LED1_CTRL,
> > +						 mode));
> > +	else
> > +		return phy_modify_mmd(phydev, MDIO_MMD_VEND2,
> > +				      MII_DP83822_LEDCFG1,
> > +				      DP83822_LEDCFG1_LED3_CTRL,
> > +				      FIELD_PREP(DP83822_LEDCFG1_LED3_CTRL,
> > +						 mode));
> 
> index is taken direct from DT. Somebody might have:
> 
>            leds {
>                 #address-cells = <1>;
>                 #size-cells = <0>;
> 
>                 led@42 {
>                     reg = <42>;
>                     color = <LED_COLOR_ID_WHITE>;
>                     function = LED_FUNCTION_LAN;
>                     default-state = "keep";
>                 };
>             };
> 
> so you should not assume if it is not 0, 1 or 2, then it must be
> 3. Please always validate index.
>

By the way. Wouldn't it be helpful adding a u32 max_leds to
struct phy_driver ? Every driver supporting PHY LEDs validates index at the
moment. With max_leds it should be easy to check it in of_phy_leds and
return with an error if index is not valid.

Best regards,
Dimitri

  parent reply	other threads:[~2024-12-18  8:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-17  9:16 [PATCH net-next] net: phy: dp83822: Add support for PHY LEDs on DP83822 Dimitri Fedrau
2024-12-17 16:32 ` Simon Horman
2024-12-17 17:54   ` Dimitri Fedrau
2024-12-17 17:13 ` Andrew Lunn
2024-12-17 17:59   ` Dimitri Fedrau
2024-12-18 17:13     ` Andrew Lunn
2024-12-18  8:54   ` Dimitri Fedrau [this message]
2024-12-18 17:16     ` Andrew Lunn
2024-12-18 18:17       ` Dimitri Fedrau
2024-12-18 20:19         ` Andrew Lunn
2024-12-18 20:44           ` Dimitri Fedrau
2024-12-18  8:32 ` 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=20241218085400.GA779107@debian \
    --to=dima.fedrau@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).