From: Thierry Reding <thierry.reding@gmail.com>
To: Alexandre Courbot <acourbot@nvidia.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, gnurou@gmail.com,
linux-kernel@vger.kernel.org,
Jonathan Hunter <jonathanh@nvidia.com>,
Rob Herring <robh+dt@kernel.org>,
linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] dt-bindings: Add documentation for GP10B GPU
Date: Fri, 31 Mar 2017 14:56:07 +0200 [thread overview]
Message-ID: <20170331125607.GA29779@ulmo.ba.sec> (raw)
In-Reply-To: <20170330092644.11890-1-acourbot@nvidia.com>
[-- Attachment #1.1: Type: text/plain, Size: 2514 bytes --]
On Thu, Mar 30, 2017 at 06:26:44PM +0900, Alexandre Courbot wrote:
> GP10B's definition is mostly similar to GK20A's and GM20B's. The only
> noticeable difference is the use of power domains instead of a regulator
> for power supply.
>
> Signed-off-by: Alexandre Courbot <acourbot@nvidia.com>
> ---
> Changes since v1:
> - It's much better when it compiles.
>
> .../devicetree/bindings/gpu/nvidia,gk20a.txt | 25 +++++++++++++++++++++-
> 1 file changed, 24 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/gpu/nvidia,gk20a.txt b/Documentation/devicetree/bindings/gpu/nvidia,gk20a.txt
> index ff3db65e50de..b7e4c7444510 100644
> --- a/Documentation/devicetree/bindings/gpu/nvidia,gk20a.txt
> +++ b/Documentation/devicetree/bindings/gpu/nvidia,gk20a.txt
> @@ -5,6 +5,7 @@ Required properties:
> Currently recognized values:
> - nvidia,gk20a
> - nvidia,gm20b
> + - nvidia,gp10b
> - reg: Physical base address and length of the controller's registers.
> Must contain two entries:
> - first entry for bar0
> @@ -14,7 +15,8 @@ Required properties:
> - interrupt-names: Must include the following entries:
> - stall
> - nonstall
> -- vdd-supply: regulator for supply voltage.
> +- vdd-supply: regulator for supply voltage. Only required for GPUs not using
> + power domains.
> - clocks: Must contain an entry for each entry in clock-names.
> See ../clocks/clock-bindings.txt for details.
> - clock-names: Must include the following entries:
> @@ -27,6 +29,8 @@ is also required:
> See ../reset/reset.txt for details.
> - reset-names: Must include the following entries:
> - gpu
> +- power-domains: GPUs that make use of power domains can define this property
> + instead of vdd-supply. Currently "nvidia,gp10b" makes use of this.
>
> Optional properties:
> - iommus: A reference to the IOMMU. See ../iommu/iommu.txt for details.
> @@ -68,3 +72,22 @@ Example for GM20B:
> iommus = <&mc TEGRA_SWGROUP_GPU>;
> status = "disabled";
> };
> +
> +Example for GP10B:
> +
> + gpu@17000000 {
> + compatible = "nvidia,gp10b";
> + reg = <0x0 0x17000000 0x0 0x1000000>,
> + <0x0 0x18000000 0x0 0x1000000>;
Would it make sense to add a reg-names property to give these meaning? I
know that the binding describes what each entry is, but having the names
specified in a property would make it more immediately obvious.
Just a thought, otherwise looks good to me.
Thierry
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2017-03-31 12:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 9:18 [PATCH 1/2] dt-bindings: Add documentation for GP10B GPU Alexandre Courbot
[not found] ` <20170330091831.18322-1-acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-03-30 9:18 ` [PATCH 2/2] arm64: tegra: Add GPU node for Tegra 186 Alexandre Courbot
2017-03-30 9:26 ` [PATCH v2] dt-bindings: Add documentation for GP10B GPU Alexandre Courbot
2017-03-31 12:56 ` Thierry Reding [this message]
[not found] ` <20170331125607.GA29779-EkSeR96xj6Pcmrwk2tT4+A@public.gmane.org>
2017-04-08 10:20 ` Alexandre Courbot
[not found] ` <20170330092644.11890-1-acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-04-03 15:55 ` Rob Herring
2017-04-04 13:21 ` Thierry Reding
[not found] ` <20170330091831.18322-2-acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-03-30 9:28 ` [PATCH v2] arm64: tegra: Add GPU node for Tegra 186 Alexandre Courbot
[not found] ` <20170330092828.13336-1-acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-04-04 13:22 ` 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=20170331125607.GA29779@ulmo.ba.sec \
--to=thierry.reding@gmail.com \
--cc=acourbot@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=gnurou@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.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).