24 Aug, 2016
40 commits
-
Replace all calls to g/s_crop by calls to the get/set_selection pad ops.
Remove the old g/s_crop video ops since they are now no longer used.
The cropcap video op is now only used to pass pixelaspect information,
and is only needed if the pixelaspect is not 1:1.Signed-off-by: Hans Verkuil
Cc: Guennadi Liakhovetski
Acked-by: Laurent Pinchart
Signed-off-by: Mauro Carvalho Chehab -
Some targets control the ADV7180 power pin via a gpio, so add
optional support for "powerdown" pin control.Signed-off-by: Steve Longerbeam
Tested-by: Tim Harvey
Acked-by: Lars-Peter Clausen
Signed-off-by: Hans Verkuil
Signed-off-by: Mauro Carvalho Chehab -
Replace hard-coded addresses with new register macro defines. No
functional changes.Signed-off-by: Steve Longerbeam
Acked-by: Lars-Peter Clausen
Signed-off-by: Hans Verkuil
Signed-off-by: Mauro Carvalho Chehab -
The video_unregister_device() function tests whether its argument is NULL
and then returns immediately. Thus the test around the call is not needed.This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
Signed-off-by: Hans Verkuil
Signed-off-by: Mauro Carvalho Chehab -
The spi_unregister_device() function tests whether its argument is NULL
and then returns immediately. Thus the test around the call is not needed.This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
Signed-off-by: Hans Verkuil
Signed-off-by: Mauro Carvalho Chehab -
The rc_free_device() function tests whether its argument is NULL
and then returns immediately. Thus the test around the call is not needed.This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
Signed-off-by: Hans Verkuil
Signed-off-by: Mauro Carvalho Chehab -
Add support for reduced fps (i.e. 59.94 Hz instead of 60 Hz) for the
HDMI output.Signed-off-by: Hans Verkuil
Signed-off-by: Mauro Carvalho Chehab -
The workqueue work_queue is involved in EDID (Extended Display
Identification Data) handling.It has a single work item(&state->edid_handler) and hence
doesn't require ordering. It is not being used on a memory reclaim path.
Hence, the singlethreaded workqueue has been replaced with
the use of system_wq.&state->edid_handler is a self requeueing work item and it has been
been sync cancelled in ad9389b_remove() to ensure that nothing is
pending when the driver is disconnected.The unused label err_unreg has also been dropped.
Signed-off-by: Bhaktipriya Shridhar
Acked-by: Tejun Heo
Signed-off-by: Hans Verkuil
Signed-off-by: Mauro Carvalho Chehab -
The workqueue "work_thread" is involved in streaming the camera data.
It has a single work item(&dev->work_struct) and hence doesn't require
ordering. Also, it is not being used on a memory reclaim path.
Hence, the singlethreaded workqueue has been replaced with the use of
system_wq.System workqueues have been able to handle high level of concurrency
for a long time now and hence it's not required to have a singlethreaded
workqueue just to gain concurrency. Unlike a dedicated per-cpu workqueue
created with create_singlethread_workqueue(), system_wq allows multiple
work items to overlap executions even on the same CPU; however, a
per-cpu workqueue doesn't have any CPU locality or global ordering
guarantee unless the target CPU is explicitly specified and thus the
increase of local concurrency shouldn't make any difference.Work item has been flushed in sd_stop0() to ensure that there are no
pending tasks while disconnecting the driver.Signed-off-by: Bhaktipriya Shridhar
Acked-by: Tejun Heo
Acked-by: Frank Zago
Signed-off-by: Hans Verkuil
Signed-off-by: Mauro Carvalho Chehab -
The workqueue "work_thread" is involved in streaming the camera data.
It has a single work item(&sd->work_struct) and hence doesn't require
ordering. Also, it is not being used on a memory reclaim path.
Hence, the singlethreaded workqueue has been replaced with the use of
system_wq.System workqueues have been able to handle high level of concurrency
for a long time now and hence it's not required to have a singlethreaded
workqueue just to gain concurrency. Unlike a dedicated per-cpu workqueue
created with create_singlethread_workqueue(), system_wq allows multiple
work items to overlap executions even on the same CPU; however, a
per-cpu workqueue doesn't have any CPU locality or global ordering
guarantee unless the target CPU is explicitly specified and thus the
increase of local concurrency shouldn't make any difference.Work item has been flushed in sd_stop0() to ensure that there are no
pending tasks while disconnecting the driver.Signed-off-by: Bhaktipriya Shridhar
Acked-by: Tejun Heo
Signed-off-by: Hans Verkuil
Signed-off-by: Mauro Carvalho Chehab -
The workqueue "work_thread" is involved in streaming the camera data.
It has a single work item(&sd->work_struct) and hence doesn't require
ordering. Also, it is not being used on a memory reclaim path.
Hence, the singlethreaded workqueue has been replaced with the use of
system_wq.System workqueues have been able to handle high level of concurrency
for a long time now and hence it's not required to have a singlethreaded
workqueue just to gain concurrency. Unlike a dedicated per-cpu workqueue
created with create_singlethread_workqueue(), system_wq allows multiple
work items to overlap executions even on the same CPU; however, a
per-cpu workqueue doesn't have any CPU locality or global ordering
guarantee unless the target CPU is explicitly specified and thus the
increase of local concurrency shouldn't make any difference.Work item has been flushed in sd_stop0() to ensure that there are no
pending tasks while disconnecting the driver.Signed-off-by: Bhaktipriya Shridhar
Acked-by: Tejun Heo
Signed-off-by: Hans Verkuil
Signed-off-by: Mauro Carvalho Chehab -
The workqueue "work_thread" is involved in updating the JPEG quality
of the gspca_dev. It has a single work item(&sd->work) and hence doesn't
require ordering. Also, it is not being used on a memory reclaim path.
Hence, the singlethreaded workqueue has been replaced with the use of
system_wq.System workqueues have been able to handle high level of concurrency
for a long time now and hence it's not required to have a singlethreaded
workqueue just to gain concurrency. Unlike a dedicated per-cpu workqueue
created with create_singlethread_workqueue(), system_wq allows multiple
work items to overlap executions even on the same CPU; however, a
per-cpu workqueue doesn't have any CPU locality or global ordering
guarantee unless the target CPU is explicitly specified and thus the
increase of local concurrency shouldn't make any difference.Work item has been flushed in sd_stop0() to ensure that there are no
pending tasks while disconnecting the driver.Signed-off-by: Bhaktipriya Shridhar
Acked-by: Tejun Heo
Signed-off-by: Hans Verkuil
Signed-off-by: Mauro Carvalho Chehab -
The workqueue "workqueue" is involved in polling the pvrusb2 hardware
(pvr2_hdw).It has a single work item(&hdw->workpoll) and hence doesn't require
ordering. Also, it is not being used on a memory reclaim path.
Hence, the singlethreaded workqueue has been replaced with the use of
system_wq.System workqueues have been able to handle high level of concurrency
for a long time now and hence it's not required to have a singlethreaded
workqueue just to gain concurrency. Unlike a dedicated per-cpu workqueue
created with create_singlethread_workqueue(), system_wq allows multiple
work items to overlap executions even on the same CPU; however, a
per-cpu workqueue doesn't have any CPU locality or global ordering
guarantee unless the target CPU is explicitly specified and thus the
increase of local concurrency shouldn't make any difference.Work item has been flushed in pvr2_hdw_destroy to ensure that there are no
pending tasks while disconnecting the driver.Signed-off-by: Bhaktipriya Shridhar
Acked-by: Tejun Heo
Signed-off-by: Hans Verkuil
Signed-off-by: Mauro Carvalho Chehab -
kmalloc will print enough information in case of failure.
Signed-off-by: Wolfram Sang
Signed-off-by: Hans Verkuil
Signed-off-by: Mauro Carvalho Chehab -
kmalloc will print enough information in case of failure.
Signed-off-by: Wolfram Sang
Signed-off-by: Hans Verkuil
Signed-off-by: Mauro Carvalho Chehab -
kmalloc will print enough information in case of failure.
Signed-off-by: Wolfram Sang
Signed-off-by: Hans Verkuil
Signed-off-by: Mauro Carvalho Chehab -
kmalloc will print enough information in case of failure.
Signed-off-by: Wolfram Sang
Signed-off-by: Hans Verkuil
Signed-off-by: Mauro Carvalho Chehab -
kmalloc will print enough information in case of failure.
Signed-off-by: Wolfram Sang
Signed-off-by: Hans Verkuil
Signed-off-by: Mauro Carvalho Chehab -
kmalloc will print enough information in case of failure.
Signed-off-by: Wolfram Sang
Signed-off-by: Hans Verkuil
Signed-off-by: Mauro Carvalho Chehab -
kmalloc will print enough information in case of failure.
Signed-off-by: Wolfram Sang
Signed-off-by: Hans Verkuil
Signed-off-by: Mauro Carvalho Chehab -
kmalloc will print enough information in case of failure.
Signed-off-by: Wolfram Sang
Signed-off-by: Hans Verkuil
Signed-off-by: Mauro Carvalho Chehab -
kmalloc will print enough information in case of failure.
Signed-off-by: Wolfram Sang
Signed-off-by: Hans Verkuil
Signed-off-by: Mauro Carvalho Chehab -
kmalloc will print enough information in case of failure.
Signed-off-by: Wolfram Sang
Signed-off-by: Hans Verkuil
Signed-off-by: Mauro Carvalho Chehab -
kmalloc will print enough information in case of failure.
Signed-off-by: Wolfram Sang
Signed-off-by: Hans Verkuil
Signed-off-by: Mauro Carvalho Chehab -
kmalloc will print enough information in case of failure.
Signed-off-by: Wolfram Sang
Signed-off-by: Hans Verkuil
Signed-off-by: Mauro Carvalho Chehab -
kmalloc will print enough information in case of failure.
Signed-off-by: Wolfram Sang
Signed-off-by: Hans Verkuil
Signed-off-by: Mauro Carvalho Chehab -
kmalloc will print enough information in case of failure.
Signed-off-by: Wolfram Sang
Signed-off-by: Hans Verkuil
Signed-off-by: Mauro Carvalho Chehab -
kmalloc will print enough information in case of failure.
Signed-off-by: Wolfram Sang
Signed-off-by: Hans Verkuil
Signed-off-by: Mauro Carvalho Chehab -
kmalloc will print enough information in case of failure.
Signed-off-by: Wolfram Sang
Signed-off-by: Hans Verkuil
Signed-off-by: Mauro Carvalho Chehab -
kmalloc will print enough information in case of failure.
Signed-off-by: Wolfram Sang
Signed-off-by: Hans Verkuil
Signed-off-by: Mauro Carvalho Chehab -
kmalloc will print enough information in case of failure.
Signed-off-by: Wolfram Sang
Signed-off-by: Hans Verkuil
Signed-off-by: Mauro Carvalho Chehab -
kmalloc will print enough information in case of failure.
Signed-off-by: Wolfram Sang
Signed-off-by: Hans Verkuil
Signed-off-by: Mauro Carvalho Chehab -
kmalloc will print enough information in case of failure.
Signed-off-by: Wolfram Sang
Signed-off-by: Hans Verkuil
Signed-off-by: Mauro Carvalho Chehab -
kmalloc will print enough information in case of failure.
Signed-off-by: Wolfram Sang
Signed-off-by: Hans Verkuil
Signed-off-by: Mauro Carvalho Chehab -
kmalloc will print enough information in case of failure.
Signed-off-by: Wolfram Sang
Signed-off-by: Hans Verkuil
Signed-off-by: Mauro Carvalho Chehab -
kmalloc will print enough information in case of failure.
Signed-off-by: Wolfram Sang
Signed-off-by: Hans Verkuil
Signed-off-by: Mauro Carvalho Chehab -
kmalloc will print enough information in case of failure.
Signed-off-by: Wolfram Sang
Signed-off-by: Hans Verkuil
Signed-off-by: Mauro Carvalho Chehab -
kmalloc will print enough information in case of failure.
Signed-off-by: Wolfram Sang
Signed-off-by: Hans Verkuil
Signed-off-by: Mauro Carvalho Chehab -
kmalloc will print enough information in case of failure.
Signed-off-by: Wolfram Sang
Signed-off-by: Hans Verkuil
Signed-off-by: Mauro Carvalho Chehab -
kmalloc will print enough information in case of failure.
Signed-off-by: Wolfram Sang
Signed-off-by: Hans Verkuil
Signed-off-by: Mauro Carvalho Chehab
