From: Lukasz Majewski <lukma@denx.de>
To: Tom Rini <trini@konsulko.com>
Cc: Fabio Estevam <festevam@gmail.com>,
Stefano Babic <sbabic@nabladev.com>,
uboot-imx@nxp.com, albert.aribaud@3adev.fr, u-boot@lists.denx.de
Subject: Re: [PATCH 2/2] dts: Add u-boot specific 'fsl,mux_mask' property to iomuxc for vf610
Date: Wed, 25 Jun 2025 08:36:37 +0200 [thread overview]
Message-ID: <20250625083637.1d286cec@wsk> (raw)
In-Reply-To: <20250624210116.GL4003484@bill-the-cat>
[-- Attachment #1: Type: text/plain, Size: 1887 bytes --]
Hi Tom,
> On Tue, Jun 24, 2025 at 10:47:00PM +0200, Lukasz Majewski wrote:
>
> > The commit e8a9521e649f
> > ("vf500/vf610: synchronise device trees with linux")
> > has synchronized U-Boot's DTS with v5.19 Linux kernel.
> > It turned out that in Linux's upstream iomuxc node description the
> > fsl,mux_mask' was missing, so the U-Boot's pinctrl driver for NXP's
> > Vybrid SoC was not working properly.
> >
> > As by default the mux mask was set to 0, the vf610 based boards
> > (like BK4) were bricked, due to misconfiguration of gpio at early
> > boot stage.
> >
> > The fix for all vf610 based boards is to introduce
> > vfxxx-u-boot.dtsi file with 'fsl,mux_mask' property provided and
> > include it in boards' specific U-Boot adjustment files (like
> > vf610-bk4r1-u-boot.dtsi).
> >
> > Signed-off-by: Lukasz Majewski <lukma@denx.de>
> > ---
> > arch/arm/dts/vf610-bk4r1-u-boot.dtsi | 2 ++
> > arch/arm/dts/vfxxx-u-boot.dtsi | 9 +++++++++
> > 2 files changed, 11 insertions(+)
> > create mode 100644 arch/arm/dts/vfxxx-u-boot.dtsi
>
> It looks like this is still missing upstream, so what's the status on
> that?
It looks like in Linux the mux_mask is hardcoded (for Vybrid vf610):
https://elixir.bootlin.com/linux/v6.16-rc3/source/drivers/pinctrl/freescale/pinctrl-vf610.c#L321
In u-boot other SoCs use it as well, but with different values:
- arch/arm/dts/imxrt1050.dtsi -> 0x7
- arch/arm/dts/imx8ulp-evk-u-boot.dtsi -> 0xf00
In the imx8ulp case above - it is already set in *-u-boot.dtsi specific
file, so I've followed this approach.
> Thanks.
>
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-06-25 6:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 20:46 [PATCH 1/2] config: nxp: bk4: Increase size of CONFIG_SYS_MALLOC_F_LEN (to 0x1000) Lukasz Majewski
2025-06-24 20:47 ` [PATCH 2/2] dts: Add u-boot specific 'fsl, mux_mask' property to iomuxc for vf610 Lukasz Majewski
2025-06-24 21:01 ` [PATCH 2/2] dts: Add u-boot specific 'fsl,mux_mask' " Tom Rini
2025-06-25 6:36 ` Lukasz Majewski [this message]
2025-06-25 14:14 ` Tom Rini
2025-06-25 16:28 ` Conor Dooley
2025-06-25 16:37 ` Tom Rini
2025-06-25 20:32 ` Lukasz Majewski
2025-06-25 20:52 ` Tom Rini
2025-06-26 6:17 ` Lukasz Majewski
2025-06-25 14:25 ` Fabio Estevam
2025-06-25 1:09 ` [PATCH 1/2] config: nxp: bk4: Increase size of CONFIG_SYS_MALLOC_F_LEN (to 0x1000) Peng Fan
2025-06-25 2:18 ` Fabio Estevam
2025-06-25 6:52 ` Lukasz Majewski
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=20250625083637.1d286cec@wsk \
--to=lukma@denx.de \
--cc=albert.aribaud@3adev.fr \
--cc=festevam@gmail.com \
--cc=sbabic@nabladev.com \
--cc=trini@konsulko.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