From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Lizhe <sensor1010@163.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, mcoquelin.stm32@gmail.com,
alexandre.torgue@foss.st.com, vladimir.oltean@nxp.com,
maxime.chevallier@bootlin.com, netdev@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: stmmac: Support gpio high-level reset for devices requiring it
Date: Tue, 8 Jul 2025 18:40:06 +0100 [thread overview]
Message-ID: <aG1X9pPYDGO8kfM9@shell.armlinux.org.uk> (raw)
In-Reply-To: <20250708165044.3923-1-sensor1010@163.com>
On Tue, Jul 08, 2025 at 09:50:44AM -0700, Lizhe wrote:
> some devices only reset when the GPIO is at a high level, but the
> current function lacks support for such devices. add high-level
> reset functionality to the function to support devices that require
> high-level triggering for reset
>
> Signed-off-by: Lizhe <sensor1010@163.com>
> ---
> drivers/net/ethernet/stmicro/stmmac/stmmac_mdio.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/ethernet/stmicro/stmmac/stmmac_mdio.c b/drivers/net/ethernet/stmicro/stmmac/stmmac_mdio.c
> index 836f2848dfeb..cb989e6d7eac 100644
> --- a/drivers/net/ethernet/stmicro/stmmac/stmmac_mdio.c
> +++ b/drivers/net/ethernet/stmicro/stmmac/stmmac_mdio.c
> @@ -458,6 +458,7 @@ int stmmac_mdio_reset(struct mii_bus *bus)
>
> #ifdef CONFIG_OF
> if (priv->device->of_node) {
> + int active_low = 0;
> struct gpio_desc *reset_gpio;
> u32 delays[3] = { 0, 0, 0 };
>
> @@ -467,6 +468,9 @@ int stmmac_mdio_reset(struct mii_bus *bus)
> if (IS_ERR(reset_gpio))
> return PTR_ERR(reset_gpio);
>
> + if (reset_gpio)
> + active_low = gpiod_is_active_low(reset_gpio);
> +
> device_property_read_u32_array(priv->device,
> "snps,reset-delays-us",
> delays, ARRAY_SIZE(delays));
> @@ -474,11 +478,11 @@ int stmmac_mdio_reset(struct mii_bus *bus)
> if (delays[0])
> msleep(DIV_ROUND_UP(delays[0], 1000));
>
> - gpiod_set_value_cansleep(reset_gpio, 1);
> + gpiod_set_value_cansleep(reset_gpio, active_low ? 1 : 0);
> if (delays[1])
> msleep(DIV_ROUND_UP(delays[1], 1000));
>
> - gpiod_set_value_cansleep(reset_gpio, 0);
> + gpiod_set_value_cansleep(reset_gpio, active_low ? 0 : 1);
> if (delays[2])
> msleep(DIV_ROUND_UP(delays[2], 1000));
> }
NAK. Not required. The GPIO layer can cope with active-high and
active-low signals declared in firmware without needing driver
modification. Use the right data in the firmware and you don't
need to patch.
/* Bit 0 express polarity */
#define GPIO_ACTIVE_HIGH 0
#define GPIO_ACTIVE_LOW 1
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2025-07-08 19:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 16:50 [PATCH] net: stmmac: Support gpio high-level reset for devices requiring it Lizhe
2025-07-08 17:34 ` Andrew Lunn
[not found] ` <5c7adfef.1876.197ece74c25.Coremail.sensor1010@163.com>
2025-07-09 4:26 ` Russell King (Oracle)
[not found] ` <5bb49dc0.6933.197ee28444e.Coremail.sensor1010@163.com>
2025-07-09 11:11 ` Russell King (Oracle)
[not found] ` <4cfb4aab.9588.197eefef55f.Coremail.sensor1010@163.com>
2025-07-09 14:29 ` Russell King (Oracle)
[not found] ` <2352b745.a454.197efeef829.Coremail.sensor1010@163.com>
2025-07-09 17:01 ` Andrew Lunn
2025-07-09 17:41 ` Russell King (Oracle)
2025-07-09 12:54 ` Andrew Lunn
2025-07-08 17:40 ` Russell King (Oracle) [this message]
[not found] ` <2588871d.189d.197ece7c486.Coremail.sensor1010@163.com>
2025-07-09 4:25 ` Russell King (Oracle)
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=aG1X9pPYDGO8kfM9@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=maxime.chevallier@bootlin.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sensor1010@163.com \
--cc=vladimir.oltean@nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.