From: Michael Walle <michael@walle.cc>
To: Vladimir Oltean <olteanv@gmail.com>
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: Thu, 26 Aug 2021 09:35:12 +0200 [thread overview]
Message-ID: <5798d183839b78ed5e6f2cd880934759@walle.cc> (raw)
In-Reply-To: <20210825230305.hbxhshhbdhe56iod@skbuf>
Am 2021-08-26 01:03, schrieb Vladimir Oltean:
> On Wed, Aug 25, 2021 at 04:09:50PM -0400, Tom Rini wrote:
> In any case, it doesn't sound absurd at all, with a bit of passion it
> could be done on all Layerscapes. I would be absolutely glad to help on
> the Ethernet / DSA side of things (which I believe is the reason why
> Michael summoned me into this thread),
;) and because I thought you might be interested in the answer to the
initial question. After all, you also worked on the device trees in
linux
and u-boot.
> but I don't believe that's where
> the problem is right now. When I added the DM_DSA uclass to U-Boot I
> did
> my best to pick a reasonable subset of Linux DSA, and with compatible
> device tree bindings. Also maintaining the Linux side of things, I did
> provide feedback to Tim Harvey for the Microchip KSZ switches as to
> what is the subset supported by U-Boot that would also be DT-compatible
> with Linux. If it turns out that I failed at that, I am willing to
> rework what we have.
I started to convert the u-boot device tree yesterday - and it doesn't
look too bad for now. I was already able to copy the kernel soc dtsi
and u-boot is still booting and working.
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.
Maybe sharing the device tree between linux and u-boot isn't that hard
for the ls1028a after all and its just that nobody did it for now.
Renaming the reference here and there and introducing the linux
compatible strings may do it. I'll come back to you if there are
problems with ethernet (or DSA).
-michael
> I have been known on a few occasions to say "U-Boot does not parse this
> part of the device tree, you can just strip it away", but I will keep
> my
> mouth shut from now on.
[1] https://lists.denx.de/pipermail/u-boot/2020-May/410169.html
next prev parent reply other threads:[~2021-08-26 7:35 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 [this message]
2021-08-26 16:32 ` Vladimir Oltean
2021-08-28 23:12 ` Michael Walle
2021-08-30 0:20 ` Vladimir Oltean
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=5798d183839b78ed5e6f2cd880934759@walle.cc \
--to=michael@walle.cc \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=heiko.thiery@gmail.com \
--cc=olteanv@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).