From: Andrew Lunn <andrew@lunn.ch>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: netdev@vger.kernel.org, Jassi Brar <jaswinder.singh@linaro.org>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Willy Liu <willy.liu@realtek.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Masahisa Kojima <masahisa.kojima@linaro.org>,
Serge Semin <fancer.lancer@gmail.com>
Subject: Re: [PATCH net] netsec: ignore 'phy-mode' device property on ACPI systems
Date: Tue, 20 Oct 2020 14:50:01 +0200 [thread overview]
Message-ID: <20201020125001.GX456889@lunn.ch> (raw)
In-Reply-To: <20201018163625.2392-1-ardb@kernel.org>
On Sun, Oct 18, 2020 at 06:36:25PM +0200, Ard Biesheuvel wrote:
> Since commit bbc4d71d63549bc ("net: phy: realtek: fix rtl8211e rx/tx
> delay config"), the Realtek PHY driver will override any TX/RX delay
> set by hardware straps if the phy-mode device property does not match.
>
> This is causing problems on SynQuacer based platforms (the only SoC
> that incorporates the netsec hardware), since many were built with
> this Realtek PHY, and shipped with firmware that defines the phy-mode
> as 'rgmii', even though the PHY is configured for TX and RX delay using
> pull-ups.
>
> >From the driver's perspective, we should not make any assumptions in
> the general case that the PHY hardware does not require any initial
> configuration. However, the situation is slightly different for ACPI
> boot, since it implies rich firmware with AML abstractions to handle
> hardware details that are not exposed to the OS. So in the ACPI case,
> it is reasonable to assume that the PHY comes up in the right mode,
> regardless of whether the mode is set by straps, by boot time firmware
> or by AML executed by the ACPI interpreter.
>
> So let's ignore the 'phy-mode' device property when probing the netsec
> driver in ACPI mode, and hardcode the mode to PHY_INTERFACE_MODE_NA,
> which should work with any PHY provided that it is configured by the
> time the driver attaches to it. While at it, document that omitting
> the mode is permitted for DT probing as well, by setting the phy-mode
> DT property to the empty string.
>
> Cc: Jassi Brar <jaswinder.singh@linaro.org>
> Cc: Ilias Apalodimas <ilias.apalodimas@linaro.org>
> Cc: Masami Hiramatsu <mhiramat@kernel.org>
> Cc: Andrew Lunn <andrew@lunn.ch>
> Cc: Willy Liu <willy.liu@realtek.com>
> Cc: "David S. Miller" <davem@davemloft.net>
> Cc: Jakub Kicinski <kuba@kernel.org>
> Cc: Masahisa Kojima <masahisa.kojima@linaro.org>
> Cc: Serge Semin <fancer.lancer@gmail.com>
> Fixes: 533dd11a12f6 ("net: socionext: Add Synquacer NetSec driver")
> Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2020-10-20 12:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-18 16:36 [PATCH net] netsec: ignore 'phy-mode' device property on ACPI systems Ard Biesheuvel
2020-10-18 17:52 ` Andrew Lunn
2020-10-18 20:32 ` Ilias Apalodimas
2020-10-19 6:30 ` Ard Biesheuvel
2020-10-20 8:47 ` Ilias Apalodimas
2020-10-20 12:49 ` Andrew Lunn
2020-10-20 13:23 ` Ard Biesheuvel
2020-10-20 12:50 ` Andrew Lunn [this message]
2020-10-20 23:12 ` Jakub Kicinski
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=20201020125001.GX456889@lunn.ch \
--to=andrew@lunn.ch \
--cc=ardb@kernel.org \
--cc=davem@davemloft.net \
--cc=fancer.lancer@gmail.com \
--cc=ilias.apalodimas@linaro.org \
--cc=jaswinder.singh@linaro.org \
--cc=kuba@kernel.org \
--cc=masahisa.kojima@linaro.org \
--cc=mhiramat@kernel.org \
--cc=netdev@vger.kernel.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 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).