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: Mon, 05 Dec 2022 09:24:19 -0500 [thread overview]
Message-ID: <2697908.mvXUDI8C0e@falcon9> (raw)
In-Reply-To: <CAOMZO5DH1L_xbEwCGfy+qa92byC8HAd2u2+JnrFa=e9eEsUGhw@mail.gmail.com>
On Saturday, December 3, 2022 7:23:10 A.M. EST Fabio Estevam wrote:
> On Fri, Dec 2, 2022 at 8:36 PM Tom Rini <trini@konsulko.com> wrote:
> > No, upstream has different aliases and doesn't want these. That's the
> > point of the above thread, right?
>
> Upstream is correct in not accepting new alias for this board, as this
> could break
> existing setups.
>
> In U-Boot, we had alias for this board originally. After the sync with
> Linux they are gone.
>
> To fix U-Boot, the less invasive change is to add the alias into
> arch/arm/dts/imx6qdl-sabrelite-u-boot.dtsi.
>
> This way we can:
>
> 1. Keep the dtsi in sync with Linux
>
> 2. Do not break users in U-Boot
>
> This is the same approach I did for wandboard in the following commit:
>
> commit f827f84d3f5607d0b33e927f6127a888e7bd664f
> Author: Fabio Estevam <festevam@denx.de>
> Date: Fri Nov 4 08:12:54 2022 -0300
>
> wandboard: Pass mmc aliases
>
> Originally, the mmc aliases node was present in imx6qdl-wandboard.dtsi.
>
> After the sync with Linux in commit d0399a46e7cd ("imx6dl/imx6qdl:
> synchronise device trees with linux"), the aliases node is gone as
> the upstream version does not have it.
>
> This causes a regression in which the SD card cannot be found anymore:
>
> Since commit the aliases node has been removed
> U-Boot 2022.10-00999-gcca41ed3d63f-dirty (Nov 03 2022 - 22:07:38 -0300)
>
> CPU: Freescale i.MX6QP rev1.0 at 792 MHz
> Reset cause: POR
> DRAM: 2 GiB
> Core: 62 devices, 17 uclasses, devicetree: separate
> PMIC: PFUZE100 ID=0x10
> MMC: FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2
> Loading Environment from MMC... MMC: no card present
> *** Warning - No block device, using default environment
>
> Fix it by passing the alias node in the u-boot.dtsi file to
> restore the original behaviour where the SD card (esdhc3) was
> mapped to mmc0.
>
> Fixes: d0399a46e7cd ("imx6dl/imx6qdl: synchronise device trees with
> linux") Signed-off-by: Fabio Estevam <festevam@denx.de>
Ha good idea to use a u-boot specific dtsi. I'll send a new patch with that
then.
Thanks !
Detlev.
next prev parent reply other threads:[~2022-12-05 14:24 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 [this message]
2022-12-05 15:37 ` Tom Rini
2022-12-05 17:33 ` Fabio Estevam
2022-12-07 19:53 ` Detlev Casanova
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=2697908.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox