[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <68dcdefe-0c16-4f0a-820e-d697b862615c@nvidia.com>
Date: Thu, 27 Feb 2025 11:13:54 +0000
From: Jon Hunter <jonathanh@...dia.com>
To: Vishwaroop A <va@...dia.com>, thierry.reding@...il.com,
skomatineni@...dia.com, ldewangan@...dia.com, broonie@...nel.org,
linux-spi@...r.kernel.org, linux-tegra@...r.kernel.org,
linux-kernel@...r.kernel.org, kyarlagadda@...dia.com, smangipudi@...dia.com
Subject: Re: [PATCH v2 1/6] arm64: tegra: Configure QSPI clocks and add DMA
On 12/02/2025 14:46, Vishwaroop A wrote:
> Set QSPI0_2X_PM to 199.99 MHz and QSPI0_PM to 99.99 MHz using
> PLLC as the parent clock. These frequencies allow Quad IO DT
> reads up to 99.99 MHz, which is the fastest that can be
> achieved considering various PLL and clock divider constraints.
>
> Populate the DMA and IOMMU properties for the Tegra234 QSPI devices to
> enable DMA support.
>
> Signed-off-by: Vishwaroop A <va@...dia.com>
> ---
> arch/arm64/boot/dts/nvidia/tegra234.dtsi | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/nvidia/tegra234.dtsi b/arch/arm64/boot/dts/nvidia/tegra234.dtsi
> index 2601b43b2d8c..0ac2d3aba930 100644
> --- a/arch/arm64/boot/dts/nvidia/tegra234.dtsi
> +++ b/arch/arm64/boot/dts/nvidia/tegra234.dtsi
> @@ -2948,6 +2948,13 @@
> <&bpmp TEGRA234_CLK_QSPI0_PM>;
> clock-names = "qspi", "qspi_out";
> resets = <&bpmp TEGRA234_RESET_QSPI0>;
> + assigned-clocks = <&bpmp TEGRA234_CLK_QSPI0_2X_PM>,
> + <&bpmp TEGRA234_CLK_QSPI0_PM>;
> + assigned-clock-rates = <199999999 99999999>;
> + assigned-clock-parents = <&bpmp TEGRA234_CLK_PLLC>;
> + dma-names = "rx", "tx";
> + dma-coherent;
> + iommus = <&smmu_niso1 TEGRA234_SID_QSPI0>;
> status = "disabled";
> };
>
> @@ -3031,6 +3038,13 @@
> <&bpmp TEGRA234_CLK_QSPI1_PM>;
> clock-names = "qspi", "qspi_out";
> resets = <&bpmp TEGRA234_RESET_QSPI1>;
> + assigned-clocks = <&bpmp TEGRA234_CLK_QSPI1_2X_PM>,
> + <&bpmp TEGRA234_CLK_QSPI1_PM>;
> + assigned-clock-rates = <199999999 99999999>;
> + assigned-clock-parents = <&bpmp TEGRA234_CLK_PLLC>;
> + dma-names = "rx", "tx";
> + dma-coherent;
> + iommus = <&smmu_niso1 TEGRA234_SID_QSPI1>;
> status = "disabled";
> };
>
Make sure you CC the DT mailing list on this.
With this change I am seeing the following warnings ...
arch/arm64/boot/dts/nvidia/tegra234-p3737-0000+p3701-0000.dtb: spi@...0000: Unevaluated properties are not allowed ('dma-coherent', 'iommus' were unexpected)
from schema $id: http://devicetree.org/schemas/spi/nvidia,tegra210-quad.yaml#
DTC [C] arch/arm64/boot/dts/nvidia/tegra234-p3737-0000+p3701-0008.dtb
arch/arm64/boot/dts/nvidia/tegra234-p3737-0000+p3701-0008.dtb: spi@...0000: Unevaluated properties are not allowed ('dma-coherent', 'iommus' were unexpected)
from schema $id: http://devicetree.org/schemas/spi/nvidia,tegra210-quad.yaml#
DTC [C] arch/arm64/boot/dts/nvidia/tegra234-p3740-0002+p3701-0008.dtb
arch/arm64/boot/dts/nvidia/tegra234-p3740-0002+p3701-0008.dtb: spi@...0000: Unevaluated properties are not allowed ('dma-coherent', 'iommus' were unexpected)
from schema $id: http://devicetree.org/schemas/spi/nvidia,tegra210-quad.yaml#
DTC [C] arch/arm64/boot/dts/nvidia/tegra234-p3768-0000+p3767-0000.dtb
arch/arm64/boot/dts/nvidia/tegra234-p3768-0000+p3767-0000.dtb: spi@...0000: Unevaluated properties are not allowed ('dma-coherent', 'iommus' were unexpected)
from schema $id: http://devicetree.org/schemas/spi/nvidia,tegra210-quad.yaml#
DTC [C] arch/arm64/boot/dts/nvidia/tegra234-p3768-0000+p3767-0005.dtb
arch/arm64/boot/dts/nvidia/tegra234-p3768-0000+p3767-0005.dtb: spi@...0000: Unevaluated properties are not allowed ('dma-coherent', 'iommus' were unexpected)
from schema $id: http://devicetree.org/schemas/spi/nvidia,tegra210-quad.yaml#
Jon
--
nvpublic
Powered by blists - more mailing lists