summaryrefslogtreecommitdiffstats
path: root/arch/arm64/boot/dts/nvidia/tegra210-p2180.dtsi
diff options
context:
space:
mode:
authorThierry Reding <treding@nvidia.com>2016-04-11 15:35:06 +0200
committerThierry Reding <treding@nvidia.com>2016-04-11 15:38:10 +0200
commitbe70771d4cabe0763e7dacd55400abd38910d634 (patch)
treea6dfd6097ff55af15884ea283d1223fea52406c2 /arch/arm64/boot/dts/nvidia/tegra210-p2180.dtsi
parentLinux 4.6-rc1 (diff)
downloadlinux-be70771d4cabe0763e7dacd55400abd38910d634.tar.xz
linux-be70771d4cabe0763e7dacd55400abd38910d634.zip
arm64: tegra: Remove 0, prefix from unit-addresses
When Tegra124 support was first merged the unit-addresses of all devices were listed with a "0," prefix to encode the reg property's second cell. It turns out that this notation is not correct, and the "," separator is only used to separate fields in the unit address (such as the device and function number in PCI devices), not individual cells for addresses with more than one cell. Signed-off-by: Thierry Reding <treding@nvidia.com>
Diffstat (limited to 'arch/arm64/boot/dts/nvidia/tegra210-p2180.dtsi')
-rw-r--r--arch/arm64/boot/dts/nvidia/tegra210-p2180.dtsi8
1 files changed, 4 insertions, 4 deletions
diff --git a/arch/arm64/boot/dts/nvidia/tegra210-p2180.dtsi b/arch/arm64/boot/dts/nvidia/tegra210-p2180.dtsi
index 2b7f88950d1e..316c92c03821 100644
--- a/arch/arm64/boot/dts/nvidia/tegra210-p2180.dtsi
+++ b/arch/arm64/boot/dts/nvidia/tegra210-p2180.dtsi
@@ -5,7 +5,7 @@
compatible = "nvidia,p2180", "nvidia,tegra210";
aliases {
- rtc1 = "/rtc@0,7000e000";
+ rtc1 = "/rtc@7000e000";
serial0 = &uarta;
};
@@ -15,16 +15,16 @@
};
/* debug port */
- serial@0,70006000 {
+ serial@70006000 {
status = "okay";
};
- pmc@0,7000e400 {
+ pmc@7000e400 {
nvidia,invert-interrupt;
};
/* eMMC */
- sdhci@0,700b0600 {
+ sdhci@700b0600 {
status = "okay";
bus-width = <8>;
non-removable;