From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: devicetree@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
seanpaul@google.com, daniel.vetter@ffwll.ch, joshi@samsung.com,
dri-devel@lists.freedesktop.org,
Andrzej Hajda <a.hajda@samsung.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
ajaynumb@gmail.com, 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: Mon, 06 Oct 2014 17:38:09 +0300 [thread overview]
Message-ID: <2733435.m6m6ahdT9t@avalon> (raw)
In-Reply-To: <20140923144937.GG5982@ulmo>
Hi Thierry,
On Tuesday 23 September 2014 16:49:38 Thierry Reding wrote:
> On Tue, Sep 23, 2014 at 02:52:24PM +0300, Laurent Pinchart wrote:
> > On Tuesday 23 September 2014 13:47:40 Andrzej Hajda wrote:
> >> On 09/23/2014 01:23 PM, Laurent Pinchart wrote:
> [...]
>
> >>> This becomes an issue even on Linux when considering video-related
> >>> devices that can be part of either a capture pipeline or a display
> >>> pipeline. If the link always goes in the data flow direction, then it
> >>> will be easy to locate the downstream device (bridge or panel) from
> >>> the display controller driver, but it would be much more difficult to
> >>> locate the same device from a camera driver as all of a sudden the
> >>> device would become an upstream device.
> >>
> >> Why?
> >>
> >> If you have graph:
> >> sensor --> camera
> >>
> >> Then camera register itself in some framework as a destination device
> >> and sensor looks in this framework for the device identified by remote
> >> endpoint. Then sensor tells camera it is connected to it and voila.
> >
> > Except that both kernelspace and userspace deal with cameras the other way
> > around, the master device is the camera receiver, not the camera sensor.
> > DRM is architected the same way, with the component that performs DMA
> > operations being the master device.
>
> I don't see what's wrong with having the camera reference the sensor by
> phandle instead. That's much more natural in my opinion.
The problem, as explained by Tomi in a more recent e-mail (let's thus discuss
the issue there) is that making the phandles pointing outwards from the CPU
point of view stops working when the same chip or IP core can be used in both
a camera and a display pipeline (and we have real use cases for that), or when
the CPU isn't involved at all in the pipeline.
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2014-10-06 14:38 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
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 [this message]
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=2733435.m6m6ahdT9t@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=a.hajda@samsung.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=linux-samsung-soc@vger.kernel.org \
--cc=prashanth.g@samsung.com \
--cc=seanpaul@google.com \
--cc=thierry.reding@gmail.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