Thread (4 messages) 4 messages, 3 authors, 2014-03-07

Re: [PATCH 0/9] Doc/DT: DT bindings for various display components

From: Tomi Valkeinen <hidden>
Date: 2014-03-07 12:56:36
Also in: dri-devel, linux-arm-kernel, linux-devicetree

Possibly related (same subject, not in this thread)

On 03/03/14 10:04, Tomi Valkeinen wrote:
Hi Rob, Pawel, Mark, Ian, Kumar,
Ping,

Any hints on how to continue with this?
On 28/02/14 18:56, Russell King - ARM Linux wrote:
quoted
On Fri, Feb 28, 2014 at 06:48:35PM +0200, Tomi Valkeinen wrote:
quoted
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
  

Attachments

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help