Re: [PATCH v3 3/4] [media] davinci: vpif_capture: get subdevs from DT

On Wed, Nov 30, 2016 at 04:14:11PM -0800, Kevin Hilman wrote: > Sakari Ailus writes: > > > Hi Kevin, > > > > On Wed, Nov 23, 2016 at 03:25:32PM -0800, Kevin Hilman wrote: > >> Hi Sakari, > >> > >> Sakari Ailus writes: > >> > >> > On Tue, Nov 22, 2016

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 1 05:00:17 CET 2016 media-tree git hash:003611334d5592984e319e08c6b66825aca00290 media_build

[PATCH] Platform: Sti: Bdisp: Clean up file handle in open() error path.

The File handle is not yet added in the vdev list.So no need to call v4l2_fh_del(>fh)if it fails to create control. Signed-off-by: Shailendra Verma --- drivers/media/platform/sti/bdisp/bdisp-v4l2.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH] V4l: omap4iss: Clean up file handle in open() and release().

Both functions initialize the file handle with v4l2_fh_init() and thus need to call clean up with v4l2_fh_exit() as appropriate. Signed-off-by: Shailendra Verma --- drivers/staging/media/omap4iss/iss_video.c |2 ++ 1 file changed, 2 insertions(+) diff --git

[PATCH] Platform: vsp1: Clean up file handle in open() error path.

v4l2_fh_init is already done.So call the v4l2_fh_exit in error condition before returing from the function. Signed-off-by: Shailendra Verma --- drivers/media/platform/vsp1/vsp1_video.c |1 + 1 file changed, 1 insertion(+) diff --git

[PATCH] V4l: omap3isp: Clean up file handle in open() and release().

Both functions initialize the file handle with v4l2_fh_init() and thus need to call clean up with v4l2_fh_exit() as appropriate. Signed-off-by: Shailendra Verma --- drivers/media/platform/omap3isp/ispvideo.c |2 ++ 1 file changed, 2 insertions(+) diff --git

[PATCH] Platform: Exynos-gsc: Clean up file handle in open() error path.

The File handle is not yet added in the vfd list.So no need to call v4l2_fh_del(>fh) if it fails to create control. Signed-off-by: Shailendra Verma --- drivers/media/platform/exynos-gsc/gsc-m2m.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH] Platform: Exynos4-is: Clean up file handle in open() error path.

The File handle is not yet added in the vfd list.So no need to call v4l2_fh_del(>fh) if it fails to create control. Signed-off-by: Shailendra Verma --- drivers/media/platform/exynos4-is/fimc-m2m.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[GIT PULL STABLE] mn88472 & mn88473 chip id bug on probe

I already send these 2 simple patches to stable list, but not sure how to get those mainline so here is pull-request too. Both are same bug, which nacks driver probe when chip is already on warm state. regards Antti The following changes since commit 003611334d5592984e319e08c6b66825aca00290:

[PATCH 1/2] mn88473: fix chip id check on probe

A register used to identify chip during probe was overwritten during firmware download and due to that later probe's for warm chip were failing. Detect chip from the another register, which is located on different register bank 2. Fixes: 7908fad99a6c ("[media] mn88473: finalize driver") Cc:

Re: [PATCH v3 3/4] [media] davinci: vpif_capture: get subdevs from DT

Sakari Ailus writes: > Hi Kevin, > > On Wed, Nov 23, 2016 at 03:25:32PM -0800, Kevin Hilman wrote: >> Hi Sakari, >> >> Sakari Ailus writes: >> >> > On Tue, Nov 22, 2016 at 07:52:43AM -0800, Kevin Hilman wrote: >> >> Allow getting of subdevs from DT

Re: [PATCH v3 4/4] [media] dt-bindings: add TI VPIF documentation

Sakari Ailus writes: > Hi Rob and Kevin, > > On Tue, Nov 29, 2016 at 08:41:44AM -0600, Rob Herring wrote: >> On Mon, Nov 28, 2016 at 4:30 PM, Kevin Hilman wrote: >> > Hi Rob, >> > >> > Rob Herring writes: >> > >> >> On Tue, Nov 22,

Re: [PATCH v3 3/4] [media] davinci: vpif_capture: get subdevs from DT

Hi Kevin, On Wed, Nov 23, 2016 at 03:25:32PM -0800, Kevin Hilman wrote: > Hi Sakari, > > Sakari Ailus writes: > > > On Tue, Nov 22, 2016 at 07:52:43AM -0800, Kevin Hilman wrote: > >> Allow getting of subdevs from DT ports and endpoints. > >> > >> The _get_pdata() function

