[RFC] omap3isp: add support for CSI1 bus

omap3isp: add rest of CSI1 support CSI1 needs one more bit to be set up. Do just that. Signed-off-by: Pavel Machek --- Hmm. Looking at that... num_data_lanes probably should be modified in local variable, not globally like this. Should I do that? Anything else that needs

[PATCH] v4l2-fwnode: Fix clock lane parsing

Fix clock lane parsing in v4l2-fwnode. Signed-off-by: Pavel Machek diff --git a/drivers/media/v4l2-core/v4l2-fwnode.c b/drivers/media/v4l2-core/v4l2-fwnode.c index dd3..44036b8 100644 --- a/drivers/media/v4l2-core/v4l2-fwnode.c +++ b/drivers/media/v4l2-core/v4l2-fwnode.c

Re: [PATCH 1/4] v4l: vsp1: Implement partition algorithm restrictions

Hi Laurent, Kieran > > > Testing SRU-UDS scaling 768x576 - 768x576 - 640x480 in RGB24: fail > > > Testing SRU-UDS scaling 768x576 - 768x576 - 768x576 in RGB24: pass > > > Testing SRU-UDS scaling 768x576 - 768x576 - 1024x768 in RGB24: pass > > > Testing SRU-UDS scaling 768x576 - 1536x1152 -

cron job: media_tree daily build: ERRORS

This message is generated daily by a cron job that builds media_tree for the kernels and architectures in the list below. Results of the daily build of media_tree: date: Mon Mar 6 05:00:18 CET 2017 media-tree git hash:3dc2046ca78b3cac6c8c9098a4e3024cd91abdb4 media_build

[PATCH v2.1 3/3] v4l: vsp1: wpf: Implement rotation support

Some WPF instances, on Gen3 devices, can perform 90° rotation when writing frames to memory. Implement support for this using the V4L2_CID_ROTATE control. Signed-off-by: Laurent Pinchart --- Changes since v2: - Store controls in distinct fields instead

Re: [PATCH v4 13/36] [media] v4l2: add a frame timeout event

On Sat, Mar 04, 2017 at 04:37:43PM -0800, Steve Longerbeam wrote: > > > On 03/04/2017 02:56 AM, Sakari Ailus wrote: > >That's a bit of a special situation --- still there are alike conditions on > >existing hardware. You should return the buffers to the user with the ERROR > >flag set --- or

Re: [PATCH v3 2/3] v4l: vsp1: Extend VSP1 module API to allow DRM callbacks

Hi Laurent, On 05/03/17 21:58, Laurent Pinchart wrote: > Hi Kieran, > > Thank you for the patch. > > On Sunday 05 Mar 2017 16:00:03 Kieran Bingham wrote: >> To be able to perform page flips in DRM without flicker we need to be >> able to notify the rcar-du module when the VSP has completed its

Re: [PATCH v3 3/3] drm: rcar-du: Register a completion callback with VSP1

Hi Kieran, Thank you for the patch. On Sunday 05 Mar 2017 16:00:04 Kieran Bingham wrote: > Currently we process page flip events on every display interrupt, > however this does not take into consideration the processing time needed > by the VSP1 utilised in the pipeline. > > Register a callback

Re: [PATCH v3 1/3] v4l: vsp1: Postpone frame end handling in event of display list race

Hi Kieran, Thank you for the patch. On Sunday 05 Mar 2017 16:00:02 Kieran Bingham wrote: > If we try to commit the display list while an update is pending, we have > missed our opportunity. The display list manager will hold the commit > until the next interrupt. > > In this event, we skip the

Re: [PATCH v3 2/3] v4l: vsp1: Extend VSP1 module API to allow DRM callbacks

Hi Kieran, Thank you for the patch. On Sunday 05 Mar 2017 16:00:03 Kieran Bingham wrote: > To be able to perform page flips in DRM without flicker we need to be > able to notify the rcar-du module when the VSP has completed its > processing. > > We must not have bidirectional dependencies on

Re: [PATCH v4 13/36] [media] v4l2: add a frame timeout event

On Sat, Mar 04, 2017 at 04:37:43PM -0800, Steve Longerbeam wrote: > > > On 03/04/2017 02:56 AM, Sakari Ailus wrote: > >Hi Steve, > > > >On Fri, Mar 03, 2017 at 02:43:51PM -0800, Steve Longerbeam wrote: > >> > >> > >>On 03/03/2017 03:45 AM, Sakari Ailus wrote: > >>>On Thu, Mar 02, 2017 at

