Linux Media Controller development
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@iki.fi>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-media@vger.kernel.org
Subject: Re: [RFC 3/4] omap3isp: Configure CSI-2 phy based on platform data
Date: Mon, 19 Dec 2011 09:17:23 +0200	[thread overview]
Message-ID: <20111219071723.GL3677@valkosipuli.localdomain> (raw)
In-Reply-To: <201112190131.10973.laurent.pinchart@ideasonboard.com>

Hi Laurent,

On Mon, Dec 19, 2011 at 01:31:09AM +0100, Laurent Pinchart wrote:
> On Thursday 15 December 2011 22:50:33 Sakari Ailus wrote:
> > On Thu, Dec 15, 2011 at 01:54:52PM +0100, Laurent Pinchart wrote:
> > > On Thursday 15 December 2011 12:53:03 Sakari Ailus wrote:
> > > > On Thu, Dec 15, 2011 at 11:28:06AM +0100, Laurent Pinchart wrote:
> > > > > On Thursday 15 December 2011 10:50:34 Sakari Ailus wrote:
> > > > > > Configure CSI-2 phy based on platform data in the ISP driver rather
> > > > > > than in platform code.
> > > > > > 
> > > > > > Signed-off-by: Sakari Ailus <sakari.ailus@iki.fi>
> > > 
> > > [snip]
> > > 
> > > > > > diff --git a/drivers/media/video/omap3isp/ispcsiphy.c
> > > > > > b/drivers/media/video/omap3isp/ispcsiphy.c index 5be37ce..52af308
> > > > > > 100644 --- a/drivers/media/video/omap3isp/ispcsiphy.c
> > > > > > +++ b/drivers/media/video/omap3isp/ispcsiphy.c
> > > > > > @@ -28,6 +28,8 @@
> > > 
> > > [snip]
> > > 
> > > > > > +int omap3isp_csiphy_config(struct isp_device *isp,
> > > > > > +			   struct v4l2_subdev *csi2_subdev,
> > > > > > +			   struct v4l2_subdev *sensor,
> > > > > > +			   struct v4l2_mbus_framefmt *sensor_fmt)
> > > > > 
> > > > > The number of lanes can depend on the format. Wouldn't it be better
> > > > > to add a subdev operation to query the sensor for its bus
> > > > > configuration instead of relying on ISP platform data ?
> > > > 
> > > > In principle, yes. That's an interesting point; how this kind of
> > > > information would best be delivered?
> > > 
> > > There are two separate information that need to be delivered:
> > > 
> > > - how the lanes are connected on the board
> > > - which lanes are used by the sensor, and for what purpose
> > > 
> > > The first information must be supplied through platform data, either to
> > > the sensor driver or the OMAP3 ISP driver (or both). As the second
> > > information
> > 
> > Both, and both of them may require configuring it. I don't know sensors
> > that allow it, but the CSI-2 receiver is flexible in lane mapping.
> > 
> > > comes from the sensor, my idea was to provide the first to the sensor,
> > > and to query the sensor in the OMAP3 ISP driver for the full
> > > configuration.
> > 
> > In theory, at least, configurations with less lanes need to be specified
> > separately. There may be limitations on how the lanes can be used, say,
> > using two out of three lanes may require leaving a aparticular lane unused.
> 
> In theory, I fully agree. This brings additional complexity for use cases that 
> might never exist though. Do you think we need to support it from the very 
> beginning ?

I don't see need for it, at least not for the time being. Still we might
want to show the number of lanes to the user as a read-onlycontrol, but that
could wait as well IMO.

-- 
Sakari Ailus
e-mail: sakari.ailus@iki.fi	jabber/XMPP/Gmail: sailus@retiisi.org.uk

  reply	other threads:[~2011-12-19  7:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-15  9:50 [RFC 0/4] OMAP 3 ISP driver improvements Sakari Ailus
2011-12-15  9:50 ` [RFC 1/4] omap3isp: Implement validate_pipeline Sakari Ailus
2011-12-15 10:18   ` Laurent Pinchart
2011-12-15 11:53     ` Sakari Ailus
2011-12-15  9:50 ` [RFC 2/4] omap3isp: Add lane configuration to platform data Sakari Ailus
2011-12-15  9:50 ` [RFC 3/4] omap3isp: Configure CSI-2 phy based on " Sakari Ailus
2011-12-15 10:28   ` Laurent Pinchart
2011-12-15 11:53     ` Sakari Ailus
2011-12-15 12:54       ` Laurent Pinchart
2011-12-15 21:50         ` Sakari Ailus
2011-12-19  0:31           ` Laurent Pinchart
2011-12-19  7:17             ` Sakari Ailus [this message]
2011-12-19 10:21               ` query video dev node name using the V4L2 device driver name Zhu, Mingcheng
2011-12-19 10:31                 ` Laurent Pinchart
2011-12-19 18:09                   ` Zhu, Mingcheng
2011-12-21  0:34                     ` Laurent Pinchart
2011-12-15  9:50 ` [RFC 4/4] omap3isp: Use pixel clock from sensor media bus frameformat Sakari Ailus
2011-12-15 10:29   ` 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=20111219071723.GL3677@valkosipuli.localdomain \
    --to=sakari.ailus@iki.fi \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    /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