From: Jon Hunter <jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>,
Thierry Reding
<thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Russell King <linux-I+IVW8TIWO2tmTQ+vhA3Yw@public.gmane.org>,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH V2 4/5] dt-bindings: tegra: Update compatible strings for Tegra flowctrl
Date: Wed, 22 Mar 2017 18:13:27 +0000 [thread overview]
Message-ID: <58983614-8f75-b498-e544-5121a16d5d19@nvidia.com> (raw)
In-Reply-To: <b85e7f4e-ba63-8374-b10d-3f9f04252a69-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
On 22/03/17 17:26, Stephen Warren wrote:
> On 03/22/2017 11:00 AM, Jon Hunter wrote:
>> Update the compatible strings for Tegra Flow Control driver to match
>> the device-tree source files for Tegra.
>
>> +++
>> b/Documentation/devicetree/bindings/arm/tegra/nvidia,tegra20-flowctrl.txt
>
>> + - "nvidia,tegra124-flowctrl": for Tegra124 and Tegra132
>
> I think that should be:
>
> + - "nvidia,tegra124-flowctrl": for Tegra124
> + - "nvidia,tegra132-flowctrl", "nvidia,tegra124-flowctrl": for \
> Tegra132
This is based upon the current tegra132.dtsi file which just has ...
flow-controller@60007000 {
compatible = "nvidia,tegra124-flowctrl";
...
So I can fix-it up if that is what we want/should have. I have a feeling
there are a few other cases like this.
Cheers
Jon
--
nvpublic
next prev parent reply other threads:[~2017-03-22 18:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 17:00 [PATCH V2 0/5] soc/tegra: Enable flowctrl support for Tegra132/210 Jon Hunter
[not found] ` <1490202056-13040-1-git-send-email-jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-03-22 17:00 ` [PATCH V2 1/5] ARM: tegra: Remove unnecessary inclusion of flowctrl header Jon Hunter
2017-03-22 17:00 ` [PATCH V2 2/5] soc/tegra: Move Tegra flowctrl driver Jon Hunter
2017-03-22 17:00 ` [PATCH V2 3/5] soc/tegra: flowctrl: Add basic platform driver Jon Hunter
2017-03-22 17:00 ` [PATCH V2 4/5] dt-bindings: tegra: Update compatible strings for Tegra flowctrl Jon Hunter
2017-03-22 17:26 ` Stephen Warren
[not found] ` <b85e7f4e-ba63-8374-b10d-3f9f04252a69-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2017-03-22 18:13 ` Jon Hunter [this message]
[not found] ` <58983614-8f75-b498-e544-5121a16d5d19-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-03-22 19:00 ` Stephen Warren
2017-03-22 17:00 ` [PATCH V2 5/5] soc/tegra: Add initial flowctrl support for Tegra132/210 Jon Hunter
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=58983614-8f75-b498-e544-5121a16d5d19@nvidia.com \
--to=jonathanh-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-I+IVW8TIWO2tmTQ+vhA3Yw@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org \
--cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox