From: Mark Rutland <mark.rutland@arm.com>
To: Liviu Dudau <Liviu.Dudau@arm.com>
Cc: Dave Airlie <airlied@gmail.com>,
Daniel Stone <daniel@fooishbar.org>,
David Brown <David.Brown@arm.com>,
Brian Starkey <Brian.Starkey@arm.com>,
DRI devel <dri-devel@lists.freedesktop.org>,
devicetree@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>
Subject: Re: [RFC][PATCH 1/2] dt/bindings: display: Add DT bindings for Mali Display Processors.
Date: Fri, 1 Apr 2016 17:47:57 +0100 [thread overview]
Message-ID: <20160401164757.GB7395@leverpostej> (raw)
In-Reply-To: <1459527712-9488-2-git-send-email-Liviu.Dudau@arm.com>
On Fri, Apr 01, 2016 at 05:21:51PM +0100, Liviu Dudau wrote:
> Add DT bindings documentation for the Mali Display Processor. The bindings
> describe the Mali DP500, DP550 and DP650 processors from ARM Ltd.
>
> Cc: Rob Herring <robh+dt@kernel.org>
> Cc: Pawel Moll <pawel.moll@arm.com>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Cc: Ian Campbell <ijc+devicetree@hellion.org.uk>
> Cc: Kumar Gala <galak@codeaurora.org>
>
> Signed-off-by: Liviu Dudau <Liviu.Dudau@arm.com>
> ---
> .../devicetree/bindings/display/arm,malidp.txt | 65 ++++++++++++++++++++++
> 1 file changed, 65 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/display/arm,malidp.txt
>
> diff --git a/Documentation/devicetree/bindings/display/arm,malidp.txt b/Documentation/devicetree/bindings/display/arm,malidp.txt
> new file mode 100644
> index 0000000..ed70de3
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/display/arm,malidp.txt
> @@ -0,0 +1,65 @@
> +ARM Mali-DP
> +
> +The following bindings apply to a family of Display Processors sold as
> +licensable IP by ARM Ltd. The bindings describe the Mali DP500, DP550 and
> +DP650 processors that offer multiple composition layers, support for
> +rotation and scaling output.
> +
> +Required properties:
> + - compatible: should be one of
> + "arm,mali-dp500"
> + "arm,mali-dp550"
> + "arm,mali-dp650"
> + depending on the particular implementation present in the hardware
> + - reg: Physical base address and size of the block of registers used by
> + the processor.
> + - interrupts: Interrupt list, as defined in ../interrupt-controller/interrupts.txt,
> + interrupt client nodes.
> + - interrupt-names: name of the engine inside the processor that will
> + use the corresponding interrupt. Should be one of "DE" or "SE".
s/be one of/contain/, s/or/and/, judging by the example.
Otherwise this generally looks fine to me.
Mark.
> + - clocks: A list of phandle + clock-specifier pairs, one for each entry
> + in 'clock-names'
> + - clock-names: A list of clock names. It should contain:
> + - "pclk": for the APB interface clock
> + - "aclk": for the AXI interface clock
> + - "mclk": for the main processor clock
> + - "pxlclk": for the pixel clock feeding the output PLL of the processor.
> + - arm,malidp-output-port-lines: Array of u8 values describing the number
> + of output lines per channel (R, G and B).
> +
> +Required sub-nodes:
> + - port: The Mali DP connection to an encoder input port. The connection
> + is modelled using the OF graph bindings specified in
> + Documentation/devicetree/bindings/graph.txt
> +
> +Optional properties:
> + - memory-region: phandle to a node describing memory (see
> + Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt)
> + to be used for the framebuffer; if not present, the framebuffer may
> + be located anywhere in memory.
> +
> +
> +Example:
> +
> +/ {
> + ...
> +
> + dp0: malidp@6f200000 {
> + compatible = "arm,mali-dp650";
> + reg = <0 0x6f200000 0 0x20000>;
> + memory-region = <&display_reserved>;
> + interrupts = <0 168 IRQ_TYPE_LEVEL_HIGH>,
> + <0 168 IRQ_TYPE_LEVEL_HIGH>;
> + interrupt-names = "DE", "SE";
> + clocks = <&oscclk2>, <&fpgaosc0>, <&fpgaosc1>, <&fpgaosc1>;
> + clock-names = "pxlclk", "mclk", "aclk", "pclk";
> + arm,malidp-output-port-lines = /bits/ 8 <8 8 8>;
> + port {
> + dp0_output: endpoint {
> + remote-endpoint = <&tda998x_2_input>;
> + };
> + };
> + };
> +
> + ...
> +};
> --
> 2.7.1
>
next prev parent reply other threads:[~2016-04-01 16:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 16:21 [RFC][PATCH 0/2] Initial support for ARM " Liviu Dudau
2016-04-01 16:21 ` [RFC][PATCH 1/2] dt/bindings: display: Add DT bindings for " Liviu Dudau
2016-04-01 16:47 ` Mark Rutland [this message]
2016-04-04 9:02 ` Liviu Dudau
2016-04-04 5:16 ` Rob Herring
2016-04-04 9:01 ` Liviu Dudau
2016-04-01 16:21 ` [RFC][PATCH 2/2] drm/arm: Add support " Liviu Dudau
2016-04-12 15:47 ` Daniel Vetter
2016-04-12 17:13 ` Liviu Dudau
2016-04-12 19:30 ` Daniel Vetter
2016-04-12 15:58 ` Daniel Vetter
2016-04-12 17:16 ` Liviu Dudau
2016-04-12 19:31 ` Daniel Vetter
2016-04-13 11:48 ` Emil Velikov
2016-04-13 13:48 ` Liviu Dudau
2016-04-13 15:29 ` Emil Velikov
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=20160401164757.GB7395@leverpostej \
--to=mark.rutland@arm.com \
--cc=Brian.Starkey@arm.com \
--cc=David.Brown@arm.com \
--cc=Liviu.Dudau@arm.com \
--cc=airlied@gmail.com \
--cc=daniel@fooishbar.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
/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®