From: Hans Verkuil <hansverk@cisco.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Sylwester Nawrocki <snjw23@gmail.com>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
Stan <svarbanov@mm-sol.com>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
saaguirre@ti.com
Subject: Re: [RFC/PATCH 0/1] New subdev sensor operation g_interface_parms
Date: Wed, 23 Feb 2011 10:31:34 +0100 [thread overview]
Message-ID: <201102231031.34362.hansverk@cisco.com> (raw)
In-Reply-To: <201102230910.43069.hverkuil@xs4all.nl>
On Wednesday, February 23, 2011 09:10:42 Hans Verkuil wrote:
> Unfortunately, if a subdev is set to 'sample at rising edge', then that does
> not necessarily mean that the host should sample at the same edge. Depending
> on the clock line routing and the integrity of the clock signal the host may
> actually have to sample on the other edge. And yes, I've seen this.
It might be useful to give some background information regarding the sampling
edge problems.
There are two main reasons why the sampling edge can be hardware dependent.
The first is if the data lines go through an amplifier or something similar
that will slightly delay the data lines compared to the clock signal. This can
shift the edge at which you have to sample.
Actually, this may even be dependent on the clock frequency. I have not seen
that in real life yet, but it might happen. This will complicate things even
more since in that case you need to make a callback function in the board code
that determines the sampling edge based on the clock frequency. I think we can
ignore that for now, but we do need to keep it in mind.
The other is the waveform of the clock. For relatively low frequencies this
will resemble a symmetrical square wave. But for higher frequencies this more
resembles the bottom waveform in this picture:
http://myweb.msoe.edu/williamstm/Images/Divider2.jpg
This is asymmetric so depending on the slopes the sampling edge can make quite
a difference.
The higher the clock frequency, the more asymmetric the waveform will look.
Regards,
Hans
next prev parent reply other threads:[~2011-02-23 9:30 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
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 [this message]
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=201102231031.34362.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