Re: [PATCH 01/10] doc: DT: camss: Binding document for Qualcomm Camera subsystem driver

On Fri, Nov 25, 2016 at 04:56:53PM +0200, Todor Tomov wrote: > Add DT binding document for Qualcomm Camera subsystem driver. > > Signed-off-by: Todor Tomov > --- > .../devicetree/bindings/media/qcom,camss.txt | 196 > + > 1 file changed, 196

[PATCH v6 1/3] media: Media Device Allocator API

Media Device Allocator API to allows multiple drivers share a media device. Using this API, drivers can allocate a media device with the shared struct device as the key. Once the media device is allocated by a driver, other drivers can get a reference to it. The media device is released when all

[PATCH v6 2/3] media: change au0828 to use Media Device Allocator API

Change au0828 to use Media Device Allocator API to allocate media device with the parent usb struct device as the key, so it can be shared with the snd_usb_audio driver. Signed-off-by: Shuah Khan --- Changes to patch 0002: - No changes since patch v2, applies cleanly on

[PATCH v6 3/3] sound/usb: Use Media Controller API to share media resources

Change ALSA driver to use Media Controller API to share media resources with DVB, and V4L2 drivers on a AU0828 media device. Media Controller specific initialization is done after sound card is registered. ALSA creates Media interface and entity function graph nodes for Control, Mixer, PCM

[PATCH v6 0/3] Media Device Allocator API

Media Device Allocator API to allows multiple drivers share a media device. Using this API, drivers can allocate a media device with the shared struct device as the key. Once the media device is allocated by a driver, other drivers can get a reference to it. The media device is released when all

Re: [PATCH v3 4/4] [media] dt-bindings: add TI VPIF documentation

Hi Rob and Kevin, On Tue, Nov 29, 2016 at 08:41:44AM -0600, Rob Herring wrote: > On Mon, Nov 28, 2016 at 4:30 PM, Kevin Hilman wrote: > > Hi Rob, > > > > Rob Herring writes: > > > >> On Tue, Nov 22, 2016 at 07:52:44AM -0800, Kevin Hilman wrote: > >>>

[PATCH 2/4] [media] lmedm04: change some static variables to automatic

ibuf and rbuf in lme2510_int_response are always assigned to before they are read, and their addresses do not escape the function, so they have no reason to be static. Signed-off-by: Rasmus Villemoes --- drivers/media/usb/dvb-usb-v2/lmedm04.c | 2 +- 1 file changed, 1

[PATCH 3/4] [media] lmedm04: make some string arrays static

It takes more .text to initialize these on the stack than they occupy in .rodata, so just make them static const. Signed-off-by: Rasmus Villemoes --- drivers/media/usb/dvb-usb-v2/lmedm04.c | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git

[PATCH 1/4] [media] lmedm04: use %phN for hex dump

Using the %ph printf extension for hex dumps like this makes the generated code quite a bit smaller. Signed-off-by: Rasmus Villemoes --- drivers/media/usb/dvb-usb-v2/lmedm04.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git

[PATCH 4/4] [media] lmedm04: make lme2510_powerup a little smaller

gcc isn't smart enough to realize it can share most of the argument buildup and the actual function call between the two branches, so help it a little. Signed-off-by: Rasmus Villemoes --- drivers/media/usb/dvb-usb-v2/lmedm04.c | 5 + 1 file changed, 1 insertion(+),

RE: Enabling peer to peer device transactions for PCIe devices

> -Original Message- > From: Haggai Eran [mailto:hagg...@mellanox.com] > Sent: Wednesday, November 30, 2016 5:46 AM > To: Jason Gunthorpe > Cc: linux-ker...@vger.kernel.org; linux-r...@vger.kernel.org; linux- > nvd...@ml01.01.org; Koenig, Christian; Suthikulpanit, Suravee; Bridgman, >

Re: Enabling peer to peer device transactions for PCIe devices

On 30/11/16 09:23 AM, Jason Gunthorpe wrote: >> Two cases I can think of are RDMA access to an NVMe device's controller >> memory buffer, > > I'm not sure on the use model there.. The NVMe fabrics stuff could probably make use of this. It's an in-kernel system to allow remote access to an NVMe

Re: Enabling peer to peer device transactions for PCIe devices

