dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: David Airlie <airlied@redhat.com>,
	Daniel Vetter <daniel@ffwll.ch>,
	Thomas Zimmermann <tzimmermann@suse.de>
Cc: devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Jon Hunter <jonathanh@nvidia.com>,
	linux-tegra@vger.kernel.org, Robin Murphy <robin.murphy@arm.com>
Subject: [PATCH v3 1/8] dt-bindings: display: simple-framebuffer: Support system memory framebuffers
Date: Thu, 17 Nov 2022 19:40:32 +0100	[thread overview]
Message-ID: <20221117184039.2291937-2-thierry.reding@gmail.com> (raw)
In-Reply-To: <20221117184039.2291937-1-thierry.reding@gmail.com>

From: Thierry Reding <treding@nvidia.com>

In order to support framebuffers residing in system memory, allow the
memory-region property to override the framebuffer memory specification
in the "reg" property.

Reviewed-by: Rob Herring <robh@kernel.org>
Signed-off-by: Thierry Reding <treding@nvidia.com>
---
 .../devicetree/bindings/display/simple-framebuffer.yaml      | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/Documentation/devicetree/bindings/display/simple-framebuffer.yaml b/Documentation/devicetree/bindings/display/simple-framebuffer.yaml
index dd64f70b5014..3e9857eb002e 100644
--- a/Documentation/devicetree/bindings/display/simple-framebuffer.yaml
+++ b/Documentation/devicetree/bindings/display/simple-framebuffer.yaml
@@ -63,6 +63,11 @@ properties:
   reg:
     description: Location and size of the framebuffer memory
 
+  memory-region:
+    maxItems: 1
+    description: Phandle to a node describing the memory to be used for the
+      framebuffer. If present, overrides the "reg" property (if one exists).
+
   clocks:
     description: List of clocks used by the framebuffer.
 
-- 
2.38.1


  reply	other threads:[~2022-11-17 18:40 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-17 18:40 [PATCH v3 0/8] drm/simpledrm: Support system memory framebuffers Thierry Reding
2022-11-17 18:40 ` Thierry Reding [this message]
2022-11-17 18:40 ` [PATCH v3 2/8] dt-bindings: display: simple-framebuffer: Document 32-bit BGR format Thierry Reding
2022-11-17 18:40 ` [PATCH v3 3/8] dt-bindings: reserved-memory: Support framebuffer reserved memory Thierry Reding
2022-11-17 18:40 ` [PATCH v3 4/8] drm/simpledrm: Use struct iosys_map consistently Thierry Reding
2022-11-18 13:56   ` Thomas Zimmermann
2022-11-17 18:40 ` [PATCH v3 5/8] drm/simpledrm: Add support for system memory framebuffers Thierry Reding
2022-11-18 14:11   ` Thomas Zimmermann
2022-11-18 14:21   ` Thomas Zimmermann
2022-11-18 15:38     ` Thierry Reding
2022-11-18 15:54       ` Thomas Zimmermann
2022-11-18 16:28         ` Thierry Reding
2022-11-17 18:40 ` [PATCH v3 6/8] drm/format-helper: Support the XB24 format Thierry Reding
2022-11-18 15:00   ` Thomas Zimmermann
2022-11-17 18:40 ` [PATCH v3 7/8] drm/simpledrm: Support the XB24/AB24 format Thierry Reding
2022-11-18 15:08   ` Thomas Zimmermann
2022-11-18 15:44     ` Thierry Reding
2022-11-18 16:10       ` Thomas Zimmermann
2022-11-18 16:34         ` Thierry Reding
2022-11-17 18:40 ` [PATCH v3 8/8] arm64: tegra: Add simple framebuffer on Jetson Xavier NX Thierry Reding
2023-01-17 14:55   ` Thomas Zimmermann
2023-01-19 15:10     ` 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=20221117184039.2291937-2-thierry.reding@gmail.com \
    --to=thierry.reding@gmail.com \
    --cc=airlied@redhat.com \
    --cc=daniel@ffwll.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-tegra@vger.kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=tzimmermann@suse.de \
    /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