All of lore.kernel.org
 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: Wed, 19 Sep 2012 06:43:54 -0700	[thread overview]
Message-ID: <5059CC1A.8000808@boundarydevices.com> (raw)
In-Reply-To: <20120919065240.GU6180@pengutronix.de>

On 09/18/2012 11:52 PM, Sascha Hauer wrote:
> On Tue, Sep 18, 2012 at 03:06:36PM -0700, Eric Nelson wrote:
>> 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
>>>
>>> +
>>> +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?
>
> No, we are using the of videomode helper, see
>
> http://www.mail-archive.com/devicetree-discuss at lists.ozlabs.org/msg18618.html
>
> It is not included here to not add a dependency on it. We are trying to
> mainline this separately.
>
> Sascha
>

Thanks Sascha.

WARNING: multiple messages have this Message-ID (diff)
From: Eric Nelson <eric.nelson@boundarydevices.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: David Jander <david.jander@protonic.nl>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	DRI Development <dri-devel@lists.freedesktop.org>,
	Ahmed Ammar <aammar@genesi-usa.com>,
	kernel@pengutronix.de, Matt Sealey <matt@genesi-usa.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 5/6] staging: drm/imx: Add devicetree binding documentation
Date: Wed, 19 Sep 2012 06:43:54 -0700	[thread overview]
Message-ID: <5059CC1A.8000808@boundarydevices.com> (raw)
In-Reply-To: <20120919065240.GU6180@pengutronix.de>

On 09/18/2012 11:52 PM, Sascha Hauer wrote:
> On Tue, Sep 18, 2012 at 03:06:36PM -0700, Eric Nelson wrote:
>> 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
>>>
>>> +
>>> +example:
>>> +
>>> +display@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?
>
> No, we are using the of videomode helper, see
>
> http://www.mail-archive.com/devicetree-discuss@lists.ozlabs.org/msg18618.html
>
> It is not included here to not add a dependency on it. We are trying to
> mainline this separately.
>
> Sascha
>

Thanks Sascha.

  reply	other threads:[~2012-09-19 13:43 UTC|newest]

Thread overview: 36+ 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 ` Sascha Hauer
2012-09-12 10:31 ` [PATCH 1/6] staging: drm/imx: Add i.MX drm core support Sascha Hauer
2012-09-12 10:31   ` Sascha Hauer
2012-09-12 16:49   ` Greg Kroah-Hartman
2012-09-12 16:49     ` Greg Kroah-Hartman
2012-09-13  6:56     ` Sascha Hauer
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   ` Sascha Hauer
2012-09-12 10:31 ` [PATCH 3/6] staging: drm/imx: add i.MX IPUv3 base driver Sascha Hauer
2012-09-12 10:31   ` Sascha Hauer
2012-09-14  9:29   ` Dirk Behme
2012-09-14  9:29     ` Dirk Behme
2012-09-14  9:38     ` Sascha Hauer
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   ` Sascha Hauer
2012-09-12 10:31 ` [PATCH 5/6] staging: drm/imx: Add devicetree binding documentation Sascha Hauer
2012-09-12 10:31   ` Sascha Hauer
2012-09-18 22:06   ` Eric Nelson
2012-09-18 22:06     ` Eric Nelson
2012-09-19  6:52     ` Sascha Hauer
2012-09-19  6:52       ` Sascha Hauer
2012-09-19 13:43       ` Eric Nelson [this message]
2012-09-19 13:43         ` Eric Nelson
2012-09-12 10:31 ` [PATCH 6/6] staging: drm/imx: Add TODO Sascha Hauer
2012-09-12 10:31   ` Sascha Hauer
2012-09-19  5:53   ` Shawn Guo
2012-09-19  5:53     ` Shawn Guo
2012-09-19  7:18     ` Sascha Hauer
2012-09-19  7:18       ` Sascha Hauer
2012-09-19  8:05       ` Greg Kroah-Hartman
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
2012-09-21  8:07   ` 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=5059CC1A.8000808@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.