linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: eric.nelson@boundarydevices.com (Eric Nelson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 5/6] staging: drm/imx: Add devicetree binding documentation
Date: Tue, 18 Sep 2012 15:06:36 -0700	[thread overview]
Message-ID: <5058F06C.1020409@boundarydevices.com> (raw)
In-Reply-To: <1347445874-10779-6-git-send-email-s.hauer@pengutronix.de>

Hi Sascha,

On 09/12/2012 03:31 AM, Sascha Hauer wrote:
> From: Philipp Zabel<p.zabel@pengutronix.de>
>
> Signed-off-by: Philipp Zabel<p.zabel@pengutronix.de>
> Signed-off-by: Sascha Hauer<s.hauer@pengutronix.de>
> ---
>   .../bindings/staging/imx-drm/fsl-imx-drm.txt       |   41 ++++++++++++++++++++
>   1 file changed, 41 insertions(+)
>   create mode 100644 Documentation/devicetree/bindings/staging/imx-drm/fsl-imx-drm.txt
>
> diff --git a/Documentation/devicetree/bindings/staging/imx-drm/fsl-imx-drm.txt b/Documentation/devicetree/bindings/staging/imx-drm/fsl-imx-drm.txt
> new file mode 100644
> index 0000000..07654f0
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/staging/imx-drm/fsl-imx-drm.txt
> @@ -0,0 +1,41 @@
> +Freescale i.MX IPUv3
> +====================
> +
> +Required properties:
> +- compatible: Should be "fsl,<chip>-ipu"
> +- reg: should be register base and length as documented in the
> +  datasheet
> +- interrupts: Should contain sync interrupt and error interrupt,
> +  in this order.
> +- #crtc-cells: 1, See below
> +
> +example:
> +
> +ipu: ipu at 18000000 {
> +	#crtc-cells =<1>;
> +	compatible = "fsl,imx53-ipu";
> +	reg =<0x18000000 0x080000000>;
> +	interrupts =<11 10>;
> +};
> +
> +Parallel display support
> +========================
> +
> +Required properties:
> +- compatible: Should be "fsl,imx-parallel-display"
> +- crtc: the crtc this display is connected to, see below
> +Optional properties:
> +- interface_pix_fmt: How this display is connected to the
> +  crtc. Currently supported types: "rgb24", "rgb565"
> +- edid: verbatim EDID data block describing attached display.
> +- ddc: phandle describing the i2c bus handling the display data
> +  channel
> +
> +example:
> +
> +display at di0 {
> +	compatible = "fsl,imx-parallel-display";
> +	edid = [edid-data];
> +	crtc =<&ipu 0>;
> +	interface-pix-fmt = "rgb24";
> +};

Do you have a working sample of [edid-data] for a parallel/LVDS/HDMI
display or know a good way to produce one?

Thanks in advance,


Eric

  reply	other threads:[~2012-09-18 22:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-12 10:31 [PATCH] Add i.MX IPUv3 base/KMS driver to the staging tree Sascha Hauer
2012-09-12 10:31 ` [PATCH 1/6] staging: drm/imx: Add i.MX drm core support Sascha Hauer
2012-09-12 16:49   ` Greg Kroah-Hartman
2012-09-13  6:56     ` Sascha Hauer
2012-09-12 10:31 ` [PATCH 2/6] staging: drm/imx: Add parallel display support Sascha Hauer
2012-09-12 10:31 ` [PATCH 3/6] staging: drm/imx: add i.MX IPUv3 base driver Sascha Hauer
2012-09-14  9:29   ` Dirk Behme
2012-09-14  9:38     ` Sascha Hauer
2012-09-12 10:31 ` [PATCH 4/6] staging: drm/imx: Add i.MX IPUv3 crtc support Sascha Hauer
2012-09-12 10:31 ` [PATCH 5/6] staging: drm/imx: Add devicetree binding documentation Sascha Hauer
2012-09-18 22:06   ` Eric Nelson [this message]
2012-09-19  6:52     ` Sascha Hauer
2012-09-19 13:43       ` Eric Nelson
2012-09-12 10:31 ` [PATCH 6/6] staging: drm/imx: Add TODO Sascha Hauer
2012-09-19  5:53   ` Shawn Guo
2012-09-19  7:18     ` Sascha Hauer
2012-09-19  8:05       ` Greg Kroah-Hartman
  -- strict thread matches above, loose matches on Subject: below --
2012-09-21  8:07 [PATCH] Add i.MX IPUv3 base/KMS driver to the staging tree Sascha Hauer
2012-09-21  8:07 ` [PATCH 5/6] staging: drm/imx: Add devicetree binding documentation Sascha Hauer

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=5058F06C.1020409@boundarydevices.com \
    --to=eric.nelson@boundarydevices.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).