From: Rob Herring <robh@kernel.org>
To: Joel Stanley <joel@jms.id.au>
Cc: devicetree@vger.kernel.org, linux-aspeed@lists.ozlabs.org,
David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org, Andrew Jeffery <andrew@aj.id.au>,
Sean Paul <sean@poorly.run>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 1/3] dt-bindings: gpu: Add ASPEED GFX bindings document
Date: Sat, 06 Apr 2019 01:06:49 -0500 [thread overview]
Message-ID: <5ca841fb.1c69fb81.58fe6.fabd@mx.google.com> (raw)
In-Reply-To: <20190403001909.31637-2-joel@jms.id.au>
On Wed, Apr 03, 2019 at 10:49:07AM +1030, Joel Stanley wrote:
> This describes the ASPEED BMC SoC's display controller.
>
> Signed-off-by: Joel Stanley <joel@jms.id.au>
> Reviewed-by: Andrew Jeffery <andrew@aj.id.au>
> ---
> v3:
> Add Andrew's reviewed-by
>
> .../devicetree/bindings/gpu/aspeed-gfx.txt | 41 +++++++++++++++++++
> 1 file changed, 41 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/gpu/aspeed-gfx.txt
>
> diff --git a/Documentation/devicetree/bindings/gpu/aspeed-gfx.txt b/Documentation/devicetree/bindings/gpu/aspeed-gfx.txt
> new file mode 100644
> index 000000000000..a74033332668
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/gpu/aspeed-gfx.txt
> @@ -0,0 +1,41 @@
> +Device tree configuration for the GFX display deivce on the AST2500 SoCs.
> +
> +Required properties:
> + - compatible
> + * Must be one of the following:
> + + aspeed,ast2500-gfx
> + + aspeed,ast2400-gfx
> + * In addition, the ASPEED pinctrl bindings require the 'syscon' property to
> + be present
> +
> + - reg: Physical base address and length of the GFX registers
> +
> + - interrupts: interrupt number for the GFX device
> +
> + - clocks: clock number used to generate the pixel clock
> +
> + - resets: reset line that must be released to use the GFX device
> +
> + - memory-region:
> + Phandle to a memory region to allocate from, as defined in
> + Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt
If required, does that mean the h/w can only use certain memory? Why?
> +
> +
> +Example:
> +
> +gfx: display@1e6e6000 {
> + compatible = "aspeed,ast2500-gfx", "syscon";
> + reg = <0x1e6e6000 0x1000>;
> + reg-io-width = <4>;
Not documented as used. This should be implied by the compatible though.
> + clocks = <&syscon ASPEED_CLK_GATE_D1CLK>;
> + resets = <&syscon ASPEED_RESET_CRT1>;
> + interrupts = <0x19>;
> + memory-region = <&gfx_memory>;
> +};
> +
> +gfx_memory: framebuffer {
> + size = <0x01000000>;
> + alignment = <0x01000000>;
> + compatible = "shared-dma-pool";
> + reusable;
> +};
> --
> 2.20.1
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-04-06 6:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 0:19 [PATCH v3 0/3] drm: Add ASPEED BMC 'GFX' driver Joel Stanley
2019-04-03 0:19 ` [PATCH v3 1/3] dt-bindings: gpu: Add ASPEED GFX bindings document Joel Stanley
2019-04-06 6:06 ` Rob Herring [this message]
2019-04-03 0:19 ` [PATCH v3 2/3] drm: Add ASPEED GFX driver Joel Stanley
2019-04-03 0:19 ` [PATCH v3 3/3] MAINTAINERS: Add ASPEED BMC GFX DRM driver entry Joel Stanley
2019-04-03 7:11 ` Daniel Vetter
2019-04-03 7:30 ` Joel Stanley
2019-04-03 7:36 ` Joel Stanley
2019-04-04 1:04 ` Andrew Jeffery
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=5ca841fb.1c69fb81.58fe6.fabd@mx.google.com \
--to=robh@kernel.org \
--cc=airlied@linux.ie \
--cc=andrew@aj.id.au \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.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).