- 17 Jun, 2013 33 commits
-
-
Hans Verkuil authored
Signed-off-by:
Hans Verkuil <hans.verkuil@cisco.com> Cc: Fabio Belavenuto <belavenuto@gmail.com> Signed-off-by:
Mauro Carvalho Chehab <mchehab@redhat.com>
-
Hans Verkuil authored
Signed-off-by:
-
Hans Verkuil authored
Signed-off-by:
Sylwester Nawrocki <s.nawrocki@samsung.com> Signed-off-by:
-
Hans Verkuil authored
Signed-off-by:
-
Hans Verkuil authored
The framework documentation used the g_chip_ident op as an example. This op has been removed, so replace its use in the examples by the g_std op. Signed-off-by:
-
Hans Verkuil authored
- Remove the "On failure the structure remains unchanged." part since that isn't necessarily true. - Document the 'size' field. Signed-off-by:
-
Hans Verkuil authored
Ensure that the register is aligned to a dword, otherwise the range check could fail since it assumes dword alignment. Signed-off-by:
-
Hans Verkuil authored
Ensure that the register is aligned to a dword, otherwise the range check could fail since it assumes dword alignment. Signed-off-by:
-
Hans Verkuil authored
Signed-off-by:
Lad, Prabhakar <prabhakar.csengg@gmail.com> Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de> Signed-off-by:
-
Hans Verkuil authored
Register access to subdevices no longer needs bridge support for those ioctls. The v4l2 core handles that these days. Signed-off-by:
-
Hans Verkuil authored
Signed-off-by:
-
Hans Verkuil authored
Signed-off-by:
-
Hans Verkuil authored
The size field wasn't filled in. Signed-off-by:
-
Hans Verkuil authored
Prevent out-of-range register accesses. Signed-off-by:
-
Hans Verkuil authored
These are no longer needed: register access to subdevices no longer needs the bridge driver to forward them. Signed-off-by:
-
Hans Verkuil authored
Prevent out-of-range register accesses. Signed-off-by:
-
Hans Verkuil authored
Prevent reading out-of-range register values. Signed-off-by:
-
Hans Verkuil authored
Replace the V4L2_IDENT_ macros from v4l2-chip-ident.h with driver specific defines. Signed-off-by:
-
Hans Verkuil authored
This is no longer needed since the core now handles this through DBG_G_CHIP_INFO. Signed-off-by:
Laurent Pinchart <laurent.pinchart@ideasonboard.com> Acked-by:
-
Hans Verkuil authored
This is no longer needed since the core now handles this through DBG_G_CHIP_INFO. Signed-off-by:
-
Hans Verkuil authored
This is no longer needed since the core now handles this through DBG_G_CHIP_INFO. Signed-off-by:
-
Hans Verkuil authored
This is no longer needed since the core now handles this through DBG_G_CHIP_INFO. Signed-off-by:
-
Hans Verkuil authored
This is no longer needed since the core now handles this through DBG_G_CHIP_INFO. Signed-off-by:
-
Hans Verkuil authored
Replace the V4L2_IDENT_* usage with tveeprom-specific defines. This header is deprecated, so those defines shouldn't be used anymore. The em28xx driver is the only one that uses the tveeprom audio_processor field, so that has been updated to use the new tveeprom AUDPROC define. Signed-off-by:
-
Hans Verkuil authored
Remove g_chip_ident. This driver used some of the V4L2_IDENT defines, replace those with a driver-specific enum. This makes it possible to drop the v4l2-chip-ident.h define as well. Signed-off-by:
-
Hans Verkuil authored
Remove g_chip_ident and replace it with g_chip_info. Signed-off-by:
-
Hans Verkuil authored
Remove g_chip_ident and replace it with g_chip_info. Signed-off-by:
-
Hans Verkuil authored
This op and the v4l2-chip-ident.h header are no longer needed. Signed-off-by:
-
Hans Verkuil authored
Replace g_chip_ident by g_chip_info. Note that the IR support is implemented as a subdev, so this part no longer needs to be handled as a 'bridge' chip. Signed-off-by:
-
Hans Verkuil authored
g_chip_ident was used to determine if a saa7114 or saa7115 was used. Instead just check the subdev name. After that the g_chip_ident function can be removed. Signed-off-by:
-
Hans Verkuil authored
The saa7115 driver used to show a 'chip found' message during probe. This was accidentally dropped during recent commits. Add it back as it is quite useful. Signed-off-by:
-
Hans Verkuil authored
The av-core is really a subdev, so there is no need anymore to act as if it is a 'second' bridge chip. As a result of this the g_chip_ident implementation can be completely dropped. Signed-off-by:
-
Hans Verkuil authored
VIDIOC_DBG_G_CHIP_IDENT has been replaced by VIDIOC_DBG_G_CHIP_INFO. Remove g_chip_ident support from bridge drivers since it is no longer needed. This patch takes care of all the trivial cases. Signed-off-by:
Scott Jiang <scott.jiang.linux@gmail.com> Signed-off-by:
-
- 13 Jun, 2013 7 commits
-
-
Hans Verkuil authored
Drop support for V4L2_CHIP_MATCH_I2C_DRIVER/ADDR and V4L2_CHIP_MATCH_AC97 types. The following patches will remove support for those in the drivers as well. This means that bridge drivers no longer have to check for the match.type field in their g/s_register implementations. Only if they also implement g_chip_info do they still have to check the match.addr field, otherwise the core will check for that as well. Signed-off-by:
-
Lad, Prabhakar authored
generally the pdata needs to be a constant pointer in the device state structure. This patch makes the pdata as a constant pointer and alongside returns -EINVAL when pdata is NULL. Signed-off-by:
-
Lad, Prabhakar authored
the ths7303_setup() was doing the same thing as ths7303_setval() except that ths7303_setval() sets it to some particular mode. This patch removes ths7303_setup() function and calls ths7303_setval() in the probe setting the device to 480I_576I filter mode in the probe. Signed-off-by:
-
Lad, Prabhakar authored
This patch removes init_enable option from pdata, the init_enable was intended that the device should start streaming video immediately but ideally the bridge drivers should call s_stream explicitly for such devices to start video. Signed-off-by:
-
Lad, Prabhakar authored
Remove init_enable from ths7303 pdata as it is being dropped from ths7303_platform_data. The purpose of init_enable was that the device should start streaming video immediately but instead the bridge drivers should call s_stream explicitly for such devices. This is in fact what happens for the dm365, so setting init_enable here never made sense in the first place. Signed-off-by:
Sekhar Nori <nsekhar@ti.com> Signed-off-by:
-
Antti Palosaari authored
It was found by trial and error testing that at least 11 ms delay is needed before first I/O, otherwise device will skip given command. Signed-off-by:
Antti Palosaari <crope@iki.fi> Signed-off-by:
-
Hans Verkuil authored
The device was never set to the initial frequency. Signed-off-by:
-
