From: Arnd Bergmann <arnd@kernel.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Chen-Yu Tsai <wens@csie.org>, Maxime Ripard <mripard@kernel.org>,
SoC Team <soc@kernel.org>, arm-soc <arm@kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL] Allwinner Fixes for 5.10
Date: Fri, 30 Oct 2020 10:06:31 +0100 [thread overview]
Message-ID: <CAK8P3a2FsRpueZd8rBpE9DyW7QPXPoKud4K748QdspO-7J2ReQ@mail.gmail.com> (raw)
In-Reply-To: <CAMj1kXHdEbE2Tm7nG_2cv61omgwfoMivErqejqOcoiWGiWE4Hw@mail.gmail.com>
On Thu, Oct 29, 2020 at 11:59 PM Ard Biesheuvel <ardb@kernel.org> wrote:
>
> This is what Ilias and I tried to argue [0] earlier today, but Andrew
> has a different view.
>
> [0] https://lore.kernel.org/netdev/CAMj1kXGQDeOGj+2+tMnPhjoPJRX+eTh8-94yaH_bGwDATL7pkg@mail.gmail.com/
Could we work around it in by updating the DT contents at boot time before it
gets to the driver? We've done that in the past on specific machines to avoid
breaking DT compatibility, though I don't like the idea of doing it
for everyone.
Is there a safe fallback? I.e. would it break other platforms if we were to
always replace phy-mode="rgmii" with phy-mode="rgmii-id"? I suppose we
have no way of detecting the actual phy from early DT code in order to
figure out if the device behind the mdio bus is affected. The best we could
do might be either a list of affected boards or a list of affected ethernet
controllers for which this gets updated.
Arnd
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-10-30 9:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 19:06 [GIT PULL] Allwinner Fixes for 5.10 Maxime Ripard
2020-10-29 21:23 ` Arnd Bergmann
2020-10-29 21:40 ` Arnd Bergmann
2020-10-29 22:03 ` Ard Biesheuvel
2020-10-29 22:55 ` Arnd Bergmann
2020-10-29 22:59 ` Ard Biesheuvel
2020-10-30 9:06 ` Arnd Bergmann [this message]
2020-10-30 9:14 ` Ard Biesheuvel
2020-10-30 9:45 ` Arnd Bergmann
2020-10-30 10:03 ` Ard Biesheuvel
2020-10-30 10:15 ` Arnd Bergmann
2020-10-30 10:29 ` Ard Biesheuvel
2020-11-13 13:44 ` Arnd Bergmann
2020-11-13 13:29 ` Arnd Bergmann
2020-11-28 10:57 Maxime Ripard
2020-11-28 10:57 ` Maxime Ripard
2020-12-08 16:11 ` Arnd Bergmann
2020-12-08 16:11 ` Arnd Bergmann
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=CAK8P3a2FsRpueZd8rBpE9DyW7QPXPoKud4K748QdspO-7J2ReQ@mail.gmail.com \
--to=arnd@kernel.org \
--cc=ard.biesheuvel@linaro.org \
--cc=ardb@kernel.org \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mripard@kernel.org \
--cc=soc@kernel.org \
--cc=wens@csie.org \
/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.