From: Andrew Lunn <andrew@lunn.ch>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Ioana Ciornei <ioana.ciornei@nxp.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Russell King <linux@armlinux.org.uk>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Sergei Shtylyov <sergei.shtylyov@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] [RFC] net: phy: Fix reboot crash if CONFIG_IP_PNP is not set
Date: Tue, 5 Jan 2021 15:10:13 +0100 [thread overview]
Message-ID: <X/RzRd0zXHzAqLDl@lunn.ch> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2101051038550.302140@ramsan.of.borg>
> I added a statically-linked ethtool binary to my initramfs, and can
> confirm that retrieving the PHY statistics does not access the PHY
> registers when the device is suspended:
>
> # ethtool --phy-statistics eth0
> no stats available
> # ifconfig eth0 up
> # ethtool --phy-statistics eth0
> PHY statistics:
> phy_receive_errors: 0
> phy_idle_errors: 0
> #
>
> In the past, we've gone to great lengths to avoid accessing the PHY
> registers when the device is suspended, usually in the statistics
> handling (see e.g. [1][2]).
I would argue that is the wrong approach. The PHY device is a
device. It has its own lifetime. You would not suspend a PCI bus
controller without first suspending all PCI devices on the bus etc.
> +static int sh_mdiobb_read(struct mii_bus *bus, int phy, int reg)
> +{
> + struct bb_info *bb = container_of(bus->priv, struct bb_info, ctrl);
mii_bus->parent should give you dev, so there is no need to add it to
bb_info.
> + /* Wrap accessors with Runtime PM-aware ops */
> + bitbang->read = mdp->mii_bus->read;
> + bitbang->write = mdp->mii_bus->write;
> + mdp->mii_bus->read = sh_mdiobb_read;
> + mdp->mii_bus->write = sh_mdiobb_write;
I did wonder about just exporting the two functions so you can
directly call them.
Otherwise, this looks good.
Andrew
next prev parent reply other threads:[~2021-01-05 14:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 12:24 [PATCH] [RFC] net: phy: Fix reboot crash if CONFIG_IP_PNP is not set Geert Uytterhoeven
2021-01-04 14:53 ` Ioana Ciornei
2021-01-04 15:11 ` Geert Uytterhoeven
2021-01-04 17:01 ` Ioana Ciornei
2021-01-04 17:15 ` Andrew Lunn
2021-01-04 17:31 ` Andrew Lunn
2021-01-04 18:43 ` Ioana Ciornei
2021-01-04 21:30 ` Florian Fainelli
2021-01-05 10:01 ` Geert Uytterhoeven
2021-01-05 14:10 ` Andrew Lunn [this message]
2021-01-13 9:02 ` Geert Uytterhoeven
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=X/RzRd0zXHzAqLDl@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=hkallweit1@gmail.com \
--cc=ioana.ciornei@nxp.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=sergei.shtylyov@gmail.com \
--cc=wsa+renesas@sang-engineering.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