From: Frank Li <Frank.li@nxp.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: imx@lists.linux.dev, Shawn Guo <shawnguo@kernel.org>,
soc@kernel.org, arm@kernel.org, kernel@pengutronix.de,
Fabio Estevam <festevam@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL 2/4] i.MX arm dts changes for v7.1
Date: Thu, 30 Apr 2026 14:47:43 -0400 [thread overview]
Message-ID: <afOjz03KQGa8sHRY@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <0c5a5204-331e-473b-9969-ff96bf711ce5@kernel.org>
On Wed, Apr 29, 2026 at 08:29:49PM +0200, Krzysztof Kozlowski wrote:
> On 28/04/2026 16:03, Sébastien Szymanski wrote:
> > Hello,
> >
> > On 3/30/26 4:14 PM, Frank Li wrote:
> >> ARM: dts: imx: remove redundant intermediate node in pinmux hierarchy
> >
> > This commit breaks Linux 7.1-rc1 boot on my APF27Dev board. I see the
> > following errors with earlyprintk enabled:
> >
> > [ 0.346162] imx27-pinctrl 10015000.pinmux: unable to find group for
> > node i2c1grp
> > [ 0.354438] imx27-pinctrl 10015000.pinmux: unable to find group for
> > node i2c2grp
> > ...
> > [ 0.636217] imx27-pinctrl 10015000.pinmux: unable to find group for
> > node pwmgrp
> > [ 0.644346] imx27-pinctrl 10015000.pinmux: unable to find group for
> > node gpioledsgrp
> > [ 0.657247] imx27-pinctrl 10015000.pinmux: unable to find group for
> > node uart1grp
> > ...
> > [ 0.868102] imx27-pinctrl 10015000.pinmux: unable to find group for
> > node cspi1grp
> > [ 0.876513] imx27-pinctrl 10015000.pinmux: unable to find group for
> > node cspi2grp
> > [ 0.888903] imx27-pinctrl 10015000.pinmux: unable to find group for
> > node fec1grp
> > ...
> > [ 2.413181] imx27-pinctrl 10015000.pinmux: unable to find group for
> > node gpiokeysgrp
> >
> > Reverting the commit makes the errors disappear and the board boot again.
> >
> > Should I send a patch reverting this commit ?
>
>
> If you know how to fix it, then better fixing it instead of reverting,
> but otherwise yes, revert is justified. Just give a few more days for
> Frank or community to reply, because maybe there is a fix known.
Thanks for your report this problem, let me check at next monday since I
am traving.
Frank
>
> Best regards,
> Krzysztof
next prev parent reply other threads:[~2026-04-30 18:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 14:14 [GIT PULL 3/4] i.MX dt binding changes for v7.1 Frank Li
2026-03-30 14:14 ` [GIT PULL 1/4] i.MX arm64 dts " Frank Li
2026-04-04 14:34 ` Krzysztof Kozlowski
2026-04-06 1:31 ` Frank Li
2026-03-30 14:14 ` [GIT PULL 2/4] i.MX arm " Frank Li
2026-04-04 14:47 ` Krzysztof Kozlowski
2026-04-28 14:03 ` Sébastien Szymanski
2026-04-29 18:29 ` Krzysztof Kozlowski
2026-04-30 18:47 ` Frank Li [this message]
2026-03-30 14:14 ` [GIT PULL 4/4] i.MX drivers/soc " Frank Li
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=afOjz03KQGa8sHRY@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=arm@kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=shawnguo@kernel.org \
--cc=soc@kernel.org \
/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