From: Jon Hunter <jonathanh@nvidia.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Terje Bergstrom <tbergstrom@nvidia.com>,
Debarshi Dutta <ddutta@nvidia.com>, <linux-tegra@vger.kernel.org>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 1/2] dt-bindings: Add documentation for GV11B GPU
Date: Fri, 17 Jul 2020 09:40:32 +0100 [thread overview]
Message-ID: <5b8d0aaa-41c5-e577-df4c-737660be46f4@nvidia.com> (raw)
In-Reply-To: <20200717083609.557205-1-thierry.reding@gmail.com>
On 17/07/2020 09:36, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> The GV11B's device tree bindings are the same as for GP10B, though the
> GPU is not completely compatible, so all that is needed is a different
> compatible string.
>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
> Changes in v3:
> - document the "fuse" clock which needs to be enabled during the GPU
> initialization
>
> .../devicetree/bindings/gpu/nvidia,gk20a.txt | 25 +++++++++++++++++++
> 1 file changed, 25 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/gpu/nvidia,gk20a.txt b/Documentation/devicetree/bindings/gpu/nvidia,gk20a.txt
> index f32bbba4d3bc..662a3c8a7d29 100644
> --- a/Documentation/devicetree/bindings/gpu/nvidia,gk20a.txt
> +++ b/Documentation/devicetree/bindings/gpu/nvidia,gk20a.txt
> @@ -6,6 +6,7 @@ Required properties:
> - nvidia,gk20a
> - nvidia,gm20b
> - nvidia,gp10b
> + - nvidia,gv11b
> - reg: Physical base address and length of the controller's registers.
> Must contain two entries:
> - first entry for bar0
> @@ -25,6 +26,9 @@ Required properties:
> If the compatible string is "nvidia,gm20b", then the following clock
> is also required:
> - ref
> +If the compatible string is "nvidia,gv11b", then the following clock is also
> +required:
> + - fuse
> - resets: Must contain an entry for each entry in reset-names.
> See ../reset/reset.txt for details.
> - reset-names: Must include the following entries:
> @@ -88,3 +92,24 @@ Example for GP10B:
> power-domains = <&bpmp TEGRA186_POWER_DOMAIN_GPU>;
> iommus = <&smmu TEGRA186_SID_GPU>;
> };
> +
> +Example for GV11B:
> +
> + gpu@17000000 {
> + compatible = "nvidia,gv11b";
> + reg = <0x17000000 0x10000000>,
> + <0x18000000 0x10000000>;
> + interrupts = <GIC_SPI 70 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 71 IRQ_TYPE_LEVEL_HIGH>;
> + interrupt-names = "stall", "nonstall";
> + clocks = <&bpmp TEGRA194_CLK_GPCCLK>,
> + <&bpmp TEGRA194_CLK_GPU_PWR>,
> + <&bpmp TEGRA194_CLK_FUSE>;
> + clock-names = "gpu", "pwr", "fuse";
> + resets = <&bpmp TEGRA194_RESET_GPU>;
> + reset-names = "gpu";
> + dma-coherent;
> +
> + power-domains = <&bpmp TEGRA194_POWER_DOMAIN_GPU>;
> + iommus = <&smmu TEGRA194_SID_GPU>;
> + };
>
Reviewed-by: Jon Hunter <jonathanh@nvidia.com>
Cheers
Jon
--
nvpublic
prev parent reply other threads:[~2020-07-17 8:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 8:36 [PATCH v3 1/2] dt-bindings: Add documentation for GV11B GPU Thierry Reding
2020-07-17 8:36 ` [PATCH v3 2/2] arm64: tegra: Add the GPU on Tegra194 Thierry Reding
2020-07-17 8:40 ` Jon Hunter
2020-07-17 8:40 ` Jon Hunter [this message]
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=5b8d0aaa-41c5-e577-df4c-737660be46f4@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=ddutta@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=tbergstrom@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).