lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1309897762-23564-4-git-send-email-swarren@nvidia.com>
Date:	Tue,  5 Jul 2011 14:29:22 -0600
From:	Stephen Warren <swarren@...dia.com>
To:	Grant Likely <grant.likely@...retlab.ca>
Cc:	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	linux-tegra@...r.kernel.org, devicetree-discuss@...ts.ozlabs.org,
	Stephen Warren <swarren@...dia.com>
Subject: [PATCH 3/3] dt: docs: tegra: Use engineering names in DT compatible property

Engineering names are more stable than marketing names. Hence, use them
for Device Tree compatible properties instead.

Signed-off-by: Stephen Warren <swarren@...dia.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@...41000 {
-			compatible = "nvidia,tegra250-gic";
+			compatible = "nvidia,tegra20-gic";
 			interrupt-controller;
 			#interrupt-cells = <1>;
 			reg = <0x50041000 0x1000>, < 0x50040100 0x0100 >;
 		};
 
 		serial@...06300 {
-			compatible = "nvidia,tegra250-uart";
+			compatible = "nvidia,tegra20-uart";
 			reg = <0x70006300 0x100>;
 			interrupts = <122>;
 		};
 
 		i2s-1: i2s@...02800 {
-			compatible = "nvidia,tegra250-i2s";
+			compatible = "nvidia,tegra20-i2s";
 			reg = <0x70002800 0x100>;
 			interrupts = <77>;
 			codec = <&wm8903>;
 		};
 
 		i2c@...0c000 {
-			compatible = "nvidia,tegra250-i2c";
+			compatible = "nvidia,tegra20-i2c";
 			#address-cells = <1>;
 			#size-cells = <1>;
 			reg = <0x7000c000 0x100>;
-- 
1.7.0.4

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