devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vishwaroop A <va@nvidia.com>
To: <robh@kernel.org>, <jonathanh@nvidia.com>, <krzk+dt@kernel.org>,
	<conor+dt@kernel.org>, <thierry.reding@gmail.com>,
	<broonie@kernel.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
	<linux-spi@vger.kernel.org>
Cc: Vishwaroop A <va@nvidia.com>
Subject: [PATCH 1/3] arm64: tegra: Add spidev nodes for SPI controllers
Date: Tue, 26 Nov 2024 13:45:27 +0000	[thread overview]
Message-ID: <20241126134529.936451-2-va@nvidia.com> (raw)
In-Reply-To: <20241126134529.936451-1-va@nvidia.com>

Add spidev nodes to two existing SPI controllers on the
NVIDIA Tegra234 SoC. These additions enable user-space
SPI device support for testing and development purposes.
Specifies a maximum frequency of 81MHz for each spidev node.

The 81MHz maximum frequency is defined to ensure stable operation
while allowing for high-speed SPI communication. This frequency
can be adjusted based on specific hardware capabilities and
requirements.

Signed-off-by: Vishwaroop A <va@nvidia.com>
---
 .../dts/nvidia/tegra234-p3737-0000+p3701.dtsi | 28 +++++++++++++++++++
 1 file changed, 28 insertions(+)

diff --git a/arch/arm64/boot/dts/nvidia/tegra234-p3737-0000+p3701.dtsi b/arch/arm64/boot/dts/nvidia/tegra234-p3737-0000+p3701.dtsi
index f6cad29355e6..17de3d0feb45 100644
--- a/arch/arm64/boot/dts/nvidia/tegra234-p3737-0000+p3701.dtsi
+++ b/arch/arm64/boot/dts/nvidia/tegra234-p3737-0000+p3701.dtsi
@@ -84,6 +84,34 @@
 			};
 		};
 
+		spi@3210000 {
+			status = "okay";
+			spi@0 {
+				compatible = "nvidia,tegra-spidev";
+				reg = <0x0>;
+				spi-max-frequency = <81000000>;
+			};
+			spi@1 {
+				compatible = "nvidia,tegra-spidev";
+				reg = <0x1>;
+				spi-max-frequency = <81000000>;
+			};
+		};
+
+		spi@3230000 {
+			status = "okay";
+			spi@0 {
+				compatible = "nvidia,tegra-spidev";
+				reg = <0x0>;
+				spi-max-frequency = <81000000>;
+			};
+			spi@1 {
+				compatible = "nvidia,tegra-spidev";
+				reg = <0x1>;
+				spi-max-frequency = <81000000>;
+			};
+		};
+
 		pwm@3280000 {
 			status = "okay";
 		};
-- 
2.17.1


  reply	other threads:[~2024-11-26 13:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-26 13:45 [PATCH 0/3] Add spidev nodes for SPI controllers Vishwaroop A
2024-11-26 13:45 ` Vishwaroop A [this message]
2024-11-26 13:45 ` [PATCH 2/3] dt-bindings: spi: Add DT schema for Tegra SPIDEV controller Vishwaroop A
2024-11-26 13:56   ` Mark Brown
2024-11-27 15:54     ` Jon Hunter
2024-11-27 16:09       ` Mark Brown
2024-11-27 17:24         ` Jon Hunter
2024-11-27 17:31           ` Mark Brown
2025-03-25 10:36             ` Jon Hunter
2025-03-25 12:10               ` Mark Brown
2025-03-25 12:45                 ` Thierry Reding
2025-03-25 13:05                   ` Thierry Reding
2025-03-25 15:55                     ` Mark Brown
2025-03-25 16:38                       ` Thierry Reding
2025-03-25 17:05                         ` Mark Brown
2025-03-26 12:16                           ` Jon Hunter
2025-03-27 15:33                             ` Mark Brown
2025-03-31 12:34                               ` Jon Hunter
2025-03-31 12:44                                 ` Mark Brown
2025-03-31 13:11                                   ` Jon Hunter
2025-03-31 14:09                                     ` Mark Brown
2025-03-25 13:57                   ` Mark Brown
2024-11-26 13:45 ` [PATCH 3/3] spi: spidev: add "tegra-spidev" name string Vishwaroop A
2024-11-26 14:02   ` Krzysztof Kozlowski

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=20241126134529.936451-2-va@nvidia.com \
    --to=va@nvidia.com \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).