From: Mikko Perttunen <mperttunen@nvidia.com>
To: thierry.reding@gmail.com, jonathanh@nvidia.com,
robh+dt@kernel.org, mark.rutland@arm.com
Cc: digetx@gmail.com, amerilainen@nvidia.com, dnibade@nvidia.com,
sgurrappadi@nvidia.com, dri-devel@lists.freedesktop.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
Mikko Perttunen <mperttunen@nvidia.com>
Subject: [PATCH v2 4/6] dt-bindings: host1x: Add Tegra186 information
Date: Tue, 5 Sep 2017 11:43:04 +0300 [thread overview]
Message-ID: <20170905084306.19318-5-mperttunen@nvidia.com> (raw)
In-Reply-To: <20170905084306.19318-1-mperttunen@nvidia.com>
Add the Tegra186-specific hypervisor-related register range
properties.
Signed-off-by: Mikko Perttunen <mperttunen@nvidia.com>
---
v2:
- Dropped incorrect note about cells properties.
.../devicetree/bindings/display/tegra/nvidia,tegra20-host1x.txt | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-host1x.txt b/Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-host1x.txt
index 74e1e8add5a1..844e0103fb0d 100644
--- a/Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-host1x.txt
+++ b/Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-host1x.txt
@@ -3,6 +3,10 @@ NVIDIA Tegra host1x
Required properties:
- compatible: "nvidia,tegra<chip>-host1x"
- reg: Physical base address and length of the controller's registers.
+ For pre-Tegra186, one entry describing the whole register area.
+ For Tegra186, one entry for each entry in reg-names:
+ "vm" - VM region assigned to Linux
+ "hypervisor" - Hypervisor region (only if Linux acts as hypervisor)
- interrupts: The interrupt outputs from the controller.
- #address-cells: The number of cells used to represent physical base addresses
in the host1x address space. Should be 1.
--
2.14.1
next prev parent reply other threads:[~2017-09-05 8:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 8:43 [PATCH v2 0/6] Host1x and VIC support for Tegra186 Mikko Perttunen
2017-09-05 8:43 ` [PATCH v2 1/6] arm64: tegra: Add #power-domain-cells for BPMP Mikko Perttunen
2017-10-19 10:49 ` Thierry Reding
2017-09-05 8:43 ` [PATCH v2 2/6] arm64: tegra: Add host1x on Tegra186 Mikko Perttunen
2017-10-19 10:50 ` Thierry Reding
2017-09-05 8:43 ` [PATCH v2 3/6] arm64: tegra: Add VIC " Mikko Perttunen
2017-10-19 10:50 ` Thierry Reding
2017-09-05 8:43 ` Mikko Perttunen [this message]
2017-09-12 21:49 ` [PATCH v2 4/6] dt-bindings: host1x: Add Tegra186 information Rob Herring
2017-10-19 11:39 ` Thierry Reding
2017-09-05 8:43 ` [PATCH v2 5/6] gpu: host1x: Add Tegra186 support Mikko Perttunen
2017-10-19 11:39 ` Thierry Reding
2017-09-05 8:43 ` [PATCH v2 6/6] drm/tegra: Add Tegra186 support for VIC Mikko Perttunen
2017-10-19 11:40 ` Thierry Reding
2017-09-05 11:10 ` [PATCH v2 0/6] Host1x and VIC support for Tegra186 Daniel Vetter
2017-09-05 11:28 ` Mikko Perttunen
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=20170905084306.19318-5-mperttunen@nvidia.com \
--to=mperttunen@nvidia.com \
--cc=amerilainen@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=digetx@gmail.com \
--cc=dnibade@nvidia.com \
--cc=dri-devel@lists.freedesktop.org \
--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 \
--cc=sgurrappadi@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
all inboxes | Powered by JetHome®