From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: Raju Rangoju <Raju.Rangoju@amd.com>, netdev@vger.kernel.org
Cc: pabeni@redhat.com, kuba@kernel.org, edumazet@google.com,
davem@davemloft.net, andrew+netdev@lunn.ch,
Shyam-sundar.S-k@amd.com
Subject: Re: [PATCH net-next] amd-xgbe: let the MAC manage PHY PM
Date: Wed, 19 Nov 2025 16:57:47 +0100 [thread overview]
Message-ID: <0ca796b8-2add-4101-a3d5-cd7135662938@bootlin.com> (raw)
In-Reply-To: <20251119093124.548566-1-Raju.Rangoju@amd.com>
Hi Raju,
On 19/11/2025 10:31, Raju Rangoju wrote:
> Use the MAC managed PM flag to indicate that MAC driver takes care of
> suspending/resuming the PHY, and reset it when the device is brought up.
>
> Signed-off-by: Raju Rangoju <Raju.Rangoju@amd.com>
> ---
> drivers/net/ethernet/amd/xgbe/xgbe-drv.c | 3 +++
> drivers/net/ethernet/amd/xgbe/xgbe-phy-v2.c | 1 +
> 2 files changed, 4 insertions(+)
>
> diff --git a/drivers/net/ethernet/amd/xgbe/xgbe-drv.c b/drivers/net/ethernet/amd/xgbe/xgbe-drv.c
> index f3adf29b222b..1c03fb138ce6 100644
> --- a/drivers/net/ethernet/amd/xgbe/xgbe-drv.c
> +++ b/drivers/net/ethernet/amd/xgbe/xgbe-drv.c
> @@ -1266,6 +1266,9 @@ static int xgbe_start(struct xgbe_prv_data *pdata)
>
> clear_bit(XGBE_STOPPED, &pdata->dev_state);
>
> + /* Reset the phy settings */
> + xgbe_phy_reset(pdata);
> +
At a first glance, this looks like 2 different things, so maybe 2
different patches ?
That said, with this change does it still make sense to call
xgbe_phy_reset() in xgbe_open() ?
With this patch we have :
xgpe_open() {
xgbe_phy_reset();
xgbe_start() {
xgbe_phy_reset(); /* again */
}
}
Can you remove the first call in .ndo_open ?
Maxime
next prev parent reply other threads:[~2025-11-19 15:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 9:31 [PATCH net-next] amd-xgbe: let the MAC manage PHY PM Raju Rangoju
2025-11-19 15:57 ` Maxime Chevallier [this message]
2025-11-21 10:22 ` Rangoju, Raju
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=0ca796b8-2add-4101-a3d5-cd7135662938@bootlin.com \
--to=maxime.chevallier@bootlin.com \
--cc=Raju.Rangoju@amd.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--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 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.