[PATCH v2 1/7] dt-bindings: display: simple-framebuffer: Support system memory framebuffers

[Thomas Zimmermann]

Hi

Am 07.10.22 um 14:49 schrieb Thierry Reding:
> From: Thierry Reding <treding at 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.

What happens if both properties are present and they disagree with each 
other?

I understand that the framebuffer is behind 'memory-region', but does 
'reg' still contain device memory?  Do we need to acquire ownership from 
within the driver?

Best regards
Thomas

> 
> Signed-off-by: Thierry Reding <treding at 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.
>   

-- 
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20221010/8f19fb57/attachment.sig>