From: Florian Vaussard <florian.vaussard@epfl.ch>
To: Javier Martinez Canillas <javier@dowhile0.org>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: "Benoît Cousson" <bcousson@baylibre.com>,
"Tony Lindgren" <tony@atomide.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Ash Charles" <ash@gumstix.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 2/2] ARM: dts: duovero-parlor: Add HDMI output
Date: Tue, 25 Feb 2014 08:54:22 +0100 [thread overview]
Message-ID: <530C4C2E.8040606@epfl.ch> (raw)
In-Reply-To: <CABxcv=kKxidVJWcMrueB+edW=g_6gcucvi6=7p=EZ_WooCpbMA@mail.gmail.com>
Hi Russell, Javier,
On 02/24/2014 09:22 PM, Javier Martinez Canillas wrote:
> Hi Russell,
>
> On Mon, Feb 24, 2014 at 3:03 PM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
>> On Mon, Feb 24, 2014 at 06:07:49PM +0100, Florian Vaussard wrote:
>>> + hdmi0: connector@0 {
>>> + compatible = "hdmi-connector";
>>
>> This looks way to generic a compatible string. Are you sure it's
>> correct?
>>
>
> That compatible string is correct according to the latest series
> posted by Tomi Valkeinen to add DT bindings for the OMAP Display
> SubSystem (DSS) [0].
>
Indeed, this compatible string comes from the DSS series.
> The property is added on this patch [1] and as far as I understood the
> idea is that it could be a generic DT binding that can be used by
> platform specific HDMI connectors like the omap dss HDMI connector
> [2].
>
On the other side, looking at
drivers/video/omap2/displays-new/connector-hdmi.c from the DSS series
[1], the compatible string is "omapdss,hdmi-connector", which makes me
wonder which one should be used :) BTW, "omapdss" seems a strange
prefix, isn't it?
Tomi, any inputs?
Regards,
Florian
[1]
https://git.kernel.org/cgit/linux/kernel/git/tomba/linux.git/tree/drivers/video/omap2/displays-new/connector-hdmi.c?h=work/dss-dt-review-3
next prev parent reply other threads:[~2014-02-25 7:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 17:07 [PATCH 0/2] ARM: dts: OMAP4: Add support for DuoVero/Parlor Florian Vaussard
2014-02-24 17:07 ` [PATCH 1/2] ARM: dts: Add support for OMAP4 Gumstix DuoVero/Parlor Florian Vaussard
2014-03-03 10:08 ` Florian Vaussard
2014-03-04 18:17 ` Tony Lindgren
2014-02-24 17:07 ` [PATCH 2/2] ARM: dts: duovero-parlor: Add HDMI output Florian Vaussard
2014-02-24 18:03 ` Russell King - ARM Linux
2014-02-24 20:22 ` Javier Martinez Canillas
2014-02-25 7:54 ` Florian Vaussard [this message]
2014-02-25 12:39 ` Russell King - ARM Linux
2014-02-25 13:05 ` Florian Vaussard
[not found] ` <20140225123921.GY27282-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2014-02-25 13:41 ` Sebastian Reichel
2014-02-25 16:51 ` Laurent Pinchart
2014-02-25 20:56 ` Russell King - ARM Linux
2014-02-26 11:14 ` Tomi Valkeinen
[not found] ` <530DCC8A.6060708-l0cyMroinI0@public.gmane.org>
2014-02-26 12:03 ` Russell King - ARM Linux
2014-02-26 12:44 ` Tomi Valkeinen
2014-02-26 13:28 ` Russell King - ARM Linux
2014-02-26 14:35 ` Tomi Valkeinen
2014-03-06 23:29 ` Laurent Pinchart
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=530C4C2E.8040606@epfl.ch \
--to=florian.vaussard@epfl.ch \
--cc=ash@gumstix.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=javier@dowhile0.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=tomi.valkeinen@ti.com \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).