[PATCH v2.2] v4l: Clearly document interactions between formats, controls and buffers

V4L2 exposes parameters that influence buffers sizes through the format ioctls (VIDIOC_G_FMT, VIDIOC_TRY_FMT, VIDIOC_S_FMT, and possibly VIDIOC_G_SELECTION and VIDIOC_S_SELECTION). Other parameters not part of the format structure may also influence buffer sizes or buffer layout in general. One

Re: [PATCH v2.1] v4l: Clearly document interactions between formats, controls and buffers

Hi Laurent, Thanks for the update. On Sun, Mar 05, 2017 at 04:39:36PM +0200, Laurent Pinchart wrote: > V4L2 exposes parameters that influence buffers sizes through the format > ioctls (VIDIOC_G_FMT, VIDIOC_TRY_FMT, VIDIOC_S_FMT, and possibly > VIDIOC_G_SELECTION and VIDIOC_S_SELECTION). Other

Re: [Outreachy kernel] [PATCH] staging: media: Remove unnecessary function and its call

On Sun, 2017-03-05 at 10:14 -0800, Alison Schofield wrote: > On Sun, Mar 05, 2017 at 12:17:21PM +0530, simran singhal wrote: > > The function atomisp_set_stop_timeout on being called, simply returns > > back. The function hasn't been mentioned in the TODO and doesn't have > > FIXME code around.

Re: [Outreachy kernel] [PATCH] staging: media: Remove unnecessary function and its call

On Sun, Mar 05, 2017 at 12:17:21PM +0530, simran singhal wrote: > The function atomisp_set_stop_timeout on being called, simply returns > back. The function hasn't been mentioned in the TODO and doesn't have > FIXME code around. Hence, atomisp_set_stop_timeout and its calls have been > removed. >

Re: [PATCH v3 3/3] drm: rcar-du: Register a completion callback with VSP1

Hello! On 03/05/2017 07:00 PM, Kieran Bingham wrote: Currently we process page flip events on every display interrupt, however this does not take into consideration the processing time needed by the VSP1 utilised in the pipeline. Register a callback with the VSP driver to obtain completion

[PATCH v3 2/3] v4l: vsp1: Extend VSP1 module API to allow DRM callbacks

To be able to perform page flips in DRM without flicker we need to be able to notify the rcar-du module when the VSP has completed its processing. We must not have bidirectional dependencies on the two components to maintain support for loadable modules, thus we extend the API to allow a callback

[PATCH v3 0/3] RCAR-DU, VSP1: Prevent pre-emptive frame flips on VSP1-DRM pipelines

The RCAR-DU utilises a running VSPD pipeline to perform processing for the display pipeline. This presents the opportunity for some race conditions to affect the quality of the display output. To prevent reporting page flips early, we must track this timing through the VSP1, and only allow the

[PATCH v3 1/3] v4l: vsp1: Postpone frame end handling in event of display list race

If we try to commit the display list while an update is pending, we have missed our opportunity. The display list manager will hold the commit until the next interrupt. In this event, we skip the pipeline completion callback handler so that the pipeline will not mistakenly report frame completion

[PATCH v3 3/3] drm: rcar-du: Register a completion callback with VSP1

Currently we process page flip events on every display interrupt, however this does not take into consideration the processing time needed by the VSP1 utilised in the pipeline. Register a callback with the VSP driver to obtain completion events, and track them so that we only perform page flips

[PATCH] [dtv-scan-tables] [atsc] Add a new list for USA/CAN. Remove channels 52 thru 69 for those in the USA or Canada who may want to save a few clock cycles avoiding scanning through ch 52 to 69.

Signed-off-by: Bill Murphy --- atsc/us-ATSC-center-frequencies-8VSB-062009 | 306 1 file changed, 306 insertions(+) create mode 100644 atsc/us-ATSC-center-frequencies-8VSB-062009 diff --git a/atsc/us-ATSC-center-frequencies-8VSB-062009

[PATCH v2.1] v4l: Clearly document interactions between formats, controls and buffers

