From: Vladimir Oltean <olteanv@gmail.com>
To: Michael Walle <michael@walle.cc>
Cc: Tom Rini <trini@konsulko.com>, Rob Herring <robh@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
devicetree@vger.kernel.org, Priyanka Jain <priyanka.jain@nxp.com>,
u-boot@lists.denx.de, heiko.thiery@gmail.com
Subject: Re: incompatible device trees between u-boot and linux
Date: Mon, 30 Aug 2021 03:20:48 +0300 [thread overview]
Message-ID: <20210830002048.kbnsv47dnrkh4bvi@skbuf> (raw)
In-Reply-To: <0e2f6513b6fb7162faa7afd1f6f21348@walle.cc>
On Sun, Aug 29, 2021 at 01:12:30AM +0200, Michael Walle wrote:
> Am 2021-08-26 18:32, schrieb Vladimir Oltean:
> > On Thu, Aug 26, 2021 at 09:35:12AM +0200, Michael Walle wrote:
> > > Theres still one catch at the moment, AFAIK in linux you can put the
> > > PHYs either in the mdio controller node or in a "mdio" subnode within
> > > the ethernet controller node. I'm not sure wether the latter works in
> > > u-boot, but [1] looks promising. At least, linux dtbs are using the
> > > mdio subnodes and u-boot put the phys into the mdio controller node.
> >
> > Please change Linux for that, move the PHYs from the per-port MDIO node
> > to the PF 3 central MDIO controller node. Due to hardware reasons, the
> > per-port MDIO controller registers are in fact de-featured and should be
> > hidden from new LS1028A reference manuals.
>
> Care to share some more details? There should be some more information
> besides "for hardware reasons" which should go into the commit message.
> Is there an erratum?
>
> In fact, I guess in Rev0 of the RM it has already been removed, at least
> from the port memory map (in the RevB RM it was still present).
>
> -michael
It's a long and boring explanation, PM sent.
prev parent reply other threads:[~2021-08-30 0:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51c2a92f6bf771769f1e2da5157727e8@walle.cc>
[not found] ` <20210825140045.GR858@bill-the-cat>
[not found] ` <20210825141816.qfn25xlech55rwsg@skbuf>
[not found] ` <20210825142610.GU858@bill-the-cat>
[not found] ` <20210825151220.xkpxxucce2oicfvy@skbuf>
2021-08-25 15:24 ` incompatible device trees between u-boot and linux Tom Rini
2021-08-25 15:43 ` Vladimir Oltean
2021-08-25 20:09 ` Tom Rini
2021-08-25 23:03 ` Vladimir Oltean
2021-08-26 7:35 ` Michael Walle
2021-08-26 16:32 ` Vladimir Oltean
2021-08-28 23:12 ` Michael Walle
2021-08-30 0:20 ` Vladimir Oltean [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=20210830002048.kbnsv47dnrkh4bvi@skbuf \
--to=olteanv@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=heiko.thiery@gmail.com \
--cc=michael@walle.cc \
--cc=priyanka.jain@nxp.com \
--cc=robh@kernel.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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