From: tomi.valkeinen@ti•com (Tomi Valkeinen)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 3/9] Doc/DT: Add DT binding documentation for DVI Connector
Date: Mon, 3 Mar 2014 08:42:35 +0200 [thread overview]
Message-ID: <5314245B.803@ti.com> (raw)
In-Reply-To: <20140228162327.GT21483@n2100.arm.linux.org.uk>
On 28/02/14 18:23, Russell King - ARM Linux wrote:
>> I guess the compatible string is the easiest way for differentation, at
>> least for the three main types, i.e. "dvi-d-connector" etc.
>>
>> "dvi-d-1l-connector" and "dvi-d-2l-connector" for the single/dual link?
>> That looks a bit funny.
>
> I think that starts getting a tad messy:
>
> dvi-a-connector
> dvi-d-1l-connector
> dvi-d-2l-connector
> dvi-i-1l-connector
> dvi-i-2l-connector
Yes, it's messy. Pondering this over the weekend, I think it makes sense
to have just one compatible string, as all those connectors are still
the same DVI connector, just different variations of the same.
> That's rather a lot of compatible strings. Another possibility is:
>
> compatible = "dvi-connector";
> analog;
> digital;
> single-link;
> dual-link;
>
> I'm debating whether "-signalling" should be on the 2nd and 3rd (or...
> -signaling depending on how you prefer to spell that word.) At least
> one of "analog" and/or "digital" must be specified, and if "digital"
> is specified, then exactly one of "single-link" or "dual-link" should
> be specified.
>
> So, this would mean we end up with:
>
> compatible = "dvi-connector";
> analog;
> digital;
> dual-link;
>
> for a DVI-I dual-link connector.
Another option would be:
num-links = 2;
But I like your suggestion more. We could also optimize it, "digital" is
extra as both "single-link" and "dual-link" mean also digital. But... I
don't see much point in optimizing that way. So I agree with your
suggestion as is.
Tomi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 901 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140303/8ac18169/attachment.sig>
next prev parent reply other threads:[~2014-03-03 6:42 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 12:20 [PATCH 0/9] Doc/DT: DT bindings for various display components Tomi Valkeinen
2014-02-28 12:20 ` [PATCH 1/9] Doc/DT: Add OMAP DSS DT Bindings Tomi Valkeinen
2014-02-28 12:20 ` [PATCH 2/9] Doc/DT: Add DT binding documentation for Analog TV Connector Tomi Valkeinen
2014-02-28 12:20 ` [PATCH 3/9] Doc/DT: Add DT binding documentation for DVI Connector Tomi Valkeinen
2014-02-28 13:43 ` Philipp Zabel
2014-03-03 6:25 ` Tomi Valkeinen
2014-02-28 15:59 ` Russell King - ARM Linux
2014-02-28 16:12 ` Tomi Valkeinen
2014-02-28 16:23 ` Russell King - ARM Linux
2014-02-28 16:28 ` Warner Losh
2014-03-03 6:42 ` Tomi Valkeinen [this message]
2014-03-04 12:54 ` Daniel Vetter
2014-03-05 8:41 ` Tomi Valkeinen
2014-03-06 8:39 ` Geert Uytterhoeven
2014-03-06 8:52 ` Tomi Valkeinen
2014-03-07 14:17 ` Philipp Zabel
2014-03-10 10:32 ` Tomi Valkeinen
2014-02-28 16:25 ` Sebastian Reichel
2014-02-28 16:25 ` Philipp Zabel
2014-03-10 21:45 ` Rob Herring
2014-03-11 6:39 ` Tomi Valkeinen
2014-03-11 8:00 ` Geert Uytterhoeven
2014-03-11 8:04 ` Tomi Valkeinen
2014-03-11 11:19 ` Philipp Zabel
2014-03-11 6:43 ` Tomi Valkeinen
2014-02-28 12:20 ` [PATCH 4/9] Doc/DT: Add DT binding documentation for HDMI Connector Tomi Valkeinen
2014-02-28 16:06 ` Russell King - ARM Linux
2014-02-28 16:15 ` Tomi Valkeinen
2014-02-28 16:34 ` Russell King - ARM Linux
2014-03-01 18:58 ` Geert Uytterhoeven
2014-03-03 7:23 ` Tomi Valkeinen
2014-03-05 8:42 ` Tomi Valkeinen
2014-03-04 12:59 ` Daniel Vetter
2014-02-28 12:20 ` [PATCH 5/9] Doc/DT: Add DT binding documentation for MIPI DPI Panel Tomi Valkeinen
2014-02-28 13:40 ` Philipp Zabel
2014-03-03 6:05 ` Tomi Valkeinen
2014-03-17 14:19 ` Laurent Pinchart
2014-03-18 6:41 ` Tomi Valkeinen
2014-03-18 7:06 ` Tomi Valkeinen
2014-02-28 12:20 ` [PATCH 6/9] Doc/DT: Add DT binding documentation for MIPI DSI CM Panel Tomi Valkeinen
2014-03-17 14:22 ` Laurent Pinchart
2014-03-18 6:33 ` Tomi Valkeinen
2014-03-18 12:43 ` Laurent Pinchart
2014-02-28 12:20 ` [PATCH 7/9] Doc/DT: Add DT binding documentation for Sony acx565akm panel Tomi Valkeinen
2014-02-28 13:38 ` Philipp Zabel
2014-02-28 13:47 ` Tomi Valkeinen
2014-02-28 12:20 ` [PATCH 8/9] Doc/DT: Add DT binding documentation for TFP410 encoder Tomi Valkeinen
2014-02-28 13:37 ` Philipp Zabel
2014-02-28 12:20 ` [PATCH 9/9] Doc/DT: Add DT binding documentation for tpd12s015 encoder Tomi Valkeinen
2014-02-28 16:13 ` Russell King - ARM Linux
2014-02-28 16:30 ` Tomi Valkeinen
2014-02-28 12:37 ` [PATCH 0/9] Doc/DT: DT bindings for various display components Tomasz Figa
2014-02-28 12:57 ` Sebastian Hesselbarth
2014-02-28 13:14 ` Tomi Valkeinen
2014-02-28 13:51 ` Sebastian Hesselbarth
2014-02-28 15:39 ` Tomi Valkeinen
2014-02-28 16:48 ` Russell King - ARM Linux
2014-02-28 13:47 ` Philipp Zabel
2014-02-28 13:56 ` Sebastian Hesselbarth
2014-02-28 16:27 ` Russell King - ARM Linux
2014-02-28 16:48 ` Tomi Valkeinen
2014-02-28 16:56 ` Russell King - ARM Linux
2014-03-03 8:04 ` Tomi Valkeinen
2014-03-07 12:56 ` Tomi Valkeinen
2014-03-10 16:05 ` Rob Herring
2014-03-10 16:40 ` Tomi Valkeinen
2014-03-10 20:32 ` Rob Herring
2014-03-12 8:15 ` Tomi Valkeinen
2014-03-17 13:55 ` Tomi Valkeinen
2014-03-21 15:37 ` Grant Likely
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=5314245B.803@ti.com \
--to=tomi.valkeinen@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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