Re: [PATCH] media: videobuf2-core: Fix one __qbuf_dmabuf() error path

Hi Wu, Wu, Xia wrote: > Add dma_buf_put() to decrease refcount of the dmabuf in error path if DMABUF > size is smaller than the requirement. > > Signed-off-by: wu xia > --- > drivers/media/v4l2-core/videobuf2-core.c |1 + > 1 file changed, 1 insertion(+) > > diff --git

Re: [PATCH 3/7] of: reserved_mem: add support for named reserved mem nodes

Hello, On 2015-12-08 15:58, Rob Herring wrote: On Mon, Dec 7, 2015 at 6:08 AM, Marek Szyprowski wrote: This patch allows device drivers to use more than one reserved memory region assigned to given device. When NULL name is passed to of_reserved_mem_device_init(),

Re: [PATCHv11 15/15] videobuf2-core: fix plane_sizes handling in VIDIOC_CREATE_BUFS

Hi Hans, On Fri, Nov 20, 2015 at 05:45:48PM +0100, Hans Verkuil wrote: > From: Hans Verkuil > > The handling of q->plane_sizes was wrong in vb2_core_create_bufs(). > The q->plane_sizes array was global and it was overwritten by create_bufs. > So if reqbufs was called

Re: Failed to build on 4.2.6

Greg Kroah-Hartman writes: > On Mon, Dec 07, 2015 at 10:25:19AM -0500, Steven Rostedt wrote: >> Hi, >> >> The attached config doesn't build on 4.2.6, but changing it to the >> following: >> >> VIDEO_V4L2_SUBDEV_API n -> y >> +V4L2_FLASH_LED_CLASS n >> >> does build. > > Did this work on older

Re: [PATCH] v4l: Fix dma buf single plane compat handling

On Wed, Dec 09, 2015 at 01:11:12AM +0200, Laurent Pinchart wrote: > Hi Sakari, > > On Tuesday 08 December 2015 17:29:16 Sakari Ailus wrote: > > On Mon, Dec 07, 2015 at 10:45:39AM +0200, Laurent Pinchart wrote: > > > From: Gjorgji Rosikopulos > > > > > > Buffer length is

[Fwd: Problem with avermedia Volar Black HD (af9015) : recognised but not scanning]

Hello, Any ideas on my problem ? Am I on the right mailing-list ? Any help would be appreciated ! Thanks, OD Message transféré > De: oddebian > À: linux-media@vger.kernel.org > Objet: Problem with avermedia Volar Black HD (af9015) : recognised but > not

[v4l-utils PATCH 1/1] v4l: libv4l2subdev: Precisely convert media bus string to code

The length of the string was ignored, making it possible for the conversion to fail due to extra characters in the string. Signed-off-by: Sakari Ailus --- This patch should be applied before the set "[v4l-utils PATCH v2 0/3] List supported formats in libv4l2subdev":

Re: [PATCH v8 52/55] [media] media-device: remove interfaces and interface links

Em Mon, 23 Nov 2015 23:22:56 +0200 Laurent Pinchart escreveu: > Hi Mauro, > > Thank you for the patch. > > On Sunday 06 September 2015 09:03:12 Mauro Carvalho Chehab wrote: > > Just like what's done with entities, when the media controller is > >

[PATCH v2 0/7] Exynos: MFC driver: reserved memory cleanup and IOMMU support

Hello, This patchset finally perform cleanup of custom code in s5p-mfc codec driver. The first part is removal of custom, driver specific code for intializing and handling of reserved memory. Instead, a generic code for reserved memory regions is used. Then, once it is done, the proper setup of

[PATCH v2 2/7] ARM: dts: exynos4412-odroid*: enable MFC device

Enable support for Multimedia Codec (MFC) device for all Exynos4412-based Odroid boards. Signed-off-by: Marek Szyprowski --- arch/arm/boot/dts/exynos4412-odroid-common.dtsi | 24 1 file changed, 24 insertions(+) diff --git

[PATCH v2 1/7] ARM: Exynos: convert MFC device to generic reserved memory bindings

This patch replaces custom properties for definining reserved memory regions with generic reserved memory bindings. All custom code for handling MFC-specific reserved memory can be now removed from Exynos-DT generic board code. Signed-off-by: Marek Szyprowski ---

[PATCH v2 6/7] media: s5p-mfc: replace custom reserved memory init code with generic one

This patch removes custom code for initialization and handling of reserved memory regions in s5p-mfc driver and replaces it with generic named reserved memory regions specified in device tree. s5p-mfc driver now handles two reserved memory regions: "left" and "right", defined by generic reserved

[PATCH v2 7/7] media: s5p-mfc: add iommu support

This patch adds support for IOMMU to s5p-mfc device driver. MFC firmware is limited and it cannot use the default configuration. If IOMMU is available, the patch disables the default DMA address space configuration and creates a new address space of size limited to 256M and base address set to

[PATCH v2 4/7] media: vb2-dma-contig: add helper for setting dma max seg size

Add a helper function for device drivers to set DMA's max_seg_size. Setting it to largest possible value lets DMA-mapping API always create contiguous mappings in DMA address space. This is essential for all devices, which use dma-contig videobuf2 memory allocator and shared buffers.

[PATCH v2 5/7] media: set proper max seg size for devices on Exynos SoCs

