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 v2 00/11] em28xx: i2c debugging cleanups and support for newer eeproms
Date: Sun, 3 Mar 2013 20:37:33 +0100 [thread overview]
Message-ID: <1362339464-3373-1-git-send-email-fschaefer.oss@googlemail.com> (raw)
The first 3 patches clean up / simplify the debugging and info messages a bit.
Patches 4, 5 and 6 fix two bugs I've noticed while working on the eeprom stuff.
Patches 7-10 add support for the newer eeproms with 16 bit address width.
This allows us to display the eeprom content, to calculate the eeprom hash for
board hints for devices with generic USB IDs, to read the device configuration
and to use tveeprom for Hauppauge devices just as with the old eeprom type.
The used eeprom type depends on the chip type/id (confirmed by the Empia datasheets).
For unknown chips, the old 8 bit eeprom type is assumed, which makes sure that the
eeprom content can't be damaged accidentally.
In video capturing/TV/DVB devices, the new eeprom still has the old eeprom content
(device configuration + tveeprom structure for Hauppauge devices) embedded.
Camera devices (em25xx, em276x+) however are using a different data structure,
which isn't supported yet.
Patch 11 is a follow-up which enables tveeprom for the Hauppauge HVR-930C
All patches have been tested with the following devices:
- Hauppauge HVR-900 (normal 8 bit eeprom)
- Hauppauge HVR-930C (16 bit eeprom, tveeprom)
- SpeedLink VAD Laplace webcam (16 bit eeprom, no device config dataset)
I also checked the USB log of the MSI Digivox ATSC which confirms that
non-Hauppauge devices are using the same eeprom format.
Changes since v1:
- fixed the sanity check in patch 8
- fixed a minor output format issue in patch 10
Frank Schäfer (11):
em28xx-i2c: replace printk() with the corresponding em28xx macros
em28xx-i2c: get rid of the dprintk2 macro
em28xx-i2c: also print debug messages at debug level 1
em28xx: do not interpret eeprom content if eeprom key is invalid
em28xx: fix eeprom data endianess
em28xx: make sure we are at i2c bus A when calling
em28xx_i2c_register()
em28xx: add basic support for eeproms with 16 bit address width
em28xx: add helper function for reading data blocks from i2c clients
em28xx: do not store eeprom content permanently
em28xx: extract the device configuration dataset from eeproms with 16
bit address width
em28xx: enable tveeprom for device Hauppauge HVR-930C
drivers/media/usb/em28xx/em28xx-cards.c | 45 +++--
drivers/media/usb/em28xx/em28xx-i2c.c | 284 ++++++++++++++++++++-----------
drivers/media/usb/em28xx/em28xx.h | 17 +-
3 Dateien geändert, 225 Zeilen hinzugefügt(+), 121 Zeilen entfernt(-)
--
1.7.10.4
next reply other threads:[~2013-03-03 19:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-03 19:37 Frank Schäfer [this message]
2013-03-03 19:37 ` [PATCH v2 01/11] em28xx-i2c: replace printk() with the corresponding em28xx macros Frank Schäfer
2013-03-04 18:09 ` Mauro Carvalho Chehab
2013-03-04 18:27 ` Frank Schäfer
2013-03-04 18:46 ` Mauro Carvalho Chehab
2013-03-03 19:37 ` [PATCH v2 02/11] em28xx-i2c: get rid of the dprintk2 macro Frank Schäfer
2013-03-03 19:37 ` [PATCH v2 03/11] em28xx-i2c: also print debug messages at debug level 1 Frank Schäfer
2013-03-03 19:37 ` [PATCH v2 04/11] em28xx: do not interpret eeprom content if eeprom key is invalid Frank Schäfer
2013-03-03 19:37 ` [PATCH v2 05/11] em28xx: fix eeprom data endianess Frank Schäfer
2013-03-03 19:37 ` [PATCH v2 06/11] em28xx: make sure we are at i2c bus A when calling em28xx_i2c_register() Frank Schäfer
2013-03-04 19:14 ` Mauro Carvalho Chehab
2013-03-04 21:24 ` Frank Schäfer
2013-03-05 2:31 ` Mauro Carvalho Chehab
2013-03-03 19:37 ` [PATCH v2 07/11] em28xx: add basic support for eeproms with 16 bit address width Frank Schäfer
2013-03-03 19:37 ` [PATCH v2 08/11] em28xx: add helper function for reading data blocks from i2c clients Frank Schäfer
2013-03-03 19:37 ` [PATCH v2 09/11] em28xx: do not store eeprom content permanently Frank Schäfer
2013-03-03 19:37 ` [PATCH v2 10/11] em28xx: extract the device configuration dataset from eeproms with 16 bit address width Frank Schäfer
2013-03-03 19:37 ` [PATCH v2 11/11] em28xx: enable tveeprom for device Hauppauge HVR-930C 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=1362339464-3373-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).