From: tomi.valkeinen@ti•com (Tomi Valkeinen)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 0/9] Doc/DT: DT bindings for various display components
Date: Mon, 3 Mar 2014 10:04:38 +0200 [thread overview]
Message-ID: <53143796.2050309@ti.com> (raw)
In-Reply-To: <20140228165628.GX21483@n2100.arm.linux.org.uk>
Hi Rob, Pawel, Mark, Ian, Kumar,
On 28/02/14 18:56, Russell King - ARM Linux wrote:
> On Fri, Feb 28, 2014 at 06:48:35PM +0200, Tomi Valkeinen wrote:
>> This is totally unclear to me. How does it become a public standard?
>> What's the forum for this?
>
> Me too. That's where I'd hope someone on devicetree-discuss will be
> able to help us work out what's the right approach here. :)
The story briefly so far: I've implemented DT support for OMAP display,
and created bindings for various (non-OMAP) display components,
including generic connector bindings for DVI, HDMI and analog-tv.
Russell's point was that these connector bindings are very generic, i.e.
they are not for any particular chip from a particular vendor, but for
any connector for DVI, HDMI or analog-tv. And he's worried that maybe we
shouldn't define such generic bindings without consulting the whole
device-tree community (i.e including non-linux users).
So the question is, is there such a community and a forum to bring up
this kind of things? If yes, should we bring this up there? If yes, what
kind of things in general should be brought into the attention of
non-linux users?
What I wonder here is that while a thing like DVI connector is, of
course, more generic than, say, "ti,tfp410" encoder chip, but isn't the
case still the same: we're defining global bindings for hardware that
should work for everyone, not only Linux users?
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/e40abbd0/attachment-0001.sig>
next prev parent reply other threads:[~2014-03-03 8:04 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
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 [this message]
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=53143796.2050309@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