From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Hiroshi Doyu <hdoyu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH 03/23] ARM: dt: tegra30: iommu: Add "nvidia,memory-clients"
Date: Mon, 01 Jul 2013 17:07:46 -0600 [thread overview]
Message-ID: <51D20BC2.4090302@wwwdotorg.org> (raw)
In-Reply-To: <20130626101816.GE27083@manwe>
On 06/26/2013 04:18 AM, Thierry Reding wrote:
> On Wed, Jun 26, 2013 at 12:28:06PM +0300, Hiroshi Doyu wrote:
> [...]
>> diff --git
>> a/Documentation/devicetree/bindings/iommu/nvidia,tegra30-smmu.txt
>> b/Documentation/devicetree/bindings/iommu/nvidia,tegra30-smmu.txt
>
>>
[...]
>> @@ -23,3 +24,13 @@ Example: nvidia,swgroups = <0x00000000
>> 0x000779ff>; nvidia,ahb = <&ahb>; }; + + host1x { + compatible =
>> "nvidia,tegra30-host1x", "simple-bus"; + nvidia,memory-clients =
>> <SWGID_HC>;
>
> And this could use the SWGID(HC) to match up with how GPIOs are
> referenced in the DTS files.
I only made TEGRA_GPIO(bank, id) a macro because there was a regular
bank/id structure to the GPIO numbering. I haven't read these patches
yet, but I assume SWGIDs are just a flat numbering space with
arbitrarily assigned number in HW, so there's no much point saying
SWGID(X) rather than SWGID_X.
WARNING: multiple messages have this Message-ID (diff)
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 03/23] ARM: dt: tegra30: iommu: Add "nvidia, memory-clients"
Date: Mon, 01 Jul 2013 17:07:46 -0600 [thread overview]
Message-ID: <51D20BC2.4090302@wwwdotorg.org> (raw)
In-Reply-To: <20130626101816.GE27083@manwe>
On 06/26/2013 04:18 AM, Thierry Reding wrote:
> On Wed, Jun 26, 2013 at 12:28:06PM +0300, Hiroshi Doyu wrote:
> [...]
>> diff --git
>> a/Documentation/devicetree/bindings/iommu/nvidia,tegra30-smmu.txt
>> b/Documentation/devicetree/bindings/iommu/nvidia,tegra30-smmu.txt
>
>>
[...]
>> @@ -23,3 +24,13 @@ Example: nvidia,swgroups = <0x00000000
>> 0x000779ff>; nvidia,ahb = <&ahb>; }; + + host1x { + compatible =
>> "nvidia,tegra30-host1x", "simple-bus"; + nvidia,memory-clients =
>> <SWGID_HC>;
>
> And this could use the SWGID(HC) to match up with how GPIOs are
> referenced in the DTS files.
I only made TEGRA_GPIO(bank, id) a macro because there was a regular
bank/id structure to the GPIO numbering. I haven't read these patches
yet, but I assume SWGIDs are just a flat numbering space with
arbitrarily assigned number in HW, so there's no much point saying
SWGID(X) rather than SWGID_X.
next prev parent reply other threads:[~2013-07-01 23:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-26 9:28 [PATCH 03/23] ARM: dt: tegra30: iommu: Add "nvidia,memory-clients" Hiroshi Doyu
2013-06-26 9:28 ` Hiroshi Doyu
[not found] ` <1372238906-9346-4-git-send-email-hdoyu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-06-26 10:10 ` Thierry Reding
2013-06-26 10:10 ` Thierry Reding
2013-06-26 10:33 ` Hiroshi Doyu
2013-06-26 10:33 ` Hiroshi Doyu
[not found] ` <20130626.133314.1520719774895092173.hdoyu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-06-26 11:04 ` Joseph Lo
2013-06-26 11:04 ` Joseph Lo
[not found] ` <1372244646.2986.17.camel-yx3yKKdKkHfc7b1ADBJPm0n48jw8i0AO@public.gmane.org>
2013-07-01 8:18 ` Hiroshi Doyu
2013-07-01 8:18 ` Hiroshi Doyu
2013-06-26 10:18 ` Thierry Reding
2013-06-26 10:18 ` Thierry Reding
2013-06-26 10:33 ` Thierry Reding
2013-06-26 10:33 ` Thierry Reding
2013-06-26 11:02 ` Hiroshi Doyu
2013-06-26 11:02 ` Hiroshi Doyu
2013-07-01 23:07 ` Stephen Warren [this message]
2013-07-01 23:07 ` [PATCH 03/23] ARM: dt: tegra30: iommu: Add "nvidia, memory-clients" Stephen Warren
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=51D20BC2.4090302@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=hdoyu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.