From: Frieder Schrempf <frieder.schrempf@kontron.de>
To: Marek Vasut <marex@denx.de>, linux-arm-kernel@lists.infradead.org
Cc: Andrejs Cainikovs <andrejs.cainikovs@toradex.com>,
Fabio Estevam <festevam@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Marcel Ziswiler <marcel.ziswiler@toradex.com>,
Max Krummenacher <max.krummenacher@toradex.com>,
NXP Linux Team <linux-imx@nxp.com>, Peng Fan <peng.fan@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Philippe Schenker <philippe.schenker@toradex.com>,
Rob Herring <robh+dt@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH 2/3] arm64: dts: imx8mp: Drop sd-vsel-gpios from i.MX8M Plus Verdin SoM
Date: Wed, 18 Jan 2023 08:39:55 +0100 [thread overview]
Message-ID: <a1d55736-cb3e-2e52-b58a-cf12cd5aa833@kontron.de> (raw)
In-Reply-To: <20230118030757.254086-2-marex@denx.de>
On 18.01.23 04:07, Marek Vasut wrote:
> The VSELECT pin is configured as MX8MP_IOMUXC_GPIO1_IO04__USDHC2_VSELECT
> and not as a GPIO, drop the bogus sd-vsel-gpios property as the eSDHC
> block handles the VSELECT pin on its own.
>
> Signed-off-by: Marek Vasut <marex@denx.de>
Reviewed-by: Frieder Schrempf <frieder.schrempf@kontron.de>
next prev parent reply other threads:[~2023-01-18 8:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 3:07 [PATCH 1/3] arm64: dts: imx8mm: Drop sd-vsel-gpios from i.MX8M Mini Verdin SoM Marek Vasut
2023-01-18 3:07 ` [PATCH 2/3] arm64: dts: imx8mp: Drop sd-vsel-gpios from i.MX8M Plus " Marek Vasut
2023-01-18 7:39 ` Frieder Schrempf [this message]
2023-01-18 8:42 ` Max Krummenacher
2023-01-18 3:07 ` [PATCH 3/3] arm64: dts: imx8mp: Drop sd-vsel-gpios from i.MX8M Plus DHCOM SoM Marek Vasut
2023-01-18 7:40 ` Frieder Schrempf
2023-01-18 7:39 ` [PATCH 1/3] arm64: dts: imx8mm: Drop sd-vsel-gpios from i.MX8M Mini Verdin SoM Frieder Schrempf
2023-01-18 8:41 ` Max Krummenacher
2023-01-26 7:58 ` Shawn Guo
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=a1d55736-cb3e-2e52-b58a-cf12cd5aa833@kontron.de \
--to=frieder.schrempf@kontron.de \
--cc=andrejs.cainikovs@toradex.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=marcel.ziswiler@toradex.com \
--cc=marex@denx.de \
--cc=max.krummenacher@toradex.com \
--cc=peng.fan@nxp.com \
--cc=philippe.schenker@toradex.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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