public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: <Claudiu.Beznea@microchip.com>
To: <michael@walle.cc>, <Kavyasree.Kotagiri@microchip.com>,
	<Nicolas.Ferre@microchip.com>
Cc: <arnd@arndb.de>, <olof@lixom.net>, <soc@kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<robh+dt@kernel.org>, <krzysztof.kozlowski@canonical.com>,
	<alexandre.belloni@bootlin.com>
Subject: Re: [PATCH v1 1/6] ARM: dts: lan966x: swap dma channels for crypto node
Date: Fri, 4 Mar 2022 08:21:09 +0000	[thread overview]
Message-ID: <4de4a132-46d8-c8f7-dfe0-e9fae5dee808@microchip.com> (raw)
In-Reply-To: <20220303160323.3316317-2-michael@walle.cc>

On 03.03.2022 18:03, Michael Walle wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> The YAML binding (crypto/atmel,at91sam9g46-aes.yaml) mandates the order
> of the channels. Swap them to pass devicetree validation.
> 
> Fixes: 290deaa10c50 ("ARM: dts: add DT for lan966 SoC and 2-port board pcb8291")
> Signed-off-by: Michael Walle <michael@walle.cc>

Reviewed-by: Claudiu Beznea <claudiu.beznea@microchip.com>

> ---
>  arch/arm/boot/dts/lan966x.dtsi | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/arch/arm/boot/dts/lan966x.dtsi b/arch/arm/boot/dts/lan966x.dtsi
> index 7d2869648050..5e9cbc8cdcbc 100644
> --- a/arch/arm/boot/dts/lan966x.dtsi
> +++ b/arch/arm/boot/dts/lan966x.dtsi
> @@ -114,9 +114,9 @@ aes: crypto@e004c000 {
>                         compatible = "atmel,at91sam9g46-aes";
>                         reg = <0xe004c000 0x100>;
>                         interrupts = <GIC_SPI 53 IRQ_TYPE_LEVEL_HIGH>;
> -                       dmas = <&dma0 AT91_XDMAC_DT_PERID(13)>,
> -                              <&dma0 AT91_XDMAC_DT_PERID(12)>;
> -                       dma-names = "rx", "tx";
> +                       dmas = <&dma0 AT91_XDMAC_DT_PERID(12)>,
> +                              <&dma0 AT91_XDMAC_DT_PERID(13)>;
> +                       dma-names = "tx", "rx";
>                         clocks = <&nic_clk>;
>                         clock-names = "aes_clk";
>                 };
> --
> 2.30.2
> 


  reply	other threads:[~2022-03-04  8:21 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-03 16:03 [PATCH v1 0/6] ARM: dts: lan966x: dtsi improvements and KSwitch D10 support Michael Walle
2022-03-03 16:03 ` [PATCH v1 1/6] ARM: dts: lan966x: swap dma channels for crypto node Michael Walle
2022-03-04  8:21   ` Claudiu.Beznea [this message]
2022-03-03 16:03 ` [PATCH v1 2/6] ARM: dts: lan966x: add sgpio node Michael Walle
2022-03-04  8:24   ` Claudiu.Beznea
2022-03-03 16:03 ` [PATCH v1 3/6] ARM: dts: lan966x: add all flexcom usart nodes Michael Walle
2022-03-04  8:30   ` Claudiu.Beznea
2022-03-04 11:01     ` Michael Walle
2022-03-07 11:53       ` Claudiu.Beznea
2022-03-07 12:04         ` Michael Walle
2022-03-18 12:17           ` Claudiu.Beznea
2022-03-22 21:39             ` Michael Walle
2022-03-24 16:32               ` Claudiu.Beznea
2022-03-03 16:03 ` [PATCH v1 4/6] ARM: dts: lan966x: add flexcom SPI nodes Michael Walle
2022-03-04  8:30   ` Claudiu.Beznea
2022-03-03 16:03 ` [PATCH v1 5/6] ARM: dts: lan966x: add flexcom I2C nodes Michael Walle
2022-03-03 16:03 ` [PATCH v1 6/6] ARM: dts: lan966x: add basic Kontron KSwitch D10 support Michael Walle
2022-03-04  8:31   ` Claudiu.Beznea
2022-03-04 11:15     ` Michael Walle
2022-03-07 12:07       ` Claudiu.Beznea
2022-03-07 12:17         ` Michael Walle
2022-03-18 12:26           ` Claudiu.Beznea
2022-03-23  8:06     ` Tudor.Ambarus

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=4de4a132-46d8-c8f7-dfe0-e9fae5dee808@microchip.com \
    --to=claudiu.beznea@microchip.com \
    --cc=Kavyasree.Kotagiri@microchip.com \
    --cc=Nicolas.Ferre@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski@canonical.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael@walle.cc \
    --cc=olof@lixom.net \
    --cc=robh+dt@kernel.org \
    --cc=soc@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