From: Thierry Reding <thierry.reding@gmail.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
Sean Paul <seanpaul@google.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
sunil joshi <joshi@samsung.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Ajay kumar <ajaynumb@gmail.com>,
Prashanth G <prashanth.g@samsung.com>,
Ajay Kumar <ajaykumar.rs@samsung.com>
Subject: Re: [PATCH V7 11/12] Documentation: bridge: Add documentation for ps8622 DT properties
Date: Wed, 8 Oct 2014 09:09:19 +0200 [thread overview]
Message-ID: <20141008070918.GA4999@ulmo> (raw)
In-Reply-To: <2230493.RvivJykn5T@avalon>
[-- Attachment #1.1: Type: text/plain, Size: 2481 bytes --]
On Tue, Oct 07, 2014 at 05:49:24PM +0300, Laurent Pinchart wrote:
> Hi Ajay,
>
> On Tuesday 07 October 2014 16:06:55 Ajay kumar wrote:
> > On Tue, Oct 7, 2014 at 4:00 PM, Tomi Valkeinen wrote:
> > > On 20/09/14 14:22, Ajay kumar wrote:
> > >> Well, I am okay with using video ports to describe the relationship
> > >> between the encoder, bridge and the panel.
> > >> But, its just that I need to make use of 2 functions when phandle
> > >> does it using just one function ;)
> > >> - panel_node = of_parse_phandle(dev->of_node, "panel", 0)
> > >> + endpoint = of_graph_get_next_endpoint(dev->of_node, NULL);
> > >> + if (!endpoint)
> > >> + return -EPROBE_DEFER;
> > >> +
> > >> + panel_node = of_graph_get_remote_port_parent(endpoint);
> > >> + if (!panel_node)
> > >> + return -EPROBE_DEFER;
> > >>
> > >>
> > >> If nobody else has objections over using of_graph functions instead
> > >> of phandles, I can respin this patchset by making use of video ports.
> > >
> > > The discussion did digress somewhat.
> > >
> > > As a clarification, I'm in no way nack'ing this series because it
> > > doesn't use the graphs for video connections. I don't see the simple
> > > phandle bindings used here as broken as such.
> >
> > Well, I am okay with any approach you guys decide on. I desperately want
> > this to get this in since it has been floating around for quite sometime.
> > The more we drag this, the more rework for me since the number of platforms
> > using bridge support is increasing daily!
>
> I won't nack this patch either. I'm however concerned that we'll run straight
> into the wall if we don't come up with an agreement on a standard way to
> describe connections in DT for display devices, which is why I would prefer
> the ps8622 bindings to use OF graph to describe connections.
I think there's not really an easy way out here. It's pretty bold trying
to come up with a common way to describe bridges when we have only a
single one (and a single use-case at that). The worst that can happen is
that we need to change the binding at some point, in which case we may
have to special-case early drivers, but I really don't think that's as
much of an issue as everybody seems to think.
This series has been floating around for months because we're being
overly prudent to accept a binding that /may/ turn out to not be generic
enough.
Thierry
[-- Attachment #1.2: Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-10-08 7:09 UTC|newest]
Thread overview: 93+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 14:39 [PATCH V7 11/12] Documentation: bridge: Add documentation for ps8622 DT properties Ajay Kumar
2014-08-27 14:39 ` [PATCH V7 10/12] Documentation: devicetree: Add vendor prefix for parade Ajay Kumar
2014-08-27 14:39 ` [PATCH V7 09/12] Documentation: drm: bridge: move to video/bridge Ajay Kumar
2014-09-17 11:52 ` [PATCH V7 11/12] Documentation: bridge: Add documentation for ps8622 DT properties Tomi Valkeinen
2014-09-17 14:29 ` Ajay kumar
2014-09-17 16:22 ` Tomi Valkeinen
2014-09-18 5:50 ` Ajay kumar
2014-09-19 12:54 ` Tomi Valkeinen
2014-09-19 13:59 ` Ajay kumar
2014-09-19 14:28 ` Tomi Valkeinen
2014-09-20 11:22 ` Ajay kumar
2014-09-20 15:27 ` Javier Martinez Canillas
2014-09-22 6:00 ` Ajay kumar
2014-09-22 15:05 ` Tomi Valkeinen
2014-10-07 10:30 ` Tomi Valkeinen
2014-10-07 10:36 ` Ajay kumar
2014-10-07 14:49 ` Laurent Pinchart
2014-10-08 7:09 ` Thierry Reding [this message]
2014-10-10 13:03 ` Ajay kumar
2014-10-16 8:23 ` Ajay kumar
2014-10-16 9:04 ` Laurent Pinchart
2014-10-28 9:12 ` Javier Martinez Canillas
2014-10-28 11:12 ` Ajay kumar
2014-09-22 8:26 ` Thierry Reding
2014-09-22 14:42 ` Tomi Valkeinen
2014-09-23 5:53 ` Thierry Reding
2014-09-23 8:41 ` Tomi Valkeinen
2014-09-23 9:28 ` Thierry Reding
2014-09-23 11:15 ` Tomi Valkeinen
2014-09-23 14:29 ` Thierry Reding
2014-09-23 15:25 ` Tomi Valkeinen
2014-09-22 8:10 ` Thierry Reding
2014-09-22 8:31 ` Ajay kumar
2014-09-22 10:41 ` Thierry Reding
2014-09-22 11:23 ` Ajay kumar
2014-09-22 11:35 ` Thierry Reding
2014-09-22 12:12 ` Ajay kumar
2014-09-23 0:00 ` Laurent Pinchart
2014-09-23 5:55 ` Thierry Reding
2014-09-23 6:11 ` Ajay kumar
2014-09-23 6:28 ` Thierry Reding
2014-09-23 11:47 ` DT property to selectively disable device features (was [PATCH V7 11/12] Documentation: bridge: Add documentation for ps8622 DT properties) Laurent Pinchart
2014-09-22 8:06 ` [PATCH V7 11/12] Documentation: bridge: Add documentation for ps8622 DT properties Thierry Reding
2014-09-22 14:23 ` Tomi Valkeinen
2014-09-23 6:04 ` Thierry Reding
2014-09-23 7:24 ` Andrzej Hajda
2014-09-23 8:35 ` Thierry Reding
2014-09-23 9:40 ` Tomi Valkeinen
2014-09-23 10:01 ` Thierry Reding
2014-09-23 12:09 ` Tomi Valkeinen
2014-09-23 14:38 ` Thierry Reding
2014-09-23 15:33 ` Tomi Valkeinen
2014-09-23 9:43 ` Andrzej Hajda
2014-09-23 10:10 ` Thierry Reding
2014-09-23 10:34 ` Andrzej Hajda
2014-09-23 14:41 ` Thierry Reding
2014-09-24 7:11 ` Andrzej Hajda
2014-09-24 8:27 ` Tomi Valkeinen
2014-09-23 11:33 ` Laurent Pinchart
2014-09-23 8:54 ` Tomi Valkeinen
2014-09-23 9:39 ` Thierry Reding
2014-09-23 11:31 ` Tomi Valkeinen
2014-09-23 14:45 ` Thierry Reding
2014-09-24 8:42 ` Tomi Valkeinen
2014-10-06 14:40 ` Laurent Pinchart
2014-10-07 7:06 ` Tomi Valkeinen
2014-10-07 7:23 ` Laurent Pinchart
2014-10-07 8:25 ` Tomi Valkeinen
2014-10-07 16:14 ` Laurent Pinchart
2014-09-22 7:54 ` Thierry Reding
2014-09-22 14:04 ` Tomi Valkeinen
2014-09-23 6:21 ` Thierry Reding
2014-09-23 9:30 ` Tomi Valkeinen
2014-09-23 9:53 ` Thierry Reding
2014-09-23 11:12 ` Laurent Pinchart
2014-09-23 14:50 ` Thierry Reding
2014-09-23 12:00 ` Tomi Valkeinen
2014-09-23 14:58 ` Thierry Reding
2014-09-24 9:08 ` Tomi Valkeinen
2014-09-25 6:23 ` Thierry Reding
2014-10-06 11:34 ` Tomi Valkeinen
2014-10-06 13:55 ` Laurent Pinchart
2014-09-23 10:02 ` Andrzej Hajda
2014-09-23 10:02 ` Andrzej Hajda
2014-09-23 11:10 ` Laurent Pinchart
2014-09-23 11:18 ` Andrzej Hajda
2014-09-23 11:23 ` Laurent Pinchart
2014-09-23 11:47 ` Andrzej Hajda
2014-09-23 11:52 ` Laurent Pinchart
2014-09-23 12:40 ` Andrzej Hajda
2014-09-23 12:40 ` Andrzej Hajda
2014-09-23 14:49 ` Thierry Reding
2014-10-06 14:38 ` 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=20141008070918.GA4999@ulmo \
--to=thierry.reding@gmail.com \
--cc=ajaykumar.rs@samsung.com \
--cc=ajaynumb@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=joshi@samsung.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=prashanth.g@samsung.com \
--cc=seanpaul@google.com \
--cc=tomi.valkeinen@ti.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).