From: Detlev Casanova <detlev.casanova@collabora.com>
To: Tom Rini <trini@konsulko.com>, Fabio Estevam <festevam@gmail.com>
Cc: Troy Kisky <troy.kisky@boundarydevices.com>,
u-boot@lists.denx.de, Stefano Babic <sbabic@denx.de>,
"NXP i . MX U-Boot Team" <uboot-imx@nxp.com>
Subject: Re: [PATCH] dts: Re-add aliases for imx6qdl-sabrelite devices
Date: Wed, 07 Dec 2022 14:53:10 -0500 [thread overview]
Message-ID: <2745476.mvXUDI8C0e@falcon9> (raw)
In-Reply-To: <CAOMZO5BT7gV_jjjkMOsGqffa2iKys+_LQJFWwddJX7a+sqxzJQ@mail.gmail.com>
On Monday, December 5, 2022 12:33:48 P.M. EST Fabio Estevam wrote:
> On Mon, Dec 5, 2022 at 12:37 PM Tom Rini <trini@konsulko.com> wrote:
> > I'm not really happy with this approach. It's not that upstream doesn't
> > have aliases now, it's that it has different aliases, right? That's why
> > they won't accept these?
>
> imx6q.dtsi does have the default mmc aliases:
>
> mmc0 = &usdhc1;
> mmc1 = &usdhc2;
> mmc2 = &usdhc3;
> mmc3 = &usdhc4;
>
> Upstream does not want to change mmc alias because users may rely on
> this mmc aliases.
>
> Changing it now may cause the board not to boot anymore as the rootfs
> cannot be found.
>
> It is OK to change mmc alias for a newly introduced board, but please
> keep in mind that
> wandboard and sabrelite have been launched many many years ago.
>
> So for upstream Linux the message was clear: don't change the mmc
> alias for these boards.
>
> Now let's talk about U-Boot.
>
> Prior to d0399a46e7cd ("imx6dl/imx6qdl: synchronise device trees with
> linux") the mmc alias for sabrelite was present:
>
> mmc0 = &usdhc3;
> mmc1 = &usdhc4;
>
> After this commit, the mmc alias is gone and causes the boot
> regression as reported by Detlev.
>
> We don't want to cause regressions in U-Boot as well, so that's why I
> propose just adding the alias into u-boot.dtsi.
>
> There are many boards that does the same.
>
> > But this also highlights that we really need to get these kind of
> > aliases and similar (a) re-synced with upstream ASAP and (b) do that at
>
> imx6 dts files are already synced with Linux.
>
> > the start. I don't know which group of "users are broken by this change"
> > is bigger, the group that needs the aliases we have or the group that
> > needs the other aliases, but the group that gets changes upstream first
> > "wins" here is how the OSS world works.
>
> I prefer to not break things for anyone, hence my proposal.
>
> If you are still not happy with it, please feel free to submit a patch
> with your proposal.
There is no SPL enabled for the imx.6 Sabrelite, Isn't that needed to use the
*-u-boot.dtsi files ?
It is not clear to me how those are loaded.
Detlev.
next prev parent reply other threads:[~2022-12-07 19:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 15:22 [PATCH] dts: Re-add aliases for imx6qdl-sabrelite devices Detlev Casanova
2022-10-27 18:30 ` Tom Rini
2022-11-11 15:28 ` Detlev Casanova
2022-11-11 15:35 ` Tom Rini
2022-12-02 19:06 ` Detlev Casanova
2022-12-02 20:08 ` Tom Rini
2022-12-02 23:20 ` Fabio Estevam
2022-12-02 23:36 ` Tom Rini
2022-12-03 12:23 ` Fabio Estevam
2022-12-05 14:24 ` Detlev Casanova
2022-12-05 15:37 ` Tom Rini
2022-12-05 17:33 ` Fabio Estevam
2022-12-07 19:53 ` Detlev Casanova [this message]
2022-12-07 20:01 ` Tom Rini
2022-12-07 20:03 ` Tom Rini
2022-12-07 20:08 ` Detlev Casanova
2022-12-07 20:32 ` Tom Rini
2022-12-08 13:35 ` Michael Walle
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=2745476.mvXUDI8C0e@falcon9 \
--to=detlev.casanova@collabora.com \
--cc=festevam@gmail.com \
--cc=sbabic@denx.de \
--cc=trini@konsulko.com \
--cc=troy.kisky@boundarydevices.com \
--cc=u-boot@lists.denx.de \
--cc=uboot-imx@nxp.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.