From: Shawn Guo <shawnguo2@yeah.net>
To: max.oss.09@gmail.com
Cc: Max Krummenacher <max.krummenacher@toradex.com>,
Conor Dooley <conor+dt@kernel.org>,
Daniel Baluta <daniel.baluta@nxp.com>,
Fabio Estevam <festevam@gmail.com>,
Hiago De Franco <hiago.franco@toradex.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Rob Herring <robh@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
Vitor Soares <vitor.soares@toradex.com>,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/2] arm64: dts: freescale: imx8mp-toradex-smarc: remove gpio-hog on lvds_dsi_sel
Date: Fri, 11 Jul 2025 16:08:07 +0800 [thread overview]
Message-ID: <aHDGZz6C50CbeTz5@dragon> (raw)
In-Reply-To: <20250708135300.2855155-1-max.oss.09@gmail.com>
On Tue, Jul 08, 2025 at 03:51:40PM +0200, max.oss.09@gmail.com wrote:
> From: Max Krummenacher <max.krummenacher@toradex.com>
>
> The LVDS_DSI_SEL does not leave the SoM, so do its pinmuxing on the SoM dtsi and don't
> leave that to a carrier board dts file.
>
> Using a pull down on the LVDS_DSI_SEL signal is enough to have the signal not floating
> and have the SoM in a defined state.
> Thus remove the gpio-hog used on the line and leave this to carrier board dts files or
> overlays to use the signal as needed.
>
>
> Max Krummenacher (2):
> arm64: dts: freescale: imx8mp-toradex-smarc: fix lvds dsi mux gpio
> arm64: dts: freescale: imx8mp-toradex-smarc: remove gpio hog
Applied both, thanks!
prev parent reply other threads:[~2025-07-11 8:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 13:51 [PATCH v1 0/2] arm64: dts: freescale: imx8mp-toradex-smarc: remove gpio-hog on lvds_dsi_sel max.oss.09
2025-07-08 13:51 ` [PATCH v1 1/2] arm64: dts: freescale: imx8mp-toradex-smarc: fix lvds dsi mux gpio max.oss.09
2025-07-08 13:51 ` [PATCH v1 2/2] arm64: dts: freescale: imx8mp-toradex-smarc: remove gpio hog max.oss.09
2025-07-11 8:08 ` Shawn Guo [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=aHDGZz6C50CbeTz5@dragon \
--to=shawnguo2@yeah.net \
--cc=conor+dt@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=hiago.franco@toradex.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=max.krummenacher@toradex.com \
--cc=max.oss.09@gmail.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=vitor.soares@toradex.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.