From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: Hari Prasath <Hari.PrasathGE@microchip.com>,
<claudiu.beznea@microchip.com>, <davem@davemloft.net>,
<alexandre.belloni@bootlin.com>,
<ludovic.desroches@microchip.com>, <robh+dt@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux@armlinux.org.uk>
Subject: Re: [PATCH] ARM: dts: at91: update alternate function of signal PD20
Date: Wed, 8 Dec 2021 12:05:29 +0100 [thread overview]
Message-ID: <47dc40fb-aaa7-dedd-034c-465f39a5a83f@microchip.com> (raw)
In-Reply-To: <20211208063553.19807-1-Hari.PrasathGE@microchip.com>
On 08/12/2021 at 07:35, Hari Prasath wrote:
> The alternate function of PD20 is 4 as per the datasheet of
> sama7g5 and not 5 as defined earlier.
>
> Fixes: 7540629e2fc7 ("ARM: dts: at91: add sama7g5 SoC DT and sama7g5-ek")
> Signed-off-by: Hari Prasath <Hari.PrasathGE@microchip.com>
Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com>
Thanks Hari. Best regards,
Nicolas
> ---
> arch/arm/boot/dts/sama7g5-pinfunc.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/sama7g5-pinfunc.h b/arch/arm/boot/dts/sama7g5-pinfunc.h
> index 22fe9e522a97..4eb30445d205 100644
> --- a/arch/arm/boot/dts/sama7g5-pinfunc.h
> +++ b/arch/arm/boot/dts/sama7g5-pinfunc.h
> @@ -765,7 +765,7 @@
> #define PIN_PD20__PCK0 PINMUX_PIN(PIN_PD20, 1, 3)
> #define PIN_PD20__FLEXCOM2_IO3 PINMUX_PIN(PIN_PD20, 2, 2)
> #define PIN_PD20__PWMH3 PINMUX_PIN(PIN_PD20, 3, 4)
> -#define PIN_PD20__CANTX4 PINMUX_PIN(PIN_PD20, 5, 2)
> +#define PIN_PD20__CANTX4 PINMUX_PIN(PIN_PD20, 4, 2)
> #define PIN_PD20__FLEXCOM5_IO0 PINMUX_PIN(PIN_PD20, 6, 5)
> #define PIN_PD21 117
> #define PIN_PD21__GPIO PINMUX_PIN(PIN_PD21, 0, 0)
>
--
Nicolas Ferre
prev parent reply other threads:[~2021-12-08 11:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 6:35 [PATCH] ARM: dts: at91: update alternate function of signal PD20 Hari Prasath
2021-12-08 11:05 ` Nicolas Ferre [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=47dc40fb-aaa7-dedd-034c-465f39a5a83f@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=Hari.PrasathGE@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@microchip.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--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