From: "Frank Schäfer" <fschaefer.oss@googlemail.com>
To: mchehab@redhat.com
Cc: linux-media@vger.kernel.org,
"Frank Schäfer" <fschaefer.oss@googlemail.com>
Subject: [PATCH 0/5] em28xx: add support for the em2765 bridge
Date: Sun, 3 Mar 2013 20:40:56 +0100 [thread overview]
Message-ID: <1362339661-3446-1-git-send-email-fschaefer.oss@googlemail.com> (raw)
This patch series adds basic support for the em25xx/276x/7x/8x camera bridges.
These devices differ from the em2710/2750 and em28xx bridges in several points:
1) a second i2c bus is provided which has to be accessed with a different
read/write algorithm (=> patch 1)
2) a different frame data format is used (=> patch 3)
3) additional output formats (e.g. mpeg) are provided. This patch series does
not (yet) add support for them, but it fixes the output format selection
for these bridges (the current code sets bit 5 of the output format register,
which has a different meaning for the other bridges and breaks capturing
with em25xx family sdevices). (=> patch 4)
4) registers 0x34+0x35 (VBI_START_H/V for em28xx devices) are used for a
different (unknown) purpose. This needs to be investigated further (could be
zooming, cropping, image statistics or AWB/AE window selection).
At normal operation, these registers are set to capturing (input)
width/height / 16. (=> patch 5)
Patch 2 add the chip id of the em2765 as found in the "SpeedLink Vicious And
Devine Laplace" webcam. The changes have also been tested with this device.
Frank Schäfer (5):
em28xx: add support for em25xx i2c bus B read/write/check device
operations
em28xx: add chip id of the em2765
em28xx: add support for em25xx/em276x/em277x/em278x frame data
processing
em28xx: make em28xx_set_outfmt() working with EM25xx family bridges
em28xx: write output frame resolution to regs 0x34+0x35 for em25xx
family bridges
drivers/media/usb/em28xx/em28xx-cards.c | 17 +++-
drivers/media/usb/em28xx/em28xx-core.c | 27 ++++-
drivers/media/usb/em28xx/em28xx-i2c.c | 164 +++++++++++++++++++++++++++----
drivers/media/usb/em28xx/em28xx-reg.h | 7 ++
drivers/media/usb/em28xx/em28xx-video.c | 72 +++++++++++++-
drivers/media/usb/em28xx/em28xx.h | 8 ++
6 Dateien geändert, 271 Zeilen hinzugefügt(+), 24 Zeilen entfernt(-)
--
1.7.10.4
next reply other threads:[~2013-03-03 19:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-03 19:40 Frank Schäfer [this message]
2013-03-03 19:40 ` [PATCH 1/5] em28xx: add support for em25xx i2c bus B read/write/check device operations Frank Schäfer
2013-03-04 20:20 ` Mauro Carvalho Chehab
2013-03-04 20:23 ` Mauro Carvalho Chehab
2013-03-04 21:31 ` Frank Schäfer
2013-03-04 21:35 ` Frank Schäfer
2013-03-03 19:40 ` [PATCH 2/5] em28xx: add chip id of the em2765 Frank Schäfer
2013-03-03 19:40 ` [PATCH 3/5] em28xx: add support for em25xx/em276x/em277x/em278x frame data processing Frank Schäfer
2013-03-03 19:41 ` [PATCH 4/5] em28xx: make em28xx_set_outfmt() working with EM25xx family bridges Frank Schäfer
2013-03-03 19:41 ` [PATCH 5/5] em28xx: write output frame resolution to regs 0x34+0x35 for em25xx " Frank Schäfer
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=1362339661-3446-1-git-send-email-fschaefer.oss@googlemail.com \
--to=fschaefer.oss@googlemail.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.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;
as well as URLs for NNTP newsgroup(s).