From: Shawn Guo <shawnguo2@yeah.net>
To: Christoph Niedermaier <cniedermaier@dh-electronics.com>
Cc: linux-arm-kernel@lists.infradead.org,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>, Marek Vasut <marex@denx.de>,
Fabio Estevam <festevam@denx.de>,
NXP Linux Team <linux-imx@nxp.com>,
kernel@dh-electronics.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: imx6ull-dhcom: Remove /omit-if-no-ref/ from node usdhc1-pwrseq
Date: Tue, 6 Feb 2024 16:25:03 +0800 [thread overview]
Message-ID: <ZcHs36/WVSlBQxcQ@dragon> (raw)
In-Reply-To: <20240125124621.16011-1-cniedermaier@dh-electronics.com>
On Thu, Jan 25, 2024 at 01:46:21PM +0100, Christoph Niedermaier wrote:
> Remove /omit-if-no-ref/ from node usdhc1-pwrseq, because if the compile
> flag -@ (include symbols) is used the node will always be there. In this
> case, GPIO H is not released and therefore cannot be used. Therefore,
> remove this node manually from the corresponding devicetree file and
> don't rely on /omit-if-no-ref/.
>
> Signed-off-by: Christoph Niedermaier <cniedermaier@dh-electronics.com>
Applied, thanks!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo2@yeah.net>
To: Christoph Niedermaier <cniedermaier@dh-electronics.com>
Cc: linux-arm-kernel@lists.infradead.org,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>, Marek Vasut <marex@denx.de>,
Fabio Estevam <festevam@denx.de>,
NXP Linux Team <linux-imx@nxp.com>,
kernel@dh-electronics.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: imx6ull-dhcom: Remove /omit-if-no-ref/ from node usdhc1-pwrseq
Date: Tue, 6 Feb 2024 16:25:03 +0800 [thread overview]
Message-ID: <ZcHs36/WVSlBQxcQ@dragon> (raw)
In-Reply-To: <20240125124621.16011-1-cniedermaier@dh-electronics.com>
On Thu, Jan 25, 2024 at 01:46:21PM +0100, Christoph Niedermaier wrote:
> Remove /omit-if-no-ref/ from node usdhc1-pwrseq, because if the compile
> flag -@ (include symbols) is used the node will always be there. In this
> case, GPIO H is not released and therefore cannot be used. Therefore,
> remove this node manually from the corresponding devicetree file and
> don't rely on /omit-if-no-ref/.
>
> Signed-off-by: Christoph Niedermaier <cniedermaier@dh-electronics.com>
Applied, thanks!
next prev parent reply other threads:[~2024-02-06 8:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 12:46 [PATCH] ARM: dts: imx6ull-dhcom: Remove /omit-if-no-ref/ from node usdhc1-pwrseq Christoph Niedermaier
2024-01-25 12:46 ` Christoph Niedermaier
2024-02-06 8:25 ` Shawn Guo [this message]
2024-02-06 8:25 ` 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=ZcHs36/WVSlBQxcQ@dragon \
--to=shawnguo2@yeah.net \
--cc=cniedermaier@dh-electronics.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@denx.de \
--cc=kernel@dh-electronics.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=robh+dt@kernel.org \
--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 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.