From: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: [PATCH 3/3] dt: docs: tegra: Use engineering names in DT compatible property
Date: Tue, 5 Jul 2011 14:29:22 -0600 [thread overview]
Message-ID: <1309897762-23564-4-git-send-email-swarren@nvidia.com> (raw)
In-Reply-To: <1309897762-23564-1-git-send-email-swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Engineering names are more stable than marketing names. Hence, use them
for Device Tree compatible properties instead.
Signed-off-by: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
---
Documentation/devicetree/usage-model | 12 ++++++------
1 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/Documentation/devicetree/usage-model b/Documentation/devicetree/usage-model
index 03a56b3..45e03b8 100644
--- a/Documentation/devicetree/usage-model
+++ b/Documentation/devicetree/usage-model
@@ -240,7 +240,7 @@ About now is a good time to lay out an example. Here is part of the
device tree for the NVIDIA Tegra board.
/{
- compatible = "nvidia,harmony", "nvidia,tegra250";
+ compatible = "nvidia,harmony", "nvidia,tegra20";
#address-cells = <1>;
#size-cells = <1>;
interrupt-parent = <&intc>;
@@ -254,33 +254,33 @@ device tree for the NVIDIA Tegra board.
};
soc {
- compatible = "nvidia,tegra250-soc", "simple-bus";
+ compatible = "nvidia,tegra20-soc", "simple-bus";
#address-cells = <1>;
#size-cells = <1>;
ranges;
intc: interrupt-controller@50041000 {
- compatible = "nvidia,tegra250-gic";
+ compatible = "nvidia,tegra20-gic";
interrupt-controller;
#interrupt-cells = <1>;
reg = <0x50041000 0x1000>, < 0x50040100 0x0100 >;
};
serial@70006300 {
- compatible = "nvidia,tegra250-uart";
+ compatible = "nvidia,tegra20-uart";
reg = <0x70006300 0x100>;
interrupts = <122>;
};
i2s-1: i2s@70002800 {
- compatible = "nvidia,tegra250-i2s";
+ compatible = "nvidia,tegra20-i2s";
reg = <0x70002800 0x100>;
interrupts = <77>;
codec = <&wm8903>;
};
i2c@7000c000 {
- compatible = "nvidia,tegra250-i2c";
+ compatible = "nvidia,tegra20-i2c";
#address-cells = <1>;
#size-cells = <1>;
reg = <0x7000c000 0x100>;
--
1.7.0.4
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren@nvidia.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-tegra@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
Stephen Warren <swarren@nvidia.com>
Subject: [PATCH 3/3] dt: docs: tegra: Use engineering names in DT compatible property
Date: Tue, 5 Jul 2011 14:29:22 -0600 [thread overview]
Message-ID: <1309897762-23564-4-git-send-email-swarren@nvidia.com> (raw)
In-Reply-To: <1309897762-23564-1-git-send-email-swarren@nvidia.com>
Engineering names are more stable than marketing names. Hence, use them
for Device Tree compatible properties instead.
Signed-off-by: Stephen Warren <swarren@nvidia.com>
---
Documentation/devicetree/usage-model | 12 ++++++------
1 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/Documentation/devicetree/usage-model b/Documentation/devicetree/usage-model
index 03a56b3..45e03b8 100644
--- a/Documentation/devicetree/usage-model
+++ b/Documentation/devicetree/usage-model
@@ -240,7 +240,7 @@ About now is a good time to lay out an example. Here is part of the
device tree for the NVIDIA Tegra board.
/{
- compatible = "nvidia,harmony", "nvidia,tegra250";
+ compatible = "nvidia,harmony", "nvidia,tegra20";
#address-cells = <1>;
#size-cells = <1>;
interrupt-parent = <&intc>;
@@ -254,33 +254,33 @@ device tree for the NVIDIA Tegra board.
};
soc {
- compatible = "nvidia,tegra250-soc", "simple-bus";
+ compatible = "nvidia,tegra20-soc", "simple-bus";
#address-cells = <1>;
#size-cells = <1>;
ranges;
intc: interrupt-controller@50041000 {
- compatible = "nvidia,tegra250-gic";
+ compatible = "nvidia,tegra20-gic";
interrupt-controller;
#interrupt-cells = <1>;
reg = <0x50041000 0x1000>, < 0x50040100 0x0100 >;
};
serial@70006300 {
- compatible = "nvidia,tegra250-uart";
+ compatible = "nvidia,tegra20-uart";
reg = <0x70006300 0x100>;
interrupts = <122>;
};
i2s-1: i2s@70002800 {
- compatible = "nvidia,tegra250-i2s";
+ compatible = "nvidia,tegra20-i2s";
reg = <0x70002800 0x100>;
interrupts = <77>;
codec = <&wm8903>;
};
i2c@7000c000 {
- compatible = "nvidia,tegra250-i2c";
+ compatible = "nvidia,tegra20-i2c";
#address-cells = <1>;
#size-cells = <1>;
reg = <0x7000c000 0x100>;
--
1.7.0.4
WARNING: multiple messages have this Message-ID (diff)
From: swarren@nvidia.com (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] dt: docs: tegra: Use engineering names in DT compatible property
Date: Tue, 5 Jul 2011 14:29:22 -0600 [thread overview]
Message-ID: <1309897762-23564-4-git-send-email-swarren@nvidia.com> (raw)
In-Reply-To: <1309897762-23564-1-git-send-email-swarren@nvidia.com>
Engineering names are more stable than marketing names. Hence, use them
for Device Tree compatible properties instead.
Signed-off-by: Stephen Warren <swarren@nvidia.com>
---
Documentation/devicetree/usage-model | 12 ++++++------
1 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/Documentation/devicetree/usage-model b/Documentation/devicetree/usage-model
index 03a56b3..45e03b8 100644
--- a/Documentation/devicetree/usage-model
+++ b/Documentation/devicetree/usage-model
@@ -240,7 +240,7 @@ About now is a good time to lay out an example. Here is part of the
device tree for the NVIDIA Tegra board.
/{
- compatible = "nvidia,harmony", "nvidia,tegra250";
+ compatible = "nvidia,harmony", "nvidia,tegra20";
#address-cells = <1>;
#size-cells = <1>;
interrupt-parent = <&intc>;
@@ -254,33 +254,33 @@ device tree for the NVIDIA Tegra board.
};
soc {
- compatible = "nvidia,tegra250-soc", "simple-bus";
+ compatible = "nvidia,tegra20-soc", "simple-bus";
#address-cells = <1>;
#size-cells = <1>;
ranges;
intc: interrupt-controller at 50041000 {
- compatible = "nvidia,tegra250-gic";
+ compatible = "nvidia,tegra20-gic";
interrupt-controller;
#interrupt-cells = <1>;
reg = <0x50041000 0x1000>, < 0x50040100 0x0100 >;
};
serial at 70006300 {
- compatible = "nvidia,tegra250-uart";
+ compatible = "nvidia,tegra20-uart";
reg = <0x70006300 0x100>;
interrupts = <122>;
};
i2s-1: i2s at 70002800 {
- compatible = "nvidia,tegra250-i2s";
+ compatible = "nvidia,tegra20-i2s";
reg = <0x70002800 0x100>;
interrupts = <77>;
codec = <&wm8903>;
};
i2c at 7000c000 {
- compatible = "nvidia,tegra250-i2c";
+ compatible = "nvidia,tegra20-i2c";
#address-cells = <1>;
#size-cells = <1>;
reg = <0x7000c000 0x100>;
--
1.7.0.4
next prev parent reply other threads:[~2011-07-05 20:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 20:29 [PATCH 0/3] tegra: Use engineering names in DT compatible properties Stephen Warren
2011-07-05 20:29 ` Stephen Warren
2011-07-05 20:29 ` Stephen Warren
2011-07-05 20:29 ` [PATCH 1/3] mmc/tegra: Use engineering names in DT compatible property Stephen Warren
2011-07-05 20:29 ` Stephen Warren
[not found] ` <1309897762-23564-1-git-send-email-swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2011-07-05 20:29 ` [PATCH 2/3] ARM: tegra: " Stephen Warren
2011-07-05 20:29 ` Stephen Warren
2011-07-05 20:29 ` Stephen Warren
2011-07-05 20:29 ` Stephen Warren [this message]
2011-07-05 20:29 ` [PATCH 3/3] dt: docs: " Stephen Warren
2011-07-05 20:29 ` Stephen Warren
2011-07-06 5:55 ` [PATCH 0/3] tegra: Use engineering names in DT compatible properties Grant Likely
2011-07-06 5:55 ` Grant Likely
2011-07-06 5:55 ` Grant Likely
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=1309897762-23564-4-git-send-email-swarren@nvidia.com \
--to=swarren-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.