[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <01250e59-eb49-43fb-666e-c1592d9dc922@linaro.org>
Date: Thu, 7 Apr 2022 14:07:32 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Kavyasree Kotagiri <kavyasree.kotagiri@...rochip.com>,
arnd@...db.de, robh+dt@...nel.org, krzk+dt@...nel.org,
alexandre.belloni@...tlin.com, olof@...om.net, soc@...nel.org,
nicolas.ferre@...rochip.com
Cc: linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, UNGLinuxDriver@...rochip.com,
tudor.ambarus@...rochip.com, Manohar.Puri@...rochip.com
Subject: Re: [PATCH 1/2] ARM: dts: lan966x: Add QSPI nodes
Thank you for your patch. There is something to discuss/improve.
This should be sent with your DT bindings patch in one patchset.
On 07/04/2022 12:58, Kavyasree Kotagiri wrote:
> LAN966x SoC supports 3 instances of QSPI.
> Data and clock of qspi0, qspi1, qspi2 works upto 100Mhz.
s/upto/up to/
>
> Signed-off-by: Kavyasree Kotagiri <kavyasree.kotagiri@...rochip.com>
> ---
> arch/arm/boot/dts/lan966x.dtsi | 48 ++++++++++++++++++++++++++++++++++
> 1 file changed, 48 insertions(+)
>
> diff --git a/arch/arm/boot/dts/lan966x.dtsi b/arch/arm/boot/dts/lan966x.dtsi
> index 7d2869648050..b3c687db0aea 100644
> --- a/arch/arm/boot/dts/lan966x.dtsi
> +++ b/arch/arm/boot/dts/lan966x.dtsi
> @@ -196,6 +196,54 @@
> status = "disabled";
> };
>
> + qspi0: spi@...04000 {
> + compatible = "microchip,lan966x-qspi";
> + reg = <0xe0804000 0x100>,
> + <0x20000000 0x08000000>;
> + reg-names = "qspi_base", "qspi_mmap";
> + interrupts = <GIC_SPI 45 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&clks GCK_ID_QSPI0>;
> + clock-names = "gclk";
This is not correct with the DT schema.
> + dmas = <&dma0 AT91_XDMAC_DT_PERID(0)>,
> + <&dma0 AT91_XDMAC_DT_PERID(1)>;
> + dma-names = "rx", "tx";
This as well.
You can test schema with 'make dtbs_check DT_SCHEMA_FILES=...."
(check the docs for help what is needed to do it).
Best regards,
Krzysztof
Powered by blists - more mailing lists