All multimedia devices found on Exynos SoCs support only contiguous buffers, so set DMA max segment size to DMA_BIT_MASK(32) to let memory allocator to correctly create contiguous memory mappings. Signed-off-by: Marek Szyprowski ---

[PATCH v2 3/7] of: reserved_mem: add support for named reserved mem nodes

This patch allows device drivers to initialize more than one reserved memory region assigned to given device. When driver needs to use more than one reserved memory region, it should allocate child devices and initialize regions by index or name for each of its child devices. Signed-off-by: Marek

[PATCH 3/4] media: s5p-mfc: remove non-device-tree init code

Exynos and Samsung S5P platforms has been fully converted to device tree, so old platform device based init data can be now removed. Signed-off-by: Marek Szyprowski --- drivers/media/platform/s5p-mfc/s5p_mfc.c | 37 +--- 1 file changed,

[PATCH 2/4] media: s5p-g2d: remove non-device-tree init code

Exynos and Samsung S5P platforms has been fully converted to device tree, so old platform device based init data can be now removed. Signed-off-by: Marek Szyprowski --- drivers/media/platform/s5p-g2d/g2d.c | 27 +--

[PATCH 1/4] media: exynos-gsc: remove non-device-tree init code

Exynos platform has been fully converted to device tree, so old platform device based init data can be now removed. Signed-off-by: Marek Szyprowski --- drivers/media/platform/exynos-gsc/gsc-core.c | 33 +---

[PATCH 160/182] [media]: cxd2830r: use gpiochip data pointer

This makes the driver use the data pointer added to the gpio_chip to store a pointer to the state container instead of relying on container_of(). Cc: Antti Palosaari Cc: Mauro Carvalho Chehab Cc: linux-media@vger.kernel.org Signed-off-by: Linus Walleij

[PATCH 4/4] media: exynos4-is: remove non-device-tree init code

Exynos and Samsung S5P platforms has been fully converted to device tree, so old platform device based init data can be now removed. Signed-off-by: Marek Szyprowski --- drivers/media/platform/exynos4-is/fimc-core.c | 50 --- 1 file changed,

Re: DVBSky T980C ci not working with kernel 4.x

On 08.12.2015 05:49, Nibble Max wrote: Does this card work with the media code from dvbsky.net from kernel 4.x? On 2015-12-06 19:10:41, Timo_Helkiö wrote: Hi Common interface in Dvbsky T980C is not working with Ubuntu 15.10 kernel 4.2.0 and vanilla kernel 4.6 and

Re: Dear TV card experts - I need you help

On 12/04/2015 05:35 PM, Mr Andersson wrote: Hi Benjamin, Thanks for your answer. Jag uppskattar din hjälp ;) So 50 USD per mux. And I could simultaneously record up to 4 channels per mux ? Is that satellite dependant? Could you give me an example of high quality/value cards I should look at

dtv-scan-table has two ATSC files?

I’m making some updates to the ATSC dtv-scan-tables. Two questions: 1) Why do we have "us-ATSC-center-frequencies-8VSB” *and* "us-NTSC-center-frequencies-8VSB”? They appear to be identical. The later could, theoretically, list NTSC encoded channels instead of 8VSB, but doesn’t actually do

[PATCH] ca-ON-Toronto: adding scan file for Toronto, Canada

My second patch, you can be slightly less gentle now :-) This is a scan listing for the Toronto area, along with some of the harder to get signals. I was unsure how to enter the NTSC (analog) signals so I commented them out. --- atsc/ca-ON-Toronto | 200

RE: [PATCH] media: videobuf2-core: Fix one __qbuf_dmabuf() error path

Hi, Sakari, On Wed, Dec 09, 2015 at 4:26PM, Sakari wrote: > Hi Wu, > > Wu, Xia wrote: > > Add dma_buf_put() to decrease refcount of the dmabuf in error path if > DMABUF size is smaller than the requirement. > > > > Signed-off-by: wu xia > > --- > >

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: Thu Dec 10 04:00:17 CET 2015 git branch: test git hash: 991ce92f8de24cde063d531246602b6e14d3fef2 gcc

[PATCH] us-ATSC-center-frequencies-8VSB: Added channel numbers in comments to make the file easier to use by comparing against local channel lists.

This is my first attempt at a patch, so please be gentle. Signed-off-by: Maury Markowitz --- atsc/us-ATSC-center-frequencies-8VSB | 78 1 file changed, 78 insertions(+) diff --git a/atsc/us-ATSC-center-frequencies-8VSB

Re: [PATCH v2 2/7] ARM: dts: exynos4412-odroid*: enable MFC device

On 09.12.2015 22:58, Marek Szyprowski wrote: > Enable support for Multimedia Codec (MFC) device for all Exynos4412-based > Odroid boards. > > Signed-off-by: Marek Szyprowski > --- > arch/arm/boot/dts/exynos4412-odroid-common.dtsi | 24 > 1 file

Re: [PATCH v2 2/7] ARM: dts: exynos4412-odroid*: enable MFC device

On 10.12.2015 16:44, Krzysztof Kozlowski wrote: > On 09.12.2015 22:58, Marek Szyprowski wrote: >> Enable support for Multimedia Codec (MFC) device for all Exynos4412-based ... and one more finding: I think the abbreviation is Multi Format Codec. BR, Krzysztof >> Odroid boards. >> >>