linux-stable.git/drivers/media, branch v4.8.2

[media] cx23885/saa7134: assign q->dev to the PCI device

2016-09-19T15:38:05+00:00

Fix a regression caused by commit 2bc46b3ad3c1 ("[media] media/pci:
convert drivers to use the new vb2_queue dev field").

Three places where q->dev should be set were missed, causing
a WARN.

Fixes: 2bc46b3ad3c1 ("[media] media/pci: convert drivers to use the new vb2_queue dev field").

Signed-off-by: Hans Verkuil 
Reported-by: Marton Balint 
Signed-off-by: Mauro Carvalho Chehab

[media] rcar-fcp: Make sure rcar_fcp_enable() returns 0 on success

2016-09-15T12:02:16+00:00

When resuming from suspend-to-RAM on r8a7795/salvator-x:

    dpm_run_callback(): pm_genpd_resume_noirq+0x0/0x90 returns 1
    PM: Device fe940000.fdp1 failed to resume noirq: error 1
    dpm_run_callback(): pm_genpd_resume_noirq+0x0/0x90 returns 1
    PM: Device fe944000.fdp1 failed to resume noirq: error 1
    dpm_run_callback(): pm_genpd_resume_noirq+0x0/0x90 returns 1
    PM: Device fe948000.fdp1 failed to resume noirq: error 1

According to its documentation, rcar_fcp_enable() returns 0 on success
or a negative error code if an error occurs.  Hence
fdp1_pm_runtime_resume() and vsp1_pm_runtime_resume() forward its return
value to their callers.

However, rcar_fcp_enable() forwards the return value of
pm_runtime_get_sync(), which can actually be 1 on success, leading to
the resume failure above.

To fix this, consider only negative values returned by
pm_runtime_get_sync() to be failures.

Fixes: 7b49235e83b2347c ("[media] v4l: Add Renesas R-Car FCP driver")

Signed-off-by: Geert Uytterhoeven 
Reviewed-by: Laurent Pinchart 
Signed-off-by: Mauro Carvalho Chehab

[media] vcodec:mediatek: Refine VP8 encoder driver

2016-08-24T14:28:36+00:00

This patch remove field and function that unused anymore

Signed-off-by: Tiffany Lin 
Signed-off-by: Hans Verkuil 
Signed-off-by: Mauro Carvalho Chehab

[media] vcodec:mediatek: Refine H264 encoder driver

2016-08-24T14:28:11+00:00

This patch :
1. remove field and function that unused anymore
2. add support V4L2_MPEG_VIDEO_H264_LEVEL_4_2

Signed-off-by: Tiffany Lin 
Signed-off-by: Hans Verkuil 
Signed-off-by: Mauro Carvalho Chehab

[media] vcodec:mediatek: change H264 profile default to profile high

2016-08-24T14:27:38+00:00

This patch change default H264 profile from V4L2_MPEG_VIDEO_H264_PROFILE_MAIN
to V4L2_MPEG_VIDEO_H264_PROFILE_HIGH

Signed-off-by: Tiffany Lin 
Signed-off-by: Hans Verkuil 
Signed-off-by: Mauro Carvalho Chehab

[media] vcodec:mediatek: Add timestamp and timecode copy for V4L2 Encoder

2016-08-24T14:27:10+00:00

This patch add copying timestamp and timecode from src buffer to dst buffer

Signed-off-by: Tiffany Lin 
Signed-off-by: Hans Verkuil 
Signed-off-by: Mauro Carvalho Chehab

[media] vcodec:mediatek: Fix visible_height larger than coded_height issue in s_fmt_out

2016-08-24T14:26:41+00:00

The original code add extra 32 line to visible_height.
It is incorrect, 32 line should be add to coded_height.
The purpose is that user space could calcuate real buffer size needed by using
coded_width * coded_height.
But this method will make v4l2-compliance test fail, since g_fmt != s_fmt(g_fmt)
So remove extend visible_height or coded_height, user space should just
use sizeimage to get real buffer size needed

Signed-off-by: Tiffany Lin 
Signed-off-by: Hans Verkuil 
Signed-off-by: Mauro Carvalho Chehab

[media] vcodec:mediatek: Fix fops_vcodec_release flow for V4L2 Encoder

2016-08-24T14:21:43+00:00

This patch fix that mtk_vcodec_venc_release should be called after v4l2_m2m_ctx_release

Signed-off-by: Tiffany Lin 
Signed-off-by: Hans Verkuil 
Signed-off-by: Mauro Carvalho Chehab

[media] vcodec:mediatek:code refine for v4l2 Encoder driver

2016-08-24T14:20:50+00:00

This patch remove unused header and define from haeder files

Signed-off-by: Tiffany Lin 
Signed-off-by: Hans Verkuil 
Signed-off-by: Mauro Carvalho Chehab

[media] cec-edid: check for IEEE identifier

2016-08-22T17:04:51+00:00

The cec_get_edid_spa_location() function did not verify that the IEEE
identifier in the Vendor Specific Data Block matched the HDMI-LLC
identifier. This could result in the wrong VSDB block being returned.

For example, for HDMI 2.0 EDIDs there is also a HDMI Forum VSDB.

So check the IEEE identifier as well.

Signed-off-by: Hans Verkuil 
Signed-off-by: Mauro Carvalho Chehab