From: Jon Hunter <jonathanh@nvidia.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Stephen Warren <swarren@nvidia.com>,
Russell King <linux@armlinux.org.uk>,
Jon Hunter <jonathanh@nvidia.com>,
Rob Herring <robh+dt@kernel.org>,
linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3 5/6] arm64: tegra: Update the Tegra132 flowctrl compatible string
Date: Tue, 28 Mar 2017 13:42:57 +0100 [thread overview]
Message-ID: <1490704978-22906-6-git-send-email-jonathanh@nvidia.com> (raw)
In-Reply-To: <1490704978-22906-1-git-send-email-jonathanh@nvidia.com>
Update the Tegra132 flowctrl compatible string to include
"nvidia,tegra132-flowctrl" so it is aligned with the flowctrl binding
documentation.
Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
---
arch/arm64/boot/dts/nvidia/tegra132.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/boot/dts/nvidia/tegra132.dtsi b/arch/arm64/boot/dts/nvidia/tegra132.dtsi
index 3f3a46a4bd01..2b17936ac5be 100644
--- a/arch/arm64/boot/dts/nvidia/tegra132.dtsi
+++ b/arch/arm64/boot/dts/nvidia/tegra132.dtsi
@@ -224,7 +224,7 @@
};
flow-controller@60007000 {
- compatible = "nvidia,tegra124-flowctrl";
+ compatible = "nvidia,tegra132-flowctrl", "nvidia,tegra124-flowctrl";
reg = <0x0 0x60007000 0x0 0x1000>;
};
--
2.7.4
next prev parent reply other threads:[~2017-03-28 12:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 12:42 [PATCH V3 0/6] soc/tegra: Enable flowctrl support for Tegra132/210 Jon Hunter
[not found] ` <1490704978-22906-1-git-send-email-jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-03-28 12:42 ` [PATCH V3 1/6] ARM: tegra: Remove unnecessary inclusion of flowctrl header Jon Hunter
[not found] ` <1490704978-22906-2-git-send-email-jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-04-04 13:41 ` Thierry Reding
2017-03-28 12:42 ` [PATCH V3 3/6] soc/tegra: flowctrl: Add basic platform driver Jon Hunter
[not found] ` <1490704978-22906-4-git-send-email-jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-04-04 14:01 ` Thierry Reding
2017-03-28 12:42 ` [PATCH V3 2/6] soc/tegra: Move Tegra flowctrl driver Jon Hunter
[not found] ` <1490704978-22906-3-git-send-email-jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-04-04 14:01 ` Thierry Reding
2017-03-28 12:42 ` [PATCH V3 4/6] dt-bindings: tegra: Update compatible strings for Tegra flowctrl Jon Hunter
[not found] ` <1490704978-22906-5-git-send-email-jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-04-03 14:29 ` Rob Herring
2017-04-04 14:01 ` Thierry Reding
2017-03-28 12:42 ` Jon Hunter [this message]
[not found] ` <1490704978-22906-6-git-send-email-jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-04-04 14:01 ` [PATCH V3 5/6] arm64: tegra: Update the Tegra132 flowctrl compatible string Thierry Reding
2017-03-28 12:42 ` [PATCH V3 6/6] soc/tegra: Add initial flowctrl support for Tegra132/210 Jon Hunter
[not found] ` <1490704978-22906-7-git-send-email-jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-04-04 14:02 ` 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=1490704978-22906-6-git-send-email-jonathanh@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=swarren@nvidia.com \
--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).