From: Corinna Vinschen <vinschen@redhat.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Heiner Kallweit <hkallweit1@gmail.com>,
Giuseppe Cavallaro <peppe.cavallaro@st.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Jose Abreu <joabreu@synopsys.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next] net: stmmac: allow ethtool action on PCI devices if device is down
Date: Wed, 26 Apr 2023 12:24:52 +0200 [thread overview]
Message-ID: <ZEj79PLEcn7Q78T5@calimero.vinschen.de> (raw)
In-Reply-To: <20230425065441.1bc15b29@kernel.org>
On Apr 25 06:54, Jakub Kicinski wrote:
> On Tue, 25 Apr 2023 10:14:01 +0200 Corinna Vinschen wrote:
> > is that patch still under review or is it refused, given the
> > current behaviour is not actually incorrect?
>
> That's not what Heiner said. Does the device not link the netdev
> correctly to the bus device?
No, that's not the problem.
> Core already does pm_get/pm_put
> around ethtool calls.
Yeah, right. I made a more thorough test now and it appears that
the calls don't even have any effect.
For testing I created a driver which simply skips the check for
netdev_running() and compared with the driver including my patch.
I tested almost all ethtool calls fetching and setting values and
there's no difference in behaviour.
Worse, while it's possible to change a lot of settings when skipping the
netdev_running() check, , some really basic stuff doesn't work as
desired. I. e., setting autoneg or a fixed speed while the interface is
down is taken without complaints, but it has no effect when the
interface goes up again.
So we can just scratch my patch. Sorry wasting your time.
Corinna
prev parent reply other threads:[~2023-04-26 10:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 9:23 [PATCH net-next] net: stmmac: allow ethtool action on PCI devices if device is down Corinna Vinschen
2023-03-31 10:48 ` Heiner Kallweit
2023-04-03 9:43 ` Corinna Vinschen
2023-04-03 13:13 ` Heiner Kallweit
2023-04-25 8:14 ` Corinna Vinschen
2023-04-25 13:54 ` Jakub Kicinski
2023-04-26 10:24 ` Corinna Vinschen [this message]
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=ZEj79PLEcn7Q78T5@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=alexandre.torgue@foss.st.com \
--cc=hkallweit1@gmail.com \
--cc=joabreu@synopsys.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.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).