On 2016-11-30 11:23 AM, Jason Gunthorpe wrote: Yes, that sounds fine. Can we simply kill the process from the GPU driver? Or do we need to extend the OOM killer to manage GPU pages? I don't know.. We could use send_sig_info to send signal from kernel to user space. So theoretically GPU

Re: Enabling peer to peer device transactions for PCIe devices

On Wed, Nov 30, 2016 at 12:45:58PM +0200, Haggai Eran wrote: > > That just forces applications to handle horrible unexpected > > failures. If this sort of thing is needed for correctness then OOM > > kill the offending process, don't corrupt its operation. > Yes, that sounds fine. Can we simply

[PATCH v2.2 1/2] smiapp: Implement power-on and power-off sequences without runtime PM

Power on the sensor when the module is loaded and power it off when it is removed. Signed-off-by: Sakari Ailus --- since v2.1: - Power off conditionally, i.e. only if the device was powered. pm_runtime_status_suspended() returns false if CONFIG_PM is not set.

Re: [patch] [media] uvcvideo: freeing an error pointer

On Wed, Nov 30, 2016 at 03:53:03PM +0200, Laurent Pinchart wrote: > But then you get the following patch (which, apart from being totally made > up, > probably shows what I've watched yesterday evening). > > @@ ... @@ > return -ENOMEM; > } > > + ret =

Re: [patch] [media] uvcvideo: freeing an error pointer

Hi Dan, On Wednesday 30 Nov 2016 15:33:26 Dan Carpenter wrote: > On Mon, Nov 28, 2016 at 04:49:36PM +0200, Laurent Pinchart wrote: > > On Monday 28 Nov 2016 14:54:58 Julia Lawall wrote: > >> On Mon, 28 Nov 2016, Dan Carpenter wrote: > >>> I understand the comparison, but I just think it's better

Re: [patch] [media] uvcvideo: freeing an error pointer

On Mon, Nov 28, 2016 at 04:49:36PM +0200, Laurent Pinchart wrote: > Hi Julia and Dan, > > On Monday 28 Nov 2016 14:54:58 Julia Lawall wrote: > > On Mon, 28 Nov 2016, Dan Carpenter wrote: > > > I understand the comparison, but I just think it's better if people > > > always keep track of what has

Re: [PATCH v2] [media] vivid: support for contiguous DMA buffers

On 11/22/16 14:18, Vincent ABRIOU wrote: Hi Hans, Is there any issue so that those 2 patches cannot be merged? [media] vivid: support for contiguous DMA buffer [media] uvcvideo: support for contiguous DMA buffers Lack of time, really. I'll see if I can take a look at these soonish. Regards,

Re: [PATCH v2.1 1/2] smiapp: Implement power-on and power-off sequences without runtime PM

Hi Laurent, On Tue, Nov 29, 2016 at 07:35:17PM +0200, Laurent Pinchart wrote: > Hi Sakari, > > Thank you for the patch. > > On Tuesday 29 Nov 2016 19:28:53 Sakari Ailus wrote: > > Power on the sensor when the module is loaded and power it off when it is > > removed. > > > > Signed-off-by:

Re: Enabling peer to peer device transactions for PCIe devices

On 11/28/2016 9:02 PM, Jason Gunthorpe wrote: > On Mon, Nov 28, 2016 at 06:19:40PM +, Haggai Eran wrote: GPU memory. We create a non-ODP MR pointing to VRAM but rely on user-space and the GPU not to migrate it. If they do, the MR gets destroyed immediately. >>> That sounds

Re: [PATCH] [media] adv7604: Initialize drive strength to default when using DT

Hi Lars, On 2016-11-29 12:23:48 +0100, Lars-Peter Clausen wrote: > The adv7604 driver platform data contains fields for configuring the drive > strength of the output pins. When probing the driver through DT these > fields are not explicitly initialized, which means they are left at 0. This > is

Re: ir-keytable: infinite loops, segfaults

On Sun, Nov 27, 2016 at 07:35:10PM +, Sean Young wrote: > > > I wanted to mention that the IR protocol is still showing as unknown. > > Is there anything that can be done to sort that out? > > It would be nice if that could be sorted out, although that would be > a separate patch. > > So

Re: [PATCH v4 1/4] [media] davinci: vpif_capture: don't lock over s_stream

Hi Kevin, Thank you for the patch. On Tuesday 29 Nov 2016 15:57:09 Kevin Hilman wrote: > Video capture subdevs may be over I2C and may sleep during xfer, so we > cannot do IRQ-disabled locking when calling the subdev. > > Signed-off-by: Kevin Hilman > --- >