From: Alexandre Courbot <acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Alexandre Courbot
<gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>,
Thierry Reding
<thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Linux Kernel Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH v2 3/5] dt-bindings: Add documentation for GM20B GPU
Date: Tue, 22 Mar 2016 13:00:53 +0900 [thread overview]
Message-ID: <56F0C375.1030907@nvidia.com> (raw)
In-Reply-To: <CAL_Jsq+SEOC1s_j8u3hMyDj5i9ROyAAN_-qmbsLrNvR3v2cXwA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 03/22/2016 10:41 AM, Rob Herring wrote:
> On Sun, Mar 20, 2016 at 1:55 AM, Alexandre Courbot <gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>> On Sat, Mar 19, 2016 at 5:47 AM, Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> wrote:
>>> On Tue, Mar 15, 2016 at 11:58:42AM +0900, Alexandre Courbot wrote:
>>>> GM20B's definition is mostly similar to GK20A's, but requires an
>>>> additional clock.
>
> [...]
>
>>>> gpu@0,57000000 {
>>>> compatible = "nvidia,gk20a";
>>>> @@ -45,3 +49,22 @@ Example:
>>>> iommus = <&mc TEGRA_SWGROUP_GPU>;
>>>> status = "disabled";
>>>> };
>>>> +
>>>> +Example for GM20B:
>>>> +
>>>> + gpu@0,57000000 {
>>>
>>> Drop the comma and leading zero.
>>
>> Even though this is how it appears in the actual DT?
>
> Yes, those will need to get fixed, too.
Sorry, I just want to confirm that I understand why this needs to be
fixed. The parent node has #address-cells = <2>, and the practice of
specifying two cells in the node name is consistent with what I see in
http://www.devicetree.org/Device_Tree_Usage.
However in the device tree usage example one can interpret the two cells
as being two different components of the address, whereas in our case we
are using two cells because the address is 64-bit - hence we should
specify it in the name as a single entity. Is this correct?
Thanks,
Alex.
next prev parent reply other threads:[~2016-03-22 4:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 2:58 [PATCH v2 0/5] arm64: tegra: fix DT definitions for GM20B GPU Alexandre Courbot
[not found] ` <1458010724-10945-1-git-send-email-acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-03-15 2:58 ` [PATCH v2 1/5] dt-bindings: gk20a: Fix typo in compatible name Alexandre Courbot
[not found] ` <1458010724-10945-2-git-send-email-acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-03-18 20:31 ` Rob Herring
2016-03-20 6:55 ` Alexandre Courbot
2016-03-15 2:58 ` [PATCH v2 3/5] dt-bindings: Add documentation for GM20B GPU Alexandre Courbot
[not found] ` <1458010724-10945-4-git-send-email-acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-03-18 20:47 ` Rob Herring
2016-03-20 6:55 ` Alexandre Courbot
[not found] ` <CAAVeFuKQvjb20aEh9_MBnrzEUjKoVc8yQu3a4Ego6Qaqe70M6A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-03-22 1:41 ` Rob Herring
[not found] ` <CAL_Jsq+SEOC1s_j8u3hMyDj5i9ROyAAN_-qmbsLrNvR3v2cXwA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-03-22 4:00 ` Alexandre Courbot [this message]
[not found] ` <56F0C375.1030907-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-03-22 12:44 ` Rob Herring
2016-03-15 2:58 ` [PATCH v2 5/5] arm64: tegra210: Add IOMMU node to GM20B Alexandre Courbot
2016-03-15 2:58 ` [PATCH v2 2/5] dt-bindings: gk20a: Document iommus property Alexandre Courbot
2016-03-18 20:41 ` Rob Herring
2016-03-15 2:58 ` [PATCH v2 4/5] arm64: tegra210: Add reference clock to GM20B Alexandre Courbot
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=56F0C375.1030907@nvidia.com \
--to=acourbot-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=gnurou-Re5JQEeQqe8AvxtiuMwx3w@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 \
--cc=robh-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;
as well as URLs for NNTP newsgroup(s).