RE: [PATCH v2 1/3] staging: xm2mvscale: Driver support for Xilinx M2M Video Scaler

---Original Message- > From: Hans Verkuil [mailto:hverk...@xs4all.nl] > Sent: Friday, March 09, 2018 3:58 AM > To: Greg KH ; Rohit Athavale > > Cc: de...@driverdev.osuosl.org; linux-media@vger.kernel.org > Subject: Re: [PATCH v2 1/3] staging: xm2mvscale: Driver support for Xil

[PATCH v2 1/3] staging: xm2mvscale: Driver support for Xilinx M2M Video Scaler

ioctl_xm2mvsc.h - The char driver that consumes the IP layer in xm2m_vscale.c Signed-off-by: Rohit Athavale --- drivers/staging/Kconfig | 2 + drivers/staging/Makefile | 1 + drivers/staging/xm2mvscale/Kconfig| 11 + drivers/staging

[PATCH v2 2/3] staging: xm2mvscale: Add TODO for the driver

This commit highlights the key functionalities that will be improved upon in a future patch set. Signed-off-by: Rohit Athavale --- drivers/staging/xm2mvscale/TODO | 18 ++ 1 file changed, 18 insertions(+) create mode 100644 drivers/staging/xm2mvscale/TODO diff --git a/drivers

[PATCH v2 3/3] Documentation: devicetree: bindings: Add DT binding doc for xm2mvsc driver

This commit adds the binding doc for the DT that the driver expects. Driver has been tested against Zynq US+ board. Signed-off-by: Rohit Athavale --- .../devicetree/bindings/xm2mvscaler.txt| 25 ++ 1 file changed, 25 insertions(+) create mode 100644 drivers

[PATCH v2 0/3] Initial driver support for Xilinx M2M Video Scaler

.c to see if it makes sense. - Another question would be the right place to keep the driver, in drivers/staging/media or drivers/staging/ - Dropped empty mmap_open, mmap_close ops. - Removed incorrect DMA_SHARED_BUFFER select from Kconfig v1 - Initial version Rohit Athavale (3): st

[PATCH 1/3] uapi: media-bus-format: Add Xilinx specific YCbCr 4:2:0 media bus format

This commit adds Xilinx Video IP specific 8-bit color depth YCbCr 4:2:0 to the media bus format uapi. Signed-off-by: Rohit Athavale --- include/uapi/linux/media-bus-format.h | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/include/uapi/linux/media-bus-format.h b/include

[PATCH 3/3] Documentation: subdev-formats: Add Xilinx YCbCr to Vendor specific area

This commit adds the custom Xilinx IP specific 8-bit YCbCr 4:2:0 to the custom formats area in the subdev-formats documentation. Signed-off-by: Rohit Athavale --- Documentation/media/uapi/v4l/subdev-formats.rst | 5 + 1 file changed, 5 insertions(+) diff --git a/Documentation/media/uapi

[PATCH 0/3] Xilinx 8-bit color depth YCbCr 4:2:0 media bus format

Chroma when present along with the Luma component, otherwise zero padded Luma only data is sent. The first patch (1/3) adds the format to the uapi header file. The second patch (2/3) adds the format to the table in xilinx-vip.c. The third patch (3/3) updates the subdev format doc file. Rohit

[PATCH 2/3] media: xilinx-vip: Add 8-bit YCbCr 4:2:0 to formats table

Add Xilinx YCbCr 4:2:0 to xvip formats table. This commit will allow driver to setup media pad codes to YUV 420 via DT properties. Signed-off-by: Rohit Athavale --- drivers/media/platform/xilinx/xilinx-vip.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/media/platform/xilinx

Question about Large Custom Coefficients for V4L2 sub-device drivers

Hello Media Community, I am working on a scaler and gamma correction V4L2 sub-device based drivers. A common theme to both of them is that the kernel driver is expected bring-up these devices in a working (good) configuration. As it turns out these coefficients are tailor-made or are fairly comp