V4L2 exposes parameters that influence buffers sizes through the format ioctls (VIDIOC_G_FMT, VIDIOC_TRY_FMT, VIDIOC_S_FMT, and possibly VIDIOC_G_SELECTION and VIDIOC_S_SELECTION). Other parameters not part of the format structure may also influence buffer sizes or buffer layout in general. One

Re: [PATCH v2 2/3] v4l: Clearly document interactions between formats, controls and buffers

Hi Hans, On Saturday 04 Mar 2017 11:53:45 Hans Verkuil wrote: > On 28/02/17 16:03, Laurent Pinchart wrote: > > V4L2 exposes parameters that influence buffers sizes through the format > > ioctls (VIDIOC_G_FMT, VIDIOC_TRY_FMT and VIDIO_S_FMT). Other parameters > > S_SELECTION should be mentioned

Re: [PATCHv2] omap3isp: add support for CSI1 bus

Hi! > > This will probably fail. > > > > rval = omap3isp_csi2_reset(phy->csi2); > > if (rval < 0) > > goto done; > > Could you try to two patches I've applied on the ccp2 branch (I'll remove > them if there are issues). > > That's compile

[PATCH] [v4l-utils] dvb-sat: add support for North American Standard Ku LNB This is the standard LNB used in North America, it is designed with L.O. Freq of 10750 MHz. Intended for the North American

Signed-off-by: Bill Murphy --- lib/libdvbv5/dvb-sat.c | 13 + 1 file changed, 13 insertions(+) diff --git a/lib/libdvbv5/dvb-sat.c b/lib/libdvbv5/dvb-sat.c index 59cb7a6..22a45b1 100644 --- a/lib/libdvbv5/dvb-sat.c +++ b/lib/libdvbv5/dvb-sat.c @@ -126,6

TechnoTrend AG TT-connect CT-3650 CI - itself disconnecting and connecting back (upstream driver)

Hello, With provided kernel image from Debian I had these two issues: sysfs: cannot create duplicate filename '/class/dvb/dvb0.ca0 'sysfs group 'power' not found for kobject 'dvb0.ca0' = It seems that this was fixed by upstream driver. Now I have this issue: My tuner itself is disconnecting and

Re: [PATCH v2 2/3] v4l: Clearly document interactions between formats, controls and buffers

Hi Sakari, On Saturday 04 Mar 2017 15:48:54 Sakari Ailus wrote: > On Sat, Mar 04, 2017 at 11:57:32AM +0100, Hans Verkuil wrote: > ... > > >>> +To simplify their implementation, drivers may also require buffers to > >>> be +reallocated in order to change formats or controls that influence > >>>

Re: [PATCH] media: platform: Renesas IMR driver

Hi Sergei, Thanks for your efforts with this driver. Nice to see that V2 is getting in better shape. In the future, would it be possible for you to include the patch version number in the [PATCH] tag somehow? On Fri, Mar 3, 2017 at 9:03 PM, Sergei Shtylyov

[PATCH v6 2/3] v4l: Add 10/16-bits per channel YUV pixel formats

The formats added by this patch are: V4L2_PIX_FMT_P010 V4L2_PIX_FMT_P010M V4L2_PIX_FMT_P016 V4L2_PIX_FMT_P016M Currently, none of driver uses those format. Also a variant of V4L2_PIX_FMT_P010M pixel format is added. The V4L2_PIX_FMT_P010CM is a compat variant of

[PATCH v6 3/3] drm/rockchip: Support 10 bits yuv format in vop

The rockchip use a special pixel format for those yuv pixel format with 10 bits color depth. Signed-off-by: Randy Li --- drivers/gpu/drm/rockchip/rockchip_drm_fb.c | 1 + drivers/gpu/drm/rockchip/rockchip_drm_vop.c | 34 ++---

[PATCH v6 1/3] drm_fourcc: Add new P010, P016 video format

P010 is a planar 4:2:0 YUV with interleaved UV plane, 10 bits per channel video format. P016 is a planar 4:2:0 YUV with interleaved UV plane, 16 bits per channel video format. V3: Added P012 and fixed cpp for P010 V4: format definition refined per review V5: Format comment block for each new

[PATCH v6 0/3] Add pixel format for 10 bits YUV video

Thanks to Clint's work, this version just correct some wrong info in the comment. I also offer a driver sample here, but it have been verified with the 10 bits properly. I lacks of the userspace tool. And I am not sure whether it is a properly way to support the pixel format used in rockchip,