From: Detlev Casanova <detlev.casanova@collabora.com>
To: Peter Robinson <pbrobinson@gmail.com>
Cc: u-boot@lists.denx.de, Stefano Babic <sbabic@denx.de>,
Fabio Estevam <festevam@gmail.com>,
"NXP i . MX U-Boot Team" <uboot-imx@nxp.com>,
Troy Kisky <troy.kisky@boundarydevices.com>
Subject: Re: [PATCH v2] imx6: Re-add mmc aliases
Date: Fri, 09 Dec 2022 08:46:42 -0500 [thread overview]
Message-ID: <5885954.lOV4Wx5bFT@falcon9> (raw)
In-Reply-To: <CALeDE9M=xK2ptT0tnVJ=OZV9vgvqdXnK1UZSB_xKaWGNL60sng@mail.gmail.com>
On Friday, December 9, 2022 6:01:13 A.M. EST Peter Robinson wrote:
> On Thu, Dec 8, 2022 at 3:23 PM Detlev Casanova
>
> <detlev.casanova@collabora.com> wrote:
> > In commit d0399a46e7cda63c07e3eb8558bef84cfb068028, the device tree was
> > synchronized from linux and the aliases were dropped.
>
> Is there a reason not to get this change upstreamed in to Linux and
> then this wouldn't be a problem moving forward?
Yes, please check this conversation: http://patchwork.ozlabs.org/comment/3016037/[1]
> > They need to be kept so that the mmc cards are in the right order.
> > Without the aliases, u-boot reports:
> > MMC: FSL_SDHC: 2, FSL_SDHC: 3
> >
> > With the aliases, u-boot reports:
> > MMC: FSL_SDHC: 0, FSL_SDHC: 1
> >
> > The upstream linux device tree does not contain the same aliases than
> > u-boot (It keeps the devices order with /dev/mmcblk2 and /dev/mmcblk3).
> > Because this board has been using different aliases in u-boot
> > and linux, a imx6q-sabrelite-u-boot.dtsi file is added to be
> > automatically included in imx6q-sabrelite.dts.
> >
> > This way, linux and u-boot each keep their own aliases and there
> > is no breakage on current installations.
> >
> > This should never be done for new boards as we want to keep linux and
> > u-boot with the same aliases as much as possible.
> > This patch is only necessary to avoid breaking existing setups.
> >
> > Signed-off-by: Detlev Casanova <detlev.casanova@collabora.com>
> >
> > Gbp-Pq: Topic apertis/imx6
> > Gbp-Pq: Name 0010-imx6-Re-add-mmc-aliases.patch
> > ---
> >
> > arch/arm/dts/imx6q-sabrelite-u-boot.dtsi | 15 +++++++++++++++
> > 1 file changed, 15 insertions(+)
> > create mode 100644 arch/arm/dts/imx6q-sabrelite-u-boot.dtsi
> >
> > diff --git a/arch/arm/dts/imx6q-sabrelite-u-boot.dtsi
> > b/arch/arm/dts/imx6q-sabrelite-u-boot.dtsi new file mode 100644
> > index 0000000000..706ec9ba25
> > --- /dev/null
> > +++ b/arch/arm/dts/imx6q-sabrelite-u-boot.dtsi
> > @@ -0,0 +1,15 @@
> > +// SPDX-License-Identifier: GPL-2.0+
> > +/*
> > + * Copyright (C) 2022 Collabora
> > + */
> > +
> > +#include "imx6qdl-u-boot.dtsi"
> > +
> > +/ {
> > + aliases {
> > + mmc0 = &usdhc3;
> > + mmc1 = &usdhc4;
> > + pwm_lcd = &pwm1;
> > + pwm_lvds = &pwm4;
> > + };
> > +};
> > --
> > 2.38.1
--------
[1] http://patchwork.ozlabs.org/comment/3016037/
prev parent reply other threads:[~2022-12-09 13:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 15:23 [PATCH v2] imx6: Re-add mmc aliases Detlev Casanova
2022-12-08 16:55 ` Fabio Estevam
2022-12-08 18:15 ` [PATCH v3] imx6q-sabrelite: " Detlev Casanova
2022-12-08 18:37 ` Fabio Estevam
2023-01-31 16:52 ` sbabic
2022-12-09 11:01 ` [PATCH v2] imx6: " Peter Robinson
2022-12-09 13:46 ` Detlev Casanova [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=5885954.lOV4Wx5bFT@falcon9 \
--to=detlev.casanova@collabora.com \
--cc=festevam@gmail.com \
--cc=pbrobinson@gmail.com \
--cc=sbabic@denx.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox