From: "alexander.feilke@ew.tq-group.com" <alexander.feilke@ew.tq-group.com>
To: "Frank Li" <Frank.li@nxp.com>
Cc: "Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Fabio Estevam" <festevam@gmail.com>,
linux@ew.tq-group.com, devicetree@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] ARM: dts: imx7-mba7: disable boot_cfg pins after boot
Date: Wed, 18 Feb 2026 17:55:14 +0100 [thread overview]
Message-ID: <19f328-6995ef00-67-b89a9f0@203920772> (raw)
In-Reply-To: <aZXr_r1VEx5kcl7g@lizhi-Precision-Tower-5810>
On Wednesday, February 18, 2026 17:42 CET, Frank Li <Frank.li@nxp.com> wrote:
> On Wed, Feb 18, 2026 at 02:54:14PM +0100, Alexander Feilke wrote:
> > The BOOT_CFG pins are located on the LCD bus on our starterkit.
> > Disable them after boot to separate those signals.
>
> Your comments is more clear. Is below commit massage better?
>
> ARM: dts: imx7-mba7: Deassert BOOT_EN to separate BOOT_CFG circuits after boot
>
> Deassert BOOT_EN after boot to separate BOOT_CFG circuits from LCD signals.
>
> Frank
Agreed. I can send an updated patch if the rest seems ok
next prev parent reply other threads:[~2026-02-18 16:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 13:54 [PATCH 0/3] ARM: dts: TQMa7: modify for use in bootloaders Alexander Feilke
2026-02-18 13:54 ` [PATCH 1/3] ARM: dts: imx7s: add boot phase properties Alexander Feilke
2026-02-18 13:54 ` [PATCH 2/3] ARM: dts: tqma7: " Alexander Feilke
2026-02-18 13:54 ` [PATCH 3/3] ARM: dts: imx7-mba7: disable boot_cfg pins after boot Alexander Feilke
2026-02-18 16:42 ` Frank Li
2026-02-18 16:55 ` alexander.feilke [this message]
2026-02-18 17:17 ` [PATCH 3/3 v2] ARM: dts: imx7-mba7: separate BOOT_CFG circuits " alexander.feilke
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=19f328-6995ef00-67-b89a9f0@203920772 \
--to=alexander.feilke@ew.tq-group.com \
--cc=Frank.li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@ew.tq-group.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
/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