From: Hans Verkuil <hansverk@cisco.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: "Aguirre, Sergio" <saaguirre@ti.com>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
Hans Verkuil <hverkuil@xs4all.nl>,
Sylwester Nawrocki <snjw23@gmail.com>,
Stan <svarbanov@mm-sol.com>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: [RFC/PATCH 0/1] New subdev sensor operation g_interface_parms
Date: Wed, 23 Feb 2011 17:28:39 +0100 [thread overview]
Message-ID: <201102231728.40075.hansverk@cisco.com> (raw)
In-Reply-To: <201102231714.41770.laurent.pinchart@ideasonboard.com>
On Wednesday, February 23, 2011 17:14:41 Laurent Pinchart wrote:
> On Wednesday 23 February 2011 17:02:57 Hans Verkuil wrote:
> > On Wednesday, February 23, 2011 16:30:42 Laurent Pinchart wrote:
> > > On Wednesday 23 February 2011 15:06:49 Aguirre, Sergio wrote:
> > > > <snip>
> > > >
> > > > > > The only static data I am concerned about are those that affect
> > > > > > signal integrity.
> > > > > >
> > > > > > After thinking carefully about this I realized that there is
really
> > > > > > only one setting that is relevant to that: the sampling edge. The
> > > > > > polarities do not matter in this.
> > > >
> > > > I respectfully disagree.
> > >
> > > So do I. Sampling edge is related to polarities, so you need to take
both
> > > into account.
> >
> > When you switch polarity for data/field/hsync/vsync signals on a simple
bus
> > you just invert whether a 1 bit is output as high or low voltage. So you
> > just change the meaning of the bit. This does not matter for signal
> > integrity, since you obviously have to be able to sample both low and high
> > voltages. It is *when* you sample that can have a major effect.
>
> When you switch the polarity you will likely have to sample on the opposite
> edge. If, for signal integrity reasons, you can only sample on a given edge,
> you will want to use a fixed polarity and not negotiate it.
You are confusing clock polarity (which is relevant) with data, field, hsync
and vsync polarities which just invert the meaning of those pins.
I wish I had a whiteboard to draw it, much easier to explain that way.
>
> Given the very small number of parameters that are negotiated by soc-camera
at
> the moment, I'm very much in favour of hardcoding all of them in platform
data
> and just adding a g_interface_parms subdev operation.
Just for the record: I have no problem with hardcoding these polarities. After
all, that was my original idea. But they can be negotiated as well.
Regards,
Hans
>
> > This might be different for differential clocks. I have no experience with
> > this, so I can't say anything sensible about that.
>
> --
> Regards,
>
> Laurent Pinchart
>
>
next prev parent reply other threads:[~2011-02-23 16:27 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 10:31 [RFC/PATCH 0/1] New subdev sensor operation g_interface_parms Stanimir Varbanov
2011-02-22 10:31 ` [RFC/PATCH 1/1] v4l: Introduce sensor operation for getting interface configuration Stanimir Varbanov
2011-02-22 11:40 ` [RFC/PATCH 0/1] New subdev sensor operation g_interface_parms Guennadi Liakhovetski
2011-02-22 13:32 ` Hans Verkuil
2011-02-22 14:01 ` Aguirre, Sergio
2011-02-22 14:34 ` Guennadi Liakhovetski
2011-02-23 11:15 ` Laurent Pinchart
2011-02-22 14:11 ` Guennadi Liakhovetski
2011-02-22 15:17 ` Hans Verkuil
2011-02-22 15:30 ` Guennadi Liakhovetski
2011-02-22 15:34 ` Stan
2011-02-22 16:27 ` Guennadi Liakhovetski
2011-02-22 17:00 ` Hans Verkuil
2011-02-22 17:08 ` Guennadi Liakhovetski
2011-02-23 11:34 ` Laurent Pinchart
2011-02-22 21:42 ` Sylwester Nawrocki
2011-02-23 8:10 ` Hans Verkuil
2011-02-23 9:31 ` Guennadi Liakhovetski
2011-02-23 14:06 ` Aguirre, Sergio
2011-02-23 14:17 ` Hans Verkuil
2011-02-23 14:46 ` Guennadi Liakhovetski
2011-02-23 15:30 ` Laurent Pinchart
2011-02-23 15:52 ` Guennadi Liakhovetski
2011-02-23 16:02 ` Hans Verkuil
2011-02-23 16:14 ` Laurent Pinchart
2011-02-23 16:20 ` Aguirre, Sergio
2011-02-23 16:46 ` Guennadi Liakhovetski
2011-02-23 17:45 ` Aguirre, Sergio
2011-02-24 9:45 ` Stanimir Varbanov
2011-02-23 16:28 ` Hans Verkuil [this message]
2011-02-23 16:35 ` Laurent Pinchart
2011-02-23 16:37 ` Laurent Pinchart
2011-02-23 16:40 ` Guennadi Liakhovetski
2011-02-25 18:23 ` Sakari Ailus
2011-02-26 12:50 ` Hans Verkuil
2011-02-26 13:14 ` Guennadi Liakhovetski
2011-02-26 13:39 ` Hans Verkuil
2011-02-26 14:03 ` Sylwester Nawrocki
2011-02-26 14:45 ` Laurent Pinchart
2011-02-23 9:31 ` Hans Verkuil
2011-02-23 15:06 ` Aguirre, Sergio
2011-02-23 11:04 ` 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=201102231728.40075.hansverk@cisco.com \
--to=hansverk@cisco.com \
--cc=g.liakhovetski@gmx.de \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=saaguirre@ti.com \
--cc=snjw23@gmail.com \
--cc=svarbanov@mm-sol.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