[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <07b158b8-b745-4886-aa48-3b5be90fd2d9@lunn.ch>
Date: Fri, 10 Jan 2025 18:52:15 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Stefan Eichenberger <eichest@...il.com>
Cc: Dimitri Fedrau <dima.fedrau@...il.com>,
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>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] net: phy: marvell-88q2xxx: Add support for PHY LEDs on
88q2xxx
> > + if (index == MV88Q2XXX_LED_INDEX_TX_ENABLE)
> > + ret = phy_clear_bits_mmd(phydev, MDIO_MMD_PCS,
> > + MDIO_MMD_PCS_MV_RESET_CTRL,
> > + MDIO_MMD_PCS_MV_RESET_CTRL_TX_DISABLE);
>
> If I understand it correctly, this switches the function of the pin from
> TX_DISABLE to GPIO? Can you maybe add a comment here?
What is TX_DISABLE used for? I know it from SFPs, where it will
disable the laser. But here we are talking about a T1 PHY.
Do we have to be careful of use cases where the TX_DISABLE pin is
being used for TX_DISABLE?
Andrew
Powered by blists - more mailing lists