From: Lukas Wunner <lukas@wunner.de>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
kernel@pengutronix.de, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next v1 1/1] net: phy: ax88772a: fix lost pause advertisement configuration
Date: Sat, 25 Jun 2022 09:17:31 +0200 [thread overview]
Message-ID: <20220625071731.GA3462@wunner.de> (raw)
In-Reply-To: <20220624075558.3141464-1-o.rempel@pengutronix.de>
On Fri, Jun 24, 2022 at 09:55:58AM +0200, Oleksij Rempel wrote:
> In case of asix_ax88772a_link_change_notify() workaround, we run soft
> reset which will automatically clear MII_ADVERTISE configuration. The
> PHYlib framework do not know about changed configuration state of the
> PHY, so we need to save and restore all needed configuration registers.
[...]
> static void asix_ax88772a_link_change_notify(struct phy_device *phydev)
> {
> /* Reset PHY, otherwise MII_LPA will provide outdated information.
> * This issue is reproducible only with some link partner PHYs
> */
> - if (phydev->state == PHY_NOLINK && phydev->drv->soft_reset)
> + if (phydev->state == PHY_NOLINK && phydev->drv->soft_reset) {
> + struct asix_context context;
> +
> + asix_context_save(phydev, &context);
> +
> phydev->drv->soft_reset(phydev);
> +
> + asix_context_restore(phydev, &context);
> + }
> }
Hm, how about just calling phy_init_hw()? That will perform a
->soft_reset() and also restore the configuration, including
interrupts (which the above does not, but I guess that's
irrelevant as long as the driver uses polling).
Does phy_init_hw() do too much or too little compared to the above
and is hence not a viable solution?
Thanks,
Lukas
next prev parent reply other threads:[~2022-06-25 7:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 7:55 [PATCH net-next v1 1/1] net: phy: ax88772a: fix lost pause advertisement configuration Oleksij Rempel
2022-06-24 9:11 ` Oleksij Rempel
2022-06-25 7:17 ` Lukas Wunner [this message]
2022-06-26 8:58 ` Andrew Lunn
2022-06-26 12:15 ` Oleksij Rempel
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=20220625071731.GA3462@wunner.de \
--to=lukas@wunner.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--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).