From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: Claudiu Beznea <claudiu.beznea@microchip.com>,
<alexandre.belloni@bootlin.com>,
<ludovic.desroches@microchip.com>, <robh+dt@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] ARM: dts: at91: add conflict note for d3
Date: Tue, 27 Jul 2021 10:54:05 +0200 [thread overview]
Message-ID: <ca86505c-9872-8605-5887-c1c6532ca186@microchip.com> (raw)
In-Reply-To: <20210727074006.1609989-2-claudiu.beznea@microchip.com>
On 27/07/2021 at 09:40, Claudiu Beznea wrote:
> Pin feeding d3 led may be in conflict with EBI CS0, USART2 CTS.
> Add a note for this.
>
> Signed-off-by: Claudiu Beznea <claudiu.beznea@microchip.com>
Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com>
Queued for 5.15 in at91-dt.
Regards,
Nicolas
> ---
> arch/arm/boot/dts/at91-sama5d3_xplained.dts | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/at91-sama5d3_xplained.dts b/arch/arm/boot/dts/at91-sama5d3_xplained.dts
> index cc55d1684322..d72c042f2850 100644
> --- a/arch/arm/boot/dts/at91-sama5d3_xplained.dts
> +++ b/arch/arm/boot/dts/at91-sama5d3_xplained.dts
> @@ -399,7 +399,7 @@ d2 {
> };
>
> d3 {
> - label = "d3";
> + label = "d3"; /* Conflict with EBI CS0, USART2 CTS. */
> gpios = <&pioE 24 GPIO_ACTIVE_HIGH>;
> };
> };
>
--
Nicolas Ferre
next prev parent reply other threads:[~2021-07-27 8:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 7:40 [PATCH 1/2] ARM: dts: at91: add pinctrl-{names, 0} for all gpios Claudiu Beznea
2021-07-27 7:40 ` [PATCH 2/2] ARM: dts: at91: add conflict note for d3 Claudiu Beznea
2021-07-27 8:54 ` Nicolas Ferre [this message]
2021-07-27 8:53 ` [PATCH 1/2] ARM: dts: at91: add pinctrl-{names, 0} for all gpios Nicolas Ferre
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=ca86505c-9872-8605-5887-c1c6532ca186@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=robh+dt@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
all inboxes | Powered by JetHome®