From: "Daniel Glöckner" <dg@emlix.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>,
Chris Zankel <chris@zankel.net>,
linux-media@vger.kernel.org
Subject: Re: [patch 5/5] saa7121 driver for s6000 data port
Date: Mon, 30 Mar 2009 14:12:10 +0200 [thread overview]
Message-ID: <49D0B71A.5080801@emlix.com> (raw)
In-Reply-To: <200903301203.02327.hverkuil@xs4all.nl>
On 03/30/2009 12:03 PM, Hans Verkuil wrote:
> What exactly do you need? If there is something missing, then it should be
> added. But my guess is that you can pass such information via the s_routing
> callback. That's what all other drivers that use v4l2_subdev do.
The s_routing callback looks very limited. One can pass only two u32 values.
The parameters that have to be negotiated are:
- What is the on-wire video format?
- how many data lines are connected?
- synchronization using embedded SAV/EAV codes or using dedicated pins?
- polarity of sync lines?
- valid CRC and line number in digital blanking?
- what is the layout of the digital image?
- how many odd lines are there? how many even? (including blanking)
- how many horizontal pixels? (incl. blanking)
- where is the active region?
- on which pixels/lines do we start/end horizontal/vertical sync?
>> It seems the soc-camera framework is a better choice here, but to make it
>> work with the saa7121 one would first have to implement support for video
>> output.
>
> This framework will also be converted to use v4l2_subdev for the
> communication with i2c drivers.
So it shouldn't matter which one I chose?
> Actually, I recommend that you first look at the existing saa7127.c source.
> I don't know how many differences there are between the saa7121 and
> saa7127, but perhaps support for the saa7121 can be added there rather than
> introducing a new driver. Of course, that only works if the differences are
> not too big.
The chips appear to be very similar, sharing most of the registers. However, the
aforementioned problem still exists with this driver. A driver connecting this
sub device must know beforehand that it has to send standard BT.656 video frames
with SAV/EAV codes.
Daniel
--
Dipl.-Math. Daniel Glöckner, emlix GmbH, http://www.emlix.com
Fon +49 551 30664-0, Fax -11, Bahnhofsallee 1b, 37081 Göttingen, Germany
Geschäftsführung: Dr. Uwe Kracke, Dr. Cord Seele, Ust-IdNr.: DE 205 198 055
Sitz der Gesellschaft: Göttingen, Amtsgericht Göttingen HR B 3160
emlix - your embedded linux partner
next prev parent reply other threads:[~2009-03-30 12:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 15:08 [patch 5/5] saa7121 driver for s6000 data port Hans Verkuil
2009-03-30 9:56 ` Daniel Glöckner
2009-03-30 10:03 ` Hans Verkuil
2009-03-30 12:12 ` Daniel Glöckner [this message]
2009-03-30 12:50 ` Hans Verkuil
2009-03-30 13:36 ` Daniel Glöckner
2009-03-30 13:41 ` Hans Verkuil
-- strict thread matches above, loose matches on Subject: below --
2009-03-26 14:36 [patch 1/5] s6000 data port driver Daniel Glöckner
2009-03-26 14:36 ` [patch 5/5] saa7121 driver for s6000 data port Daniel Glöckner
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=49D0B71A.5080801@emlix.com \
--to=dg@emlix.com \
--cc=chris@zankel.net \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.