From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: dri-devel@lists.freedesktop.org
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org,
Alexandre TORGUE <alexandre.torgue@st.com>,
Arnd Bergmann <arnd@arndb.de>,
Russell King <linux@armlinux.org.uk>,
Rob Herring <robh+dt@kernel.org>,
Philippe Cornu <philippe.cornu@st.com>,
Yannick Fertre <yannick.fertre@st.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Mickael Reulier <mickael.reulier@st.com>,
Gabriel FERNANDEZ <gabriel.fernandez@st.com>,
linux-arm-kernel@lists.infradead.org, kernel@stlinux.com
Subject: Re: [PATCH v1 1/7] dt-bindings: display: add STM32 LTDC driver
Date: Mon, 16 Jan 2017 22:30:49 +0200 [thread overview]
Message-ID: <2080174.sm3cyM9MmB@avalon> (raw)
In-Reply-To: <1484573344-11609-2-git-send-email-yannick.fertre@st.com>
Hi Yannick,
Thank you for the patch.
On Monday 16 Jan 2017 14:28:58 Yannick Fertre wrote:
> Signed-off-by: Yannick Fertre <yannick.fertre@st.com>
> ---
> .../devicetree/bindings/display/st,ltdc.txt | 57 ++++++++++++++++++
> 1 file changed, 57 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/display/st,ltdc.txt
>
> diff --git a/Documentation/devicetree/bindings/display/st,ltdc.txt
> b/Documentation/devicetree/bindings/display/st,ltdc.txt new file mode
> 100644
> index 0000000..20e89da
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/display/st,ltdc.txt
> @@ -0,0 +1,57 @@
> +* STMicroelectronics STM32 lcd-tft display controller
> +
> +- st-display-subsystem: Master device for DRM sub-components
> + This device must be the parent of all the sub-components and is
> responsible
> + of bind them.
Why do you need this ? At a quick glance the ltdc node should be enough.
> + Required properties:
> + - compatible: "st,display-subsystem"
> + - ranges: to allow probing of subdevices
> +
> +- ltdc_host: lcd-tft display controller host
> + must be a sub-node of st-display-subsystem
> + Required properties:
> + - compatible: "st,ltdc"
> + - reg: Physical base address of the IP registers and length of memory
> mapped region.
> + - clocks: from common clock binding: handle hardware IP needed clocks,
> the
> + number of clocks may depend of the SoC type.
> + See ../clocks/clock-bindings.txt for details.
> + - clock-names: names of the clocks listed in clocks property in the same
> + order.
You need to define the required/optional clocks with their names here. If they
vary depending on the SoC, the DT bindings document need to list them for each
SoC.
> + - resets: resets to be used by the device
> + See ../reset/reset.txt for details.
> + - reset-names: names of the resets listed in resets property in the same
> + order.
> + Required nodes:
> + - Video port for RGB output.
> +
> +Example:
> +
> +/ {
> + ...
> + soc {
> + ...
> + st-display-subsystem {
> + compatible = "st,display-subsystem";
> + #address-cells = <1>;
> + #size-cells = <1>;
> + ranges;
> + dma-ranges;
> +
> + ltdc_host: stm32-ltdc@40016800 {
> + compatible = "st,ltdc";
> + reg = <0x40016800 0x200>;
> + interrupts = <88>, <89>;
> + resets = <&rcc 314>;
> + clocks = <&rcc 1 8>;
> + clock-names = "clk-lcd";
> + status = "disabled";
> +
> + port {
> + ltdc_out_rgb: endpoint {
> + };
> + };
> + };
> + };
> + ...
> + };
> +};
--
Regards,
Laurent Pinchart
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-01-16 20:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 13:28 [PATCH v1 0/7] DRM: add LTDC support for STM32F4 Yannick Fertre
2017-01-16 13:28 ` [PATCH v1 1/7] dt-bindings: display: add STM32 LTDC driver Yannick Fertre
2017-01-16 20:30 ` Laurent Pinchart [this message]
2017-01-19 16:16 ` Yannick FERTRE
2017-01-19 16:31 ` Rob Herring
[not found] ` <1484573344-11609-2-git-send-email-yannick.fertre-qxv4g6HH51o@public.gmane.org>
2017-01-19 16:29 ` Rob Herring
2017-01-16 13:28 ` [PATCH v1 2/7] drm/st: Add " Yannick Fertre
2017-01-16 13:29 ` [PATCH v1 3/7] dt-bindings: Add Ampire AM-480272H3TMQW-T01H panel Yannick Fertre
2017-01-19 16:32 ` Rob Herring
2017-01-16 13:29 ` [PATCH v1 4/7] drm/panel: simple: Add support for Ampire AM-480272H3TMQW-T01H Yannick Fertre
2017-01-16 13:29 ` [PATCH v1 5/7] ARM: dts: stm32f429: Add ltdc support Yannick Fertre
[not found] ` <1484573344-11609-6-git-send-email-yannick.fertre-qxv4g6HH51o@public.gmane.org>
2017-01-16 15:58 ` Alexandre Torgue
2017-01-16 13:29 ` [PATCH v1 6/7] ARM: dts: stm32429i-eval: Enable ltdc & simple panel on Eval board Yannick Fertre
2017-01-16 16:02 ` Alexandre Torgue
2017-01-16 13:29 ` [PATCH v1 7/7] ARM: configs: Add STM32 LTDC support in STM32 defconfig Yannick Fertre
2017-01-16 16:03 ` Alexandre Torgue
2017-01-16 16:02 ` [PATCH v1 0/7] DRM: add LTDC support for STM32F4 Neil Armstrong
2017-01-19 10:35 ` Yannick FERTRE
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=2080174.sm3cyM9MmB@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=alexandre.torgue@st.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gabriel.fernandez@st.com \
--cc=kernel@stlinux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mickael.reulier@st.com \
--cc=philippe.cornu@st.com \
--cc=robh+dt@kernel.org \
--cc=yannick.fertre@st.com \
/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