The em25xx/em276x/7x/8x provides 4 GPIO register sets,
each of them consisting of separate read and a write registers.
The same registers are also used by the em2874/174/84.
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
---
drivers/media/usb/em28xx/em28xx-cards.c | 88
- add definition for GPIO register 0x09 (reading/input)
- extend the information the chip variants that support GPIO registers 0x08/0x09
- rename EM28XX_R08_GPIO to EM2820_R08_GPIO_CTRL
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
---
drivers/media/usb/em28xx/em28xx-cards.c | 128
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
---
drivers/media/usb/em28xx/em28xx-input.c |1 -
drivers/media/usb/em28xx/em28xx-reg.h |3 ++-
2 Dateien geändert, 2 Zeilen hinzugefügt(+), 2 Zeilen entfernt(-)
diff --git a/drivers/media/usb/em28xx/em28xx-input.c
b/drivers
Am 03.06.2013 20:12, schrieb Frank Schäfer:
The first two patches add some missing GPIO register definitions,
while the third patch is a minor code movement to clean up things.
The fourth patch finally removes the GPIO register caching.
Frank Schäfer (4):
em28xx: extend GPIO register
em25xx/em276x/7x/8x provides 3 GPIO register sets,
each of them consisting of separate read and a write registers.
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
---
drivers/media/usb/em28xx/em28xx-reg.h | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/media/usb
we need to cache this register, too.
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
---
drivers/media/usb/em28xx/em28xx-cards.c | 12 -
drivers/media/usb/em28xx/em28xx-core.c | 43 ++---
drivers/media/usb/em28xx/em28xx.h | 15
3
Am 20.05.2013 01:04, schrieb Chris Rankin:
- Original Message -
What happens with kernel 3.8 ? Does ir-keytable trigger an
em28xx_ir_change_protocol() call there, too, but with type=8 ? Or is this
call missing ?
This is the dmesg output from 3.8, with an extra ex28xx_info() call at
Am 20.05.2013 02:45, schrieb Chris Rankin:
- Original Message -
I'm not familar with ir-keytable and the RC core.
Mauro ? Can you take over ? ;)
This patch seems to do the right thing... I doubt it will apply cleanly
because of TAB/space issues, but you should get the idea :-).
Am 20.05.2013 14:38, schrieb Frank Schäfer:
...
But there was a third change:
3.) the scancode passed to the RC core with rc_keypress() in case of
RC_BIT_UNKNOWN changed from a 16 bit value to 32 bit value (e.g.: old:
00 00 ab cd = new: ab cd xx xx).
See
commit
Am 20.05.2013 15:01, schrieb Chris Rankin:
- Original Message -
And this is me calling ir-keytable:
[ 2183.812407] em28xx #0: Changing protocol: rc_type=1
So with 3.8 the same happens as with 3.9.
Yes, that does appear to be part of the RC core ABI.
Well, if ir-keycode / the RC
Am 20.05.2013 16:51, schrieb Chris Rankin:
- Original Message -
If I had to guess, I would say you should check your rc_maps.cfg / keytable.
;)
This is unchanged between 3.8.x and 3.9.x, and so is correct by definition.
No, just because it didn't change it isn't automatically
Am 18.05.2013 23:02, schrieb Chris Rankin:
- Original Message -
For the em28xx driver: em28xx-input.c:
em28xx_ir_work() is called every 100ms
calls em28xx_ir_handle_key()
- calls ir-get_key() which is em2874_polling_getkey() in case of your
device
- reports the
Am 19.05.2013 16:11, schrieb Chris Rankin:
- Original Message -
em28xx_ir_change_protocol() should be called at least twice:
First from em28xx_ir_init() with RC_BIT_UNKNOWN (initial configuration)
and later from the RC core with RC_BIT_RC5.
Can you confirm that ?
Yes, it does
Am 19.05.2013 21:59, schrieb Chris Rankin:
- Original Message -
Hmm... that's weird. Are you sure about that ? Is this really a 3.9.2
vanilla kernel ?
Quite sure, although it turns out that there's a bit more to it. Here is the
dmesg output with my debugging messages in:
[
Am 18.05.2013 15:57, schrieb Chris Rankin:
I have a PCTV 290e DVB2 adapter (em28xx, em28xx_dvb, em28xx_rc, cxd2820r), and
I have just discovered that the IR remote control has stopped working with VDR
when using a vanilla 3.9.2 kernel. Downgrading the kernel to 3.8.12 fixes
things again.
Am 18.05.2013 17:17, schrieb Chris Rankin:
- Original Message -
Am 18.05.2013 15:57, schrieb Chris Rankin:
I have a PCTV 290e DVB2 adapter (em28xx, em28xx_dvb, em28xx_rc, cxd2820r), and
I have just discovered that the IR remote control has stopped working with VDR
when using a
(forwarding to the linux-media mailing list) (2nd try)
Am 18.04.2013 21:04, schrieb Michael .:
Hi
I hope you don't mind me contacting you directly.
Issues like this should always be discussed on the linux-media mailing
list, so please CC it in the future.
Neither I'm the em28xx maintainer
...
Am 13.04.2013 20:08, schrieb Mauro Carvalho Chehab:
Writing is sane: GPIO input lines requires writing as well, in order to
set it to either pull-up or pull-down mode (not sure if em28xx supports
both ways).
So, the driver needs to know if it will write there a 0 or 1, and this is
commit 61ff5d69 em28xx: improve em2710/em2820 distinction missed the
le16_to_cpu conversion of the USB vendor ID.
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
---
drivers/media/usb/em28xx/em28xx-cards.c |3 ++-
1 Datei geändert, 2 Zeilen hinzugefügt(+), 1 Zeile entfernt(-)
diff
Am 15.04.2013 14:51, schrieb Mauro Carvalho Chehab:
Em Sun, 14 Apr 2013 22:35:05 +0200
Frank Schäfer fschaefer@googlemail.com escreveu:
Am 13.04.2013 20:08, schrieb Mauro Carvalho Chehab:
Em Sat, 13 Apr 2013 19:46:20 +0200
Frank Schäfer fschaefer@googlemail.com escreveu:
Am
Am 15.04.2013 17:23, schrieb Patchwork:
Hello,
The following patch (submitted by you) has been updated in patchwork:
* em28xx: add basic support for the SpeedLink Vicious And Devine Laplace
webcam
- http://patchwork.linuxtv.org/patch/17928/
was: New
now: Under Review
This
I've just noticed that my 2 pending em28xx patches have got delegate
assigned:
https://patchwork.linuxtv.org/patch/17834/
= delegated to mkrufky
https://patchwork.linuxtv.org/patch/17928/ (Obsoleted)
= delegated to hverkuil
Ist this a patchwork failure or is the new submaintainers workflow
Am 15.04.2013 18:50, schrieb Mauro Carvalho Chehab:
Em Mon, 15 Apr 2013 18:41:44 +0200
Frank Schäfer fschaefer@googlemail.com escreveu:
I've just noticed that my 2 pending em28xx patches have got delegate
assigned:
https://patchwork.linuxtv.org/patch/17834/
= delegated to mkrufky
Am 13.04.2013 20:08, schrieb Mauro Carvalho Chehab:
Em Sat, 13 Apr 2013 19:46:20 +0200
Frank Schäfer fschaefer@googlemail.com escreveu:
Am 13.04.2013 19:04, schrieb Mauro Carvalho Chehab:
Em Sat, 13 Apr 2013 17:33:28 +0200
Frank Schäfer fschaefer@googlemail.com escreveu:
Am
Am 14.04.2013 20:32, schrieb Mauro Carvalho Chehab:
Now that dvb-only devices start to happen, it makes sense
to split the analog part on a separate module.
Signed-off-by: Mauro Carvalho Chehab mche...@redhat.com
---
This was compiled-tested only, and it is not ready yet for merging.
Yes,
Patch 1 removes the unneeded and broken gpio register caching code.
Patch 2 adds the gpio register defintions for the em25xx/em276x/7x/8x
and patch 3 finally adds a new helper function for gpio ports with separate
registers for read and write access.
Frank Schäfer (3):
em28xx: give up GPIO
em25xx/em276x/7x/8x provides 3 GPIO register sets,
each of them consisting of separate read and a write registers.
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
---
drivers/media/usb/em28xx/em28xx-reg.h |8
1 Datei geändert, 8 Zeilen hinzugefügt(+)
diff --git a/drivers
where input lines are
connected to buttons etc.
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
---
drivers/media/usb/em28xx/em28xx-cards.c | 12
drivers/media/usb/em28xx/em28xx-core.c | 27 ++-
drivers/media/usb/em28xx/em28xx.h |6
).
Make em28xx_write_reg_bits() a wrapper function calling this new function with
the same value for both registers.
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
---
drivers/media/usb/em28xx/em28xx-core.c | 26 +++---
drivers/media/usb/em28xx/em28xx.h |5
- support for the 3 buttons (snapshot, mute, illumination) is missing
- illumination/flash LED support is missing (capturing LED is functional)
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
---
drivers/media/usb/em28xx/em28xx-cards.c | 34 ++-
drivers/media/usb
Am 13.04.2013 16:25, schrieb Mauro Carvalho Chehab:
Em Sat, 13 Apr 2013 16:15:39 +0300
Antti Palosaari cr...@iki.fi escreveu:
On 04/13/2013 12:48 PM, Frank Schäfer wrote:
Patch 1 removes the unneeded and broken gpio register caching code.
Patch 2 adds the gpio register defintions
Am 13.04.2013 16:41, schrieb Mauro Carvalho Chehab:
Em Sat, 13 Apr 2013 11:48:39 +0200
Frank Schäfer fschaefer@googlemail.com escreveu:
The GPIO register tracking/caching code is partially broken, because newer
devices provide more than one GPIO register and some of them are even using
Am 13.04.2013 19:04, schrieb Mauro Carvalho Chehab:
Em Sat, 13 Apr 2013 17:33:28 +0200
Frank Schäfer fschaefer@googlemail.com escreveu:
Am 13.04.2013 16:41, schrieb Mauro Carvalho Chehab:
Em Sat, 13 Apr 2013 11:48:39 +0200
Frank Schäfer fschaefer@googlemail.com escreveu:
The GPIO
Am 13.04.2013 19:46, schrieb Frank Schäfer:
Am 13.04.2013 19:04, schrieb Mauro Carvalho Chehab:
Em Sat, 13 Apr 2013 17:33:28 +0200
Frank Schäfer fschaefer@googlemail.com escreveu:
Am 13.04.2013 16:41, schrieb Mauro Carvalho Chehab:
Em Sat, 13 Apr 2013 11:48:39 +0200
Frank Schäfer
Am 13.04.2013 20:19, schrieb Frank Schäfer:
Am 13.04.2013 19:46, schrieb Frank Schäfer:
...
We always write to the GPIO register. That's why these functions are
called em28xx_write_* ;)
Whether the write operation is sane or not (e.g. because it modifies the
bit corresponding to an input
The snapshot button support is currently broken, because module em28xx-rc is
loaded only if the device has remote control support.
Fix it by also loading this module if the device has a snapshot button.
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
---
drivers/media/usb/em28xx/em28xx
.
Fortunately both variants are using different generic USD IDs which give us a
hint about the used chip.
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
---
drivers/media/usb/em28xx/em28xx-cards.c | 16
1 Datei geändert, 8 Zeilen hinzugefügt(+), 8 Zeilen entfernt(-)
diff --git
Am 08.04.2013 10:38, schrieb Hans Verkuil:
On Mon April 8 2013 00:02:15 Frank Schäfer wrote:
In em28xx_start_streaming() and also em28xx_stop_streaming() we do
struct em28xx *dev = dvb-adapter.priv;
which I would say should be the culprit.
Are you sure that dvb-adapter.priv needs
as indicator that the device provides DVB support.
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
---
drivers/media/usb/em28xx/em28xx-cards.c |2 +-
1 Datei geändert, 1 Zeile hinzugefügt(+), 1 Zeile entfernt(-)
diff --git a/drivers/media/usb/em28xx/em28xx-cards.c
b/drivers/media/usb
Am 06.04.2013 08:38, schrieb Hans Verkuil:
On Fri April 5 2013 18:11:59 Frank Schäfer wrote:
Mauro, Hans,
with the latest media-tree, I'm getting the following kernel oops when
starting to watch digital TV with em28xx devices:
[ 124.297707] BUG: unable to handle kernel paging request
Am 03.04.2013 10:27, schrieb Timo Teras:
On Tue, 02 Apr 2013 18:39:25 +0200
Frank Schäfer fschaefer@googlemail.com wrote:
Am 02.04.2013 07:43, schrieb Timo Teras:
On Mon, 01 Apr 2013 19:26:53 +0200
Frank Schäfer fschaefer@googlemail.com wrote:
Am 30.03.2013 10:54, schrieb Timo
Mauro, Hans,
with the latest media-tree, I'm getting the following kernel oops when
starting to watch digital TV with em28xx devices:
[ 124.297707] BUG: unable to handle kernel paging request at 38326f3d
[ 124.297770] IP: [f8bf1026] em28xx_tuner_callback+0x6/0x40 [em28xx]
[ 124.297825] *pdpt =
Am 02.04.2013 07:43, schrieb Timo Teras:
On Mon, 01 Apr 2013 19:26:53 +0200
Frank Schäfer fschaefer@googlemail.com wrote:
Am 30.03.2013 10:54, schrieb Timo Teras:
On Thu, 28 Mar 2013 12:22:52 -0300
Mauro Carvalho Chehab mche...@redhat.com wrote:
On the W7 driver, I don't get any
Am 02.04.2013 00:12, schrieb Mauro Carvalho Chehab:
Em Mon, 01 Apr 2013 22:39:28 +0200
Frank Schäfer fschaefer@googlemail.com escreveu:
Am 01.04.2013 21:22, schrieb Mauro Carvalho Chehab:
Em Mon, 01 Apr 2013 19:14:03 +0200
Frank Schäfer fschaefer@googlemail.com escreveu:
Am
Am 02.04.2013 02:48, schrieb Devin Heitmueller:
On Mon, Apr 1, 2013 at 6:14 PM, Mauro Carvalho Chehab
mche...@redhat.com wrote:
In time, I meant to say:
So, it seems very unlikely that any change here will keep it
working for
model 16009 while breaking it for other HVR-930
Am 18.03.2013 22:22, schrieb Mauro Carvalho Chehab:
Em Wed, 06 Mar 2013 18:44:07 +0100
Frank Schäfer fschaefer@googlemail.com escreveu:
Am 05.03.2013 16:43, schrieb Devin Heitmueller:
2013/3/5 Mauro Carvalho Chehab mche...@redhat.com:
The em2874 chips and upper have 2 buses. On all known
Am 30.03.2013 10:54, schrieb Timo Teras:
On Thu, 28 Mar 2013 12:22:52 -0300
Mauro Carvalho Chehab mche...@redhat.com wrote:
On the W7 driver, I don't get any of the above mentioned problems.
I looked at the saa7113 register init sequence, and copied that
over to linux saa7113 init, but that
Am 01.04.2013 21:22, schrieb Mauro Carvalho Chehab:
Em Mon, 01 Apr 2013 19:14:03 +0200
Frank Schäfer fschaefer@googlemail.com escreveu:
Am 18.03.2013 22:22, schrieb Mauro Carvalho Chehab:
Em Wed, 06 Mar 2013 18:44:07 +0100
Frank Schäfer fschaefer@googlemail.com escreveu:
Am
-fmt.pix.height = height;
Acked-by: Frank Schäfer fschaefer@googlemail.com
Thanks for catching this !
Regards,
Frank
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org
Now that the board hints and the sensor initialization/configuration have been
separated, em28xx_detect_sensor() is the better name for this function.
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
---
drivers/media/usb/em28xx/em28xx-cards.c |7 +++
1 Datei geändert, 3 Zeilen
em28xx-cards.c is very large and the sensor/camera related code is growing,
so move this code to a separate source code file em28xx-camera.c.
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
---
drivers/media/usb/em28xx/Makefile|2 +-
drivers/media/usb/em28xx/em28xx-camera.c
Add further Micron chip IDs to be able to identify all Micron sensors listed
by Empiatech.
Also probe the two alternate i2c addresses used by Micron sensors with 8 bit
address and 16 bit register width.
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
---
drivers/media/usb/em28xx/em28xx
Other sensors like the ones from OmniVision need a different probing procedure,
so it makes sense have separate functions for each manufacturer/sensor type.
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
---
drivers/media/usb/em28xx/em28xx-camera.c | 23 +++
1
different
client addresses).
The most commonly used sensors (including the ones listed by Empiatech) are
detected properly, although there is no support for them yet.
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
---
drivers/media/usb/em28xx/em28xx-camera.c | 114
them properly, so leave a comment.
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
---
drivers/media/usb/em28xx/em28xx-camera.c |5 +
1 Datei geändert, 5 Zeilen hinzugefügt(+)
diff --git a/drivers/media/usb/em28xx/em28xx-camera.c
b/drivers/media/usb/em28xx/em28xx-camera.c
changes), bridge xclk adjustment and disabling of 16 bit (12 bit) output formats
at high resolutions. Image quality should also needs to be improved.
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
---
drivers/media/usb/em28xx/em28xx-camera.c | 49 ++
drivers
Am 25.03.2013 18:08, schrieb Timo Teras:
I just bought a Terratec Grabby hardware revision 2 in hopes that it
would work on my linux box.
But alas, I got only sound working. It seems that analog video picture
grabbing does not work.
I tried kernels 3.4.34-grsec, 3.7.1 (vanilla), 3.8.2-grsec
-by: Frank Schäfer fschaefer@googlemail.com
Cc: sta...@kernel.org
---
drivers/media/usb/em28xx/em28xx-cards.c |9 -
1 Datei geändert, 8 Zeilen hinzugefügt(+), 1 Zeile entfernt(-)
diff --git a/drivers/media/usb/em28xx/em28xx-cards.c
b/drivers/media/usb/em28xx/em28xx-cards.c
index 54e0362
Am 27.03.2013 19:04, schrieb Timo Teras:
On Wed, 27 Mar 2013 19:57:49 +0200
Timo Teras timo.te...@iki.fi wrote:
The errors are weird. strace gives:
open(/dev/bus/usb/005/028, O_RDONLY) = -1 ENOENT (No such file or
directory) open(/dev/bus/usb/005/028, O_RDONLY) = -1 ENOENT (No
such file
and identification (patches 5, 7 and 8)
- adding (basic) support for the OmniVision OV2640 sensor (patch 9)
Frank Schäfer (9):
em28xx: fix and separate the board hints for sensor devices
em28xx: separate sensor detection and initialization/configuration
em28xx: rename em28xx_hint_sensor
and EM2860_BOARD_NETGMBH_CAM (using the module
parameter card).
NOTE: the current board hint logic for webcams is preserved. Not more not less.
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
---
drivers/media/usb/em28xx/em28xx-cards.c | 40 +++
1 Datei
and future proof.
This also makes the code more consistent, because the initialization of the
MT9V011 sensor subdevice is already separated.
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
---
drivers/media/usb/em28xx/em28xx-cards.c | 122 ++-
1 Datei geändert, 72
on the recent em28xx i2c bus changes (real support for 2 busses)
- moved i2c algorithm depending transfer function calls to separate functions
Changes since v2:
- fixed some coding style issues and comments
Frank Schäfer (5):
em28xx: add support for em25xx i2c bus B read/write/check device
This chip can be found in the SpeedLink VAD Laplace webcam (1ae7:9003 and
1ae7:9004).
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
---
drivers/media/usb/em28xx/em28xx-cards.c | 13 -
drivers/media/usb/em28xx/em28xx-reg.h |1 +
drivers/media/usb/em28xx/em28xx.h
Streaming doesn't work with the EM2765 if bit 5 of the output format register
0x27 is set.
It's actually not clear if really has to be set for the other chips, but for
now let's keep it to avoid regressions and add a comment to the code.
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
The Windows driver writes the output resolution to registers 0x34 (width / 16)
and 0x35 (height / 16) always.
We don't know yet what these registers are used for.
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
---
drivers/media/usb/em28xx/em28xx-core.c |7 +++
drivers/media
-by: Frank Schäfer fschaefer@googlemail.com
---
drivers/media/usb/em28xx/em28xx-cards.c |8 +-
drivers/media/usb/em28xx/em28xx-i2c.c | 236 ++-
drivers/media/usb/em28xx/em28xx.h | 10 +-
3 Dateien geändert, 212 Zeilen hinzugefügt(+), 42 Zeilen entfernt
The em25xx/em276x/em277x/em278x frame data format is different to the one used
by the em2710/em2750/em28xx chips.
With the recent cleanups and reorganization of the frame data processing code it
can be easily extended to support these devices.
Signed-off-by: Frank Schäfer fschaefer
Am 24.03.2013 12:38, schrieb Mauro Carvalho Chehab:
Em Sat, 23 Mar 2013 18:27:08 +0100
Frank Schäfer fschaefer@googlemail.com escreveu:
The webcam SpeedLink VAD Laplace (em2765 + ov2640) uses a special algorithm
for i2c communication with the sensor, which is connected to a second i2c
Am 24.03.2013 12:44, schrieb Mauro Carvalho Chehab:
Em Sat, 23 Mar 2013 18:27:12 +0100
Frank Schäfer fschaefer@googlemail.com escreveu:
The Windows driver writes the output resolution to registers 0x34 (width /
16)
and 0x35 (height / 16) always.
We don't know yet what these registers
/checkpatch.pl complains for this patch:
WARNING: please, no spaces at the start of a line
#69: FILE: drivers/media/usb/em28xx/em28xx-i2c.c:8:
+ Copyright (C) 2013 Frank Schäfer fschaefer@googlemail.com$
WARNING: space prohibited between function name and open parenthesis '('
#69: FILE: drivers
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
---
drivers/media/usb/em28xx/em28xx-i2c.c | 45 +++--
1 Datei geändert, 20 Zeilen hinzugefügt(+), 25 Zeilen entfernt(-)
diff --git a/drivers/media/usb/em28xx/em28xx-i2c.c
b/drivers/media/usb/em28xx/em28xx
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
---
drivers/media/usb/em28xx/em28xx-i2c.c | 52 +
1 Datei geändert, 34 Zeilen hinzugefügt(+), 18 Zeilen entfernt(-)
diff --git a/drivers/media/usb/em28xx/em28xx-i2c.c
b/drivers/media/usb/em28xx/em28xx
Am 24.03.2013 15:02, schrieb Mauro Carvalho Chehab:
Em Sun, 24 Mar 2013 13:53:40 +0100
Frank Schäfer fschaefer@googlemail.com escreveu:
Am 24.03.2013 12:38, schrieb Mauro Carvalho Chehab:
Em Sat, 23 Mar 2013 18:27:08 +0100
Frank Schäfer fschaefer@googlemail.com escreveu:
The webcam
on the recent em28xx i2c bus changes (real support for 2 busses)
- moved i2c algorithm depending transfer function calls to separate functions
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
This chip can be found in the SpeedLink VAD Laplace webcam (1ae7:9003 and
1ae7:9004).
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
---
drivers/media/usb/em28xx/em28xx-cards.c | 11 ++-
drivers/media/usb/em28xx/em28xx-reg.h |1 +
drivers/media/usb/em28xx/em28xx.h
-by: Frank Schäfer fschaefer@googlemail.com
---
drivers/media/usb/em28xx/em28xx-cards.c |8 +-
drivers/media/usb/em28xx/em28xx-i2c.c | 229 +--
drivers/media/usb/em28xx/em28xx.h | 10 +-
3 Dateien geändert, 205 Zeilen hinzugefügt(+), 42 Zeilen entfernt
Streaming doesn't work with the EM2765 if bit 5 of the output format register
0x27 is set.
It's actually not clear if really has to be set for the other chips, but for
now let's keep it to avoid regressions and add a comment to the code.
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
The em25xx/em276x/em277x/em278x frame data format is different to the one used
by the em2710/em2750/em28xx chips.
With the recent cleanups and reorganization of the frame data processing code it
can be easily extended to support these devices.
Signed-off-by: Frank Schäfer fschaefer
The Windows driver writes the output resolution to registers 0x34 (width / 16)
and 0x35 (height / 16) always.
We don't know yet what these registers are used for.
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
---
drivers/media/usb/em28xx/em28xx-core.c |7 +++
drivers/media
Am 21.03.2013 11:56, schrieb Hans Verkuil:
On Wed 20 March 2013 20:24:49 Frank Schäfer wrote:
Instead of applying the current mute setting on last device node close,
always
mute the device.
I am very pleased with the preceding 8 patches. That does exactly what I had
in mind. For this patch
This patch series refactors function audio_mux() and fixes several issues
related to muting/unmuting on probing and first open.
Mute on last close will be fixed with further patches which are currently under
review.
Tested with a Hauppauge WinTV Theatre (model 37284, Rev B421).
Frank Schäfer
Function audio_mux() actually deals with two types of mute: gpio mute and
subdevice muting.
This patch claryfies the meaning of these values, but mainly prepares the code
for
the next patch.
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
Acked-by: Hans Verkuil hans.verk...@cisco.com
We can't and do not save the mute setting in function audio_mux(), so we
should also not save the input in this function for consistency.
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
Acked-by: Hans Verkuil hans.verk...@cisco.com
---
drivers/media/pci/bt8xx/bttv-driver.c | 10
'audio_input' better describes the meaning of this field.
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
Acked-by: Hans Verkuil hans.verk...@cisco.com
---
drivers/media/pci/bt8xx/bttv-cards.c |2 +-
drivers/media/pci/bt8xx/bttv-driver.c | 12 ++--
drivers/media/pci
There are cases where we want to call audio_mux() without changing the value of
the v4l2 mute control, for example
- mute mute on last close
- mute on device probing
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
Acked-by: Hans Verkuil hans.verk...@cisco.com
---
drivers/media/pci
Split function audio_mux():
move the mute setting part to function audio_mute() and the input setting part
to function audio_input().
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
Acked-by: Hans Verkuil hans.verk...@cisco.com
---
drivers/media/pci/bt8xx/bttv-driver.c | 51
().
Also apply the mute setting when the radio device node gets opened.
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
Acked-by: Hans Verkuil hans.verk...@cisco.com
---
drivers/media/pci/bt8xx/bttv-driver.c |3 ++-
1 Datei geändert, 2 Zeilen hinzugefügt(+), 1 Zeile entfernt(-)
diff --git
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
Acked-by: Hans Verkuil hans.verk...@cisco.com
---
drivers/media/pci/bt8xx/bttv-driver.c |4 +++-
1 Datei geändert, 3 Zeilen hinzugefügt(+), 1 Zeile entfernt(-)
diff --git a/drivers/media/pci/bt8xx/bttv-driver.c
b/drivers/media/pci
Move the GPIO part of function audio_mux() to a separate function
audio_mux_gpio().
This prepares the code for the next patch which will separate mute and input
setting.
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
Acked-by: Hans Verkuil hans.verk...@cisco.com
---
drivers/media/pci
...
Kernel: arch/x86/boot/bzImage is ready (#2)
ERROR: __divdi3 [drivers/media/common/siano/smsdvb.ko] undefined!
make[1]: *** [__modpost] Fehler 1
make: *** [modules] Fehler 2
Mauro, I assume this is caused by one of the recent Siano patches ?
Regards,
Frank
--
To unsubscribe from this list:
Am 21.03.2013 16:34, schrieb Hans Verkuil:
On Thu March 21 2013 11:03:27 Mauro Carvalho Chehab wrote:
Em Thu, 21 Mar 2013 09:33:41 +0100
Hans Verkuil hverk...@xs4all.nl escreveu:
I tried to use my HVR 900 stick today and discovered that it no longer
worked.
I traced it to commit
,
the new patches 3-6 untagle the mute and input setting code as much as possible
as suggested by hans Verkuil.
Tested with a Hauppauge WinTV Theatre (model 37284, Rev B421).
Frank Schäfer (10):
bttv: audio_mux(): use a local variable gpio_mute instead of
modifying the function parameter mute
Function audio_mux() actually deals with two types of mute: gpio mute and
subdevice muting.
This patch claryfies the meaning of these values, but mainly prepares the code
for
the next patch.
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
---
drivers/media/pci/bt8xx/bttv-driver.c
We can't and do not save the mute setting in function audio_mux(), so we
should also not save the input in this function for consistency.
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
---
drivers/media/pci/bt8xx/bttv-driver.c | 10 +-
1 Datei geändert, 5 Zeilen hinzugefügt
There are cases where we want to call audio_mux() without changing the value of
the v4l2 mute control, for example
- mute mute on last close
- mute on device probing
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
---
drivers/media/pci/bt8xx/bttv-driver.c |8
1 Datei
Move the GPIO part of function audio_mux() to a separate function
audio_mux_gpio().
This prepares the code for the next patch which will separate mute and input
setting.
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
---
drivers/media/pci/bt8xx/bttv-driver.c | 18
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
---
drivers/media/pci/bt8xx/bttv-driver.c |4 +++-
1 Datei geändert, 3 Zeilen hinzugefügt(+), 1 Zeile entfernt(-)
diff --git a/drivers/media/pci/bt8xx/bttv-driver.c
b/drivers/media/pci/bt8xx/bttv-driver.c
index 0df4a16..55eab61
Instead of applying the current mute setting on last device node close, always
mute the device.
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
---
drivers/media/pci/bt8xx/bttv-driver.c |2 +-
1 Datei geändert, 1 Zeile hinzugefügt(+), 1 Zeile entfernt(-)
diff --git a/drivers/media
'audio_input' better describes the meaning of this field.
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
---
drivers/media/pci/bt8xx/bttv-cards.c |2 +-
drivers/media/pci/bt8xx/bttv-driver.c | 12 ++--
drivers/media/pci/bt8xx/bttvp.h |2 +-
3 Dateien geändert
301 - 400 of 801 matches
Mail list logo
