From: Jordan Crouse <jcrouse@codeaurora.org>
To: linux-arm-msm@vger.kernel.org
Cc: John Stultz <john.stultz@linaro.org>, Sean Paul <sean@poorly.run>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, Rob Herring <robh+dt@kernel.org>,
Rob Clark <robdclark@gmail.com>, David Airlie <airlied@linux.ie>,
Mark Rutland <mark.rutland@arm.com>,
freedreno@lists.freedesktop.org, Daniel Vetter <daniel@ffwll.ch>
Subject: [PATCH v1 2/4] dt-bindings: display: msm: Add required dma-range property
Date: Wed, 19 Feb 2020 14:32:56 -0700 [thread overview]
Message-ID: <1582147978-31475-3-git-send-email-jcrouse@codeaurora.org> (raw)
In-Reply-To: <1582147978-31475-1-git-send-email-jcrouse@codeaurora.org>
The GMU node now requires a specific dma-range property so that the driver
can use the DMA API to do the few memory allocations required by the GMU.
This sets the IOMMU iova allocadtor to match the 'uncached' part of the
GMU virtual address space.
Signed-off-by: Jordan Crouse <jcrouse@codeaurora.org>
---
Documentation/devicetree/bindings/display/msm/gmu.yaml | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/Documentation/devicetree/bindings/display/msm/gmu.yaml b/Documentation/devicetree/bindings/display/msm/gmu.yaml
index 776ff92..6952d5a 100644
--- a/Documentation/devicetree/bindings/display/msm/gmu.yaml
+++ b/Documentation/devicetree/bindings/display/msm/gmu.yaml
@@ -83,6 +83,13 @@ properties:
Phandle to the OPP table for the available GMU frequencies. Refer to
../../opp/opp.txt for more information.
+ dma-ranges:
+ $ref: /schemas/types.yaml#/definitions/uint32-array
+ description:
+ Describe the dma-address range for the device. This should always
+ describe the range between 0x60000000 and 0x80000000 which represents
+ the uncached region of the GMU address space.
+
required:
- compatible
- reg
@@ -95,6 +102,7 @@ required:
- power-domain-names
- iommus
- operating-points-v2
+ - dma-ranges
examples:
- |
@@ -127,4 +135,6 @@ examples:
iommus = <&adreno_smmu 5>;
operating-points-v2 = <&gmu_opp_table>;
+
+ dma-ranges = <0 0x60000000 0 0x60000000 0 0x80000000>;
};
--
2.7.4
next prev parent reply other threads:[~2020-02-19 21:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 21:32 [PATCH v1 0/4] msm/gpu/a6xx: use the DMA-API for GMU memory allocations Jordan Crouse
2020-02-19 21:32 ` [PATCH v1 1/4] dt-bindings: display: msm: Convert GMU bindings to YAML Jordan Crouse
2020-02-19 21:32 ` Jordan Crouse [this message]
2020-02-19 21:32 ` [PATCH v1 3/4] arm64: dts: sdm845: Set the virtual address range for GMU allocations Jordan Crouse
2020-02-19 21:32 ` [PATCH v1 4/4] drm/msm/a6xx: Use the DMA API for GMU memory objects Jordan Crouse
2020-02-20 5:48 ` [PATCH v1 0/4] msm/gpu/a6xx: use the DMA-API for GMU memory allocations John Stultz
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=1582147978-31475-3-git-send-email-jcrouse@codeaurora.org \
--to=jcrouse@codeaurora.org \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=john.stultz@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robdclark@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sean@poorly.run \
/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).