From: Masami Hiramatsu <mhiramat@kernel.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: "Andrew Lunn" <andrew@lunn.ch>,
"Daniel Thompson" <daniel.thompson@linaro.org>,
"Sumit Garg" <sumit.garg@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
steve@einval.com,
"Ilias Apalodimas" <ilias.apalodimas@linaro.org>,
"open list:BPF JIT for MIPS (32-BIT AND 64-BIT)"
<netdev@vger.kernel.org>, "Willy Liu" <willy.liu@realtek.com>,
"David S. Miller" <davem@davemloft.net>,
"Jakub Kicinski" <kuba@kernel.org>,
"Sasha Levin" <sashal@kernel.org>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Heiner Kallweit" <hkallweit1@gmail.com>,
"Masahisa Kojima" <masahisa.kojima@linaro.org>
Subject: Re: realtek PHY commit bbc4d71d63549 causes regression
Date: Sun, 18 Oct 2020 23:20:58 +0900 [thread overview]
Message-ID: <20201018232058.53a22758eba397695adc0352@kernel.org> (raw)
In-Reply-To: <CAMj1kXEY5jK7z+_ezDX733zbtHnaGUNCkJ_gHcPqAavOQPOzBQ@mail.gmail.com>
On Sun, 18 Oct 2020 00:19:25 +0200
Ard Biesheuvel <ardb@kernel.org> wrote:
> (cc'ing some folks who may care about functional networking on SynQuacer)
>
> On Sat, 17 Oct 2020 at 21:49, Andrew Lunn <andrew@lunn.ch> wrote:
> >
> > > So we can fix this firmware by just setting phy-mode to the empty
> > > string, right?
> >
> > I've never actually tried it, but i think so. There are no DT files
> > actually doing that, so you really do need to test it and see. And
> > there might be some differences between device_get_phy_mode() and
> > of_get_phy_mode().
> >
>
> Yes, that works fine. Fixed now in the latest firmware build [0]
Great! I've just started chasing that bug this Friday.
Thanks!
> But that still leaves the question whether and how to work around this
> for units in the field. Ignoring the PHY mode in the driver would
> help, as all known hardware ships with firmware that configures the
> PHY with the correct settings, but we will lose the ability to use
> other PHY modes in the future, in case the SoC is ever used with DT
> based minimal firmware that does not configure networking.
>
> Since ACPI implies rich firmware, we could make ACPI probing of the
> driver ignore the phy-mode setting in the DSDT. But if we don't do the
> same for DT, it would mean DT users are forced to upgrade their
> firmware, and hopefully do so before upgrading to a kernel that breaks
> networking. (These boxes are often used headless, so this can be
> annoying)
>
>
> [0] http://snapshots.linaro.org/components/kernel/leg-96boards-developerbox-edk2/83/
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2020-10-18 14:21 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-17 14:20 realtek PHY commit bbc4d71d63549 causes regression Ard Biesheuvel
2020-10-17 14:44 ` Andrew Lunn
2020-10-17 14:46 ` Ard Biesheuvel
2020-10-17 15:11 ` Andrew Lunn
2020-10-17 15:18 ` Ard Biesheuvel
2020-10-17 16:14 ` Ilias Apalodimas
2020-10-17 16:17 ` Ard Biesheuvel
2020-10-17 16:21 ` Ilias Apalodimas
2020-10-17 18:04 ` Andrew Lunn
2020-10-17 18:11 ` Ard Biesheuvel
2020-10-17 18:17 ` Ard Biesheuvel
2020-10-17 18:27 ` Andrew Lunn
2020-10-17 18:55 ` Ard Biesheuvel
2020-10-17 19:49 ` Andrew Lunn
2020-10-17 22:19 ` Ard Biesheuvel
2020-10-17 23:02 ` Andrew Lunn
2020-10-18 10:35 ` Ard Biesheuvel
2020-10-18 10:56 ` Ard Biesheuvel
2020-10-18 15:45 ` Andrew Lunn
2020-10-25 14:16 ` Ard Biesheuvel
2020-10-25 14:28 ` Andrew Lunn
2020-10-25 14:34 ` Ard Biesheuvel
2020-10-25 14:42 ` Andrew Lunn
2020-10-29 14:21 ` Ilias Apalodimas
2020-10-29 14:39 ` Andrew Lunn
2020-10-29 14:42 ` Ard Biesheuvel
2020-10-29 14:50 ` Andrew Lunn
2020-10-29 14:46 ` Ilias Apalodimas
2020-11-05 17:31 ` Jernej Škrabec
2020-11-13 13:50 ` Arnd Bergmann
2020-11-13 14:44 ` Andrew Lunn
2020-11-13 15:33 ` Arnd Bergmann
2020-11-13 16:56 ` Andrew Lunn
2020-11-13 21:26 ` Arnd Bergmann
2020-11-13 22:43 ` Andrew Lunn
2020-11-13 22:49 ` Ard Biesheuvel
2020-11-14 0:40 ` Andrew Lunn
2020-11-14 10:09 ` Ard Biesheuvel
2020-10-18 15:38 ` Andrew Lunn
2020-10-18 14:20 ` Masami Hiramatsu [this message]
2020-10-17 18:01 ` Andrew Lunn
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=20201018232058.53a22758eba397695adc0352@kernel.org \
--to=mhiramat@kernel.org \
--cc=alex.bennee@linaro.org \
--cc=andrew@lunn.ch \
--cc=ardb@kernel.org \
--cc=daniel.thompson@linaro.org \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=ilias.apalodimas@linaro.org \
--cc=kuba@kernel.org \
--cc=masahisa.kojima@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=steve@einval.com \
--cc=sumit.garg@linaro.org \
--cc=willy.liu@realtek.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.