From: Thierry Reding <thierry.reding@gmail.com>
To: Brad Griffis <bgriffis@nvidia.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH 2/2] arm64: tegra: fix p3767 QSPI speed
Date: Fri, 21 Jul 2023 08:26:04 +0200 [thread overview]
Message-ID: <ZLok_Lg6B_ggDzR9@orome> (raw)
In-Reply-To: <20230626180920.318774-2-bgriffis@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 1258 bytes --]
On Mon, Jun 26, 2023 at 06:09:20PM +0000, Brad Griffis wrote:
> The QSPI device used in Jetson Orin NX and Nano modules (p3767) is
> the same as Jetson AGX Orin (p3701) and should have a max speed of
> 102 MHz.
>
> Fixes: 13b0aca303e9 ("arm64: tegra: Support Jetson Orin NX")
> Signed-off-by: Brad Griffis <bgriffis@nvidia.com>
> ---
> arch/arm64/boot/dts/nvidia/tegra234-p3767.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
This was originally copied from the downstream DTB and I see 136 MHz for
both P3701 and P3767 there. So now I wonder which one is correct. Should
perhaps the P3701 be updated to 136 MHz instead if that's what is being
used downstream?
Thierry
> diff --git a/arch/arm64/boot/dts/nvidia/tegra234-p3767.dtsi b/arch/arm64/boot/dts/nvidia/tegra234-p3767.dtsi
> index 831a553ec387..980f15ac674d 100644
> --- a/arch/arm64/boot/dts/nvidia/tegra234-p3767.dtsi
> +++ b/arch/arm64/boot/dts/nvidia/tegra234-p3767.dtsi
> @@ -28,7 +28,7 @@ spi@3270000 {
> flash@0 {
> compatible = "jedec,spi-nor";
> reg = <0>;
> - spi-max-frequency = <136000000>;
> + spi-max-frequency = <102000000>;
> spi-tx-bus-width = <4>;
> spi-rx-bus-width = <4>;
> };
> --
> 2.25.1
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-07-21 6:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 18:09 [PATCH 1/2] arm64: tegra: fix p3767 card detect polarity Brad Griffis
2023-06-26 18:09 ` [PATCH 2/2] arm64: tegra: fix p3767 QSPI speed Brad Griffis
2023-07-21 6:26 ` Thierry Reding [this message]
2023-08-15 13:38 ` Brad Griffis
2023-08-16 16:17 ` Thierry Reding
2023-07-21 6:21 ` [PATCH 1/2] arm64: tegra: fix p3767 card detect polarity Thierry Reding
2023-08-15 13:37 ` Brad Griffis
2023-08-16 16:18 ` Thierry Reding
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=ZLok_Lg6B_ggDzR9@orome \
--to=thierry.reding@gmail.com \
--cc=bgriffis@nvidia.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).