All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>,
	Rob Herring <robh+dt@kernel.org>
Cc: linux-tegra@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: [PATCH 05/11] misc: sram: Add compatible string for Tegra234 SYSRAM
Date: Fri, 12 Nov 2021 13:35:36 +0100	[thread overview]
Message-ID: <20211112123542.3680629-6-thierry.reding@gmail.com> (raw)
In-Reply-To: <20211112123542.3680629-1-thierry.reding@gmail.com>

From: Mikko Perttunen <mperttunen@nvidia.com>

We want to use the same behavior as on Tegra186 and Tegra194, so add
this the compatible string for Tegra234 SYSRAM to the list.

Signed-off-by: Mikko Perttunen <mperttunen@nvidia.com>
Signed-off-by: Thierry Reding <treding@nvidia.com>
---
 drivers/misc/sram.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/misc/sram.c b/drivers/misc/sram.c
index 4c26b19f5154..f0e7f02605eb 100644
--- a/drivers/misc/sram.c
+++ b/drivers/misc/sram.c
@@ -371,6 +371,7 @@ static const struct of_device_id sram_dt_ids[] = {
 	{ .compatible = "atmel,sama5d2-securam", .data = &atmel_securam_config },
 	{ .compatible = "nvidia,tegra186-sysram", .data = &tegra_sysram_config },
 	{ .compatible = "nvidia,tegra194-sysram", .data = &tegra_sysram_config },
+	{ .compatible = "nvidia,tegra234-sysram", .data = &tegra_sysram_config },
 	{}
 };
 
-- 
2.33.1


WARNING: multiple messages have this Message-ID (diff)
From: Thierry Reding <thierry.reding@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>,
	Rob Herring <robh+dt@kernel.org>
Cc: linux-tegra@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: [PATCH 05/11] misc: sram: Add compatible string for Tegra234 SYSRAM
Date: Fri, 12 Nov 2021 13:35:36 +0100	[thread overview]
Message-ID: <20211112123542.3680629-6-thierry.reding@gmail.com> (raw)
In-Reply-To: <20211112123542.3680629-1-thierry.reding@gmail.com>

From: Mikko Perttunen <mperttunen@nvidia.com>

We want to use the same behavior as on Tegra186 and Tegra194, so add
this the compatible string for Tegra234 SYSRAM to the list.

Signed-off-by: Mikko Perttunen <mperttunen@nvidia.com>
Signed-off-by: Thierry Reding <treding@nvidia.com>
---
 drivers/misc/sram.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/misc/sram.c b/drivers/misc/sram.c
index 4c26b19f5154..f0e7f02605eb 100644
--- a/drivers/misc/sram.c
+++ b/drivers/misc/sram.c
@@ -371,6 +371,7 @@ static const struct of_device_id sram_dt_ids[] = {
 	{ .compatible = "atmel,sama5d2-securam", .data = &atmel_securam_config },
 	{ .compatible = "nvidia,tegra186-sysram", .data = &tegra_sysram_config },
 	{ .compatible = "nvidia,tegra194-sysram", .data = &tegra_sysram_config },
+	{ .compatible = "nvidia,tegra234-sysram", .data = &tegra_sysram_config },
 	{}
 };
 
-- 
2.33.1


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2021-11-12 12:36 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-12 12:35 [PATCH 00/11] arm64: tegra: Add NVIDIA Jetson AGX Orin support Thierry Reding
2021-11-12 12:35 ` Thierry Reding
2021-11-12 12:35 ` [PATCH 01/11] dt-bindings: tegra: Describe recent developer kits consistently Thierry Reding
2021-11-12 12:35   ` Thierry Reding
2021-11-29 20:54   ` Rob Herring
2021-11-29 20:54     ` Rob Herring
2021-11-12 12:35 ` [PATCH 02/11] dt-bindings: tegra: Document Jetson AGX Orin (and devkit) Thierry Reding
2021-11-12 12:35   ` Thierry Reding
2021-11-29 20:55   ` Rob Herring
2021-11-29 20:55     ` Rob Herring
2021-11-12 12:35 ` [PATCH 03/11] dt-bindings: Update headers for Tegra234 Thierry Reding
2021-11-12 12:35   ` Thierry Reding
2021-11-29 20:59   ` Rob Herring
2021-11-29 20:59     ` Rob Herring
2021-11-12 12:35 ` [PATCH 04/11] dt-bindings: sram: Document NVIDIA Tegra SYSRAM Thierry Reding
2021-11-12 12:35   ` Thierry Reding
2021-11-29 20:59   ` Rob Herring
2021-11-29 20:59     ` Rob Herring
2021-11-12 12:35 ` Thierry Reding [this message]
2021-11-12 12:35   ` [PATCH 05/11] misc: sram: Add compatible string for Tegra234 SYSRAM Thierry Reding
2021-12-07 15:52   ` Thierry Reding
2021-12-07 15:52     ` Thierry Reding
2021-12-07 17:45     ` Greg Kroah-Hartman
2021-12-07 17:45       ` Greg Kroah-Hartman
2021-11-12 12:35 ` [PATCH 06/11] arm64: tegra: Fixup SYSRAM references Thierry Reding
2021-11-12 12:35   ` Thierry Reding
2021-11-12 12:35 ` [PATCH 07/11] arm64: tegra: Add clock for Tegra234 RTC Thierry Reding
2021-11-12 12:35   ` Thierry Reding
2021-11-12 12:35 ` [PATCH 08/11] arm64: tegra: Update Tegra234 BPMP channel addresses Thierry Reding
2021-11-12 12:35   ` Thierry Reding
2021-11-12 12:35 ` [PATCH 09/11] arm64: tegra: Fill in properties for Tegra234 eMMC Thierry Reding
2021-11-12 12:35   ` Thierry Reding
2021-11-12 12:35 ` [PATCH 10/11] arm64: tegra: Add Tegra234 TCU device Thierry Reding
2021-11-12 12:35   ` Thierry Reding
2021-11-12 12:35 ` [PATCH 11/11] arm64: tegra: Add NVIDIA Jetson AGX Orin Developer Kit support Thierry Reding
2021-11-12 12:35   ` 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=20211112123542.3680629-6-thierry.reding@gmail.com \
    --to=thierry.reding@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.