From: Jon Hunter <jonathanh@nvidia.com>
To: Vishwaroop A <va@nvidia.com>,
thierry.reding@gmail.com, skomatineni@nvidia.com,
ldewangan@nvidia.com, broonie@kernel.org,
linux-spi@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org, kyarlagadda@nvidia.com,
smangipudi@nvidia.com
Subject: Re: [PATCH v3 4/6] arm64: tegra: Configure QSPI clocks and add DMA
Date: Wed, 16 Apr 2025 15:11:27 +0100 [thread overview]
Message-ID: <a71d147c-ea95-41e6-b631-f889a18888d4@nvidia.com> (raw)
In-Reply-To: <20250416110606.2737315-5-va@nvidia.com>
On 16/04/2025 12:06, Vishwaroop A wrote:
> For Tegra234 devices, set QSPI0_2X_PM to 199.99 MHz and QSPI0_PM to
> 99.99 MHz using PLLC as the parent clock. These frequencies enable
> Quad IO reads at up to 99.99 MHz, the maximum achievable given PLL
> and clock divider limitations.
No mention of adding the iommus property here.
> Signed-off-by: Vishwaroop A <va@nvidia.com>
> ---
> arch/arm64/boot/dts/nvidia/tegra234.dtsi | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/nvidia/tegra234.dtsi b/arch/arm64/boot/dts/nvidia/tegra234.dtsi
> index 2601b43b2d8c..419dde2bfdf9 100644
> --- a/arch/arm64/boot/dts/nvidia/tegra234.dtsi
> +++ b/arch/arm64/boot/dts/nvidia/tegra234.dtsi
> @@ -2948,6 +2948,11 @@
> <&bpmp TEGRA234_CLK_QSPI0_PM>;
> clock-names = "qspi", "qspi_out";
> resets = <&bpmp TEGRA234_RESET_QSPI0>;
> + iommus = <&smmu_niso1 TEGRA234_SID_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>;
> status = "disabled";
> };
>
> @@ -3031,6 +3036,11 @@
> <&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>;
> + iommus = <&smmu_niso1 TEGRA234_SID_QSPI1>;
Please be consistent with the ordering of properties.
> status = "disabled";
> };
>
--
nvpublic
next prev parent reply other threads:[~2025-04-16 14:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 11:06 [PATCH v3 0/6] Configure Clocks, Add Internal DMA support Vishwaroop A
2025-04-16 11:06 ` [PATCH v3 1/6] spi: tegra210-quad: Fix X1_X2_X4 encoding and support x4 transfers Vishwaroop A
2025-04-16 11:06 ` [PATCH v3 2/6] spi: tegra210-quad: remove redundant error handling code Vishwaroop A
2025-04-16 11:06 ` [PATCH v3 3/6] spi: tegra210-quad: modify chip select (CS) deactivation Vishwaroop A
2025-04-16 11:06 ` [PATCH v3 4/6] arm64: tegra: Configure QSPI clocks and add DMA Vishwaroop A
2025-04-16 14:11 ` Jon Hunter [this message]
2025-04-16 11:06 ` [PATCH v3 5/6] spi: tegra210-quad: Update dummy sequence configuration Vishwaroop A
2025-04-16 11:06 ` [PATCH v3 6/6] spi: tegra210-quad: Add support for internal DMA Vishwaroop A
2025-04-16 11:57 ` Mukesh Kumar Savaliya
2025-04-16 12:23 ` Mark Brown
2025-04-16 14:08 ` Jon Hunter
2025-04-24 13:29 ` Mark Brown
2025-04-16 12:43 ` [PATCH v3 0/6] Configure Clocks, Add Internal DMA support Rob Herring (Arm)
2025-04-25 23:00 ` (subset) " Mark Brown
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=a71d147c-ea95-41e6-b631-f889a18888d4@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=broonie@kernel.org \
--cc=kyarlagadda@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=skomatineni@nvidia.com \
--cc=smangipudi@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=va@nvidia.com \
/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