From: Krzysztof Kozlowski <krzk@kernel.org>
To: Frank Li <Frank.Li@nxp.com>
Cc: soc@kernel.org, arm@kernel.org, Shawn Guo <shawnguo@kernel.org>,
Fabio Estevam <festevam@gmail.com>,
kernel@pengutronix.de, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] i.MX fixes for 7.0 round 2
Date: Sat, 11 Apr 2026 10:14:08 +0200 [thread overview]
Message-ID: <20260411-ancient-okapi-of-excitement-e5e22f@quoll> (raw)
In-Reply-To: <20260404001857.3374669-1-Frank.Li@nxp.com>
On Fri, Apr 03, 2026 at 08:18:47PM -0400, Frank Li wrote:
> From: Frank.Li@nxp.com
>
> The following changes since commit 511f76bf1dce5acf8907b65a7d1bc8f7e7c0d637:
>
> arm64: dts: imx8mq-librem5: Bump BUCK1 suspend voltage up to 0.85V (2026-03-17 23:24:44 -0400)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/frank.li/linux.git tags/imx-fixes-7.0-2nd
>
> for you to fetch changes up to 42a9f5a16328ed78a88e0498556965b6c6ec515c:
>
> arm64: dts: imx8mm-tqma8mqml: Correct PAD settings for PMIC_nINT (2026-04-02 22:07:41 -0400)
>
> ----------------------------------------------------------------
> i.MX fixes for 7.0 2nd round:
>
> - Fixes interrupt storm by adding pull up pinctrl config for pin PMIC_nINT.
This is way too vague. Commits are odd and suggest that you rely on
driver. Or that DTS and driver are inter-connected. That is a warning
sign. You need to explain all this here. We had internal discussion
about without clear resolution, so I decide to merge it.
But in future this is your message to convince SoC maintainers that
such DTS changes are correct from rules point of view.
Thanks, applied
Best regards,
Krzysztof
prev parent reply other threads:[~2026-04-11 8:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-04 0:18 [GIT PULL] i.MX fixes for 7.0 round 2 Frank Li
2026-04-11 8:14 ` Krzysztof Kozlowski [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=20260411-ancient-okapi-of-excitement-e5e22f@quoll \
--to=krzk@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=arm@kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--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