From: <Claudiu.Beznea@microchip.com>
To: <Ludovic.Desroches@microchip.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>
Cc: <alexandre.belloni@bootlin.com>, <stable@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: dts: at91: sama5d4: fix pinctrl muxing
Date: Fri, 25 Oct 2019 09:15:59 +0000 [thread overview]
Message-ID: <e2d81b87-408d-b50d-3e4c-b28367e4cb00@microchip.com> (raw)
In-Reply-To: <20191025084210.14726-1-ludovic.desroches@microchip.com>
On 25.10.2019 11:42, Ludovic Desroches wrote:
> External E-Mail
>
>
> Fix pinctrl muxing, PD28, PD29 and PD31 can be muxed to peripheral A. It
> allows to use SCK0, SCK1 and SPI0_NPCS2 signals.
>
> Signed-off-by: Ludovic Desroches <ludovic.desroches@microchip.com>
> Fixes: 679f8d92bb01 ("ARM: at91/dt: sama5d4: add pioD pin mux mask and enable pioD")
> Cc: stable@vger.kernel.org
Reviewed-by: Claudiu Beznea <claudiu.beznea@microchip.com>
> ---
> arch/arm/boot/dts/sama5d4.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/sama5d4.dtsi b/arch/arm/boot/dts/sama5d4.dtsi
> index 6ab27a7b388d..a4cef07c38cb 100644
> --- a/arch/arm/boot/dts/sama5d4.dtsi
> +++ b/arch/arm/boot/dts/sama5d4.dtsi
> @@ -914,7 +914,7 @@ /* A B C */
> 0xffffffff 0x3ffcfe7c 0x1c010101 /* pioA */
> 0x7fffffff 0xfffccc3a 0x3f00cc3a /* pioB */
> 0xffffffff 0x3ff83fff 0xff00ffff /* pioC */
> - 0x0003ff00 0x8002a800 0x00000000 /* pioD */
> + 0xb003ff00 0x8002a800 0x00000000 /* pioD */
> 0xffffffff 0x7fffffff 0x76fff1bf /* pioE */
> >;
>
>
next prev parent reply other threads:[~2019-10-25 9:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 8:42 [PATCH] ARM: dts: at91: sama5d4: fix pinctrl muxing Ludovic Desroches
2019-10-25 9:15 ` Claudiu.Beznea [this message]
2021-06-02 11:55 ` 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=e2d81b87-408d-b50d-3e4c-b28367e4cb00@microchip.com \
--to=claudiu.beznea@microchip.com \
--cc=Ludovic.Desroches@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.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