Re: em28xx broken 4.9.0-rc6+

Em Tue, 6 Dec 2016 01:06:17 +0200 Antti Palosaari escreveu: > Hello Mauro > I just noticed current em28xx driver seem to be broken. When I plug > device first time it loads correctly, but when I re-plug it, it does not > work anymore but yells a lot of noise to message log.

Re: [PATCH v2 3/3] uvcvideo: add a metadata device node

Hi Guennadi, On Tuesday 06 Dec 2016 11:39:22 Guennadi Liakhovetski wrote: > On Tue, 6 Dec 2016, Laurent Pinchart wrote: > > On Monday 05 Dec 2016 23:13:53 Guennadi Liakhovetski wrote: > >> On Tue, 6 Dec 2016, Laurent Pinchart wrote: > >> + /* > >> + * Register a metadata node.

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

Hans Verkuil writes: > On 12/01/2016 10:16 AM, Laurent Pinchart wrote: >> Hello, >> >> On Thursday 01 Dec 2016 09:57:31 Sakari Ailus wrote: >>> On Wed, Nov 30, 2016 at 04:14:11PM -0800, Kevin Hilman wrote: Sakari Ailus writes: > On Wed, Nov 23,

[PATCH for v4.10] cec: fix report_current_latency

In the (very) small print of the REPORT_CURRENT_LATENCY message there is a line that says that the last byte of the message (audio out delay) is only present if the 'audio out compensated' value is 3. I missed this, and so if this message was sent with a total length of 6 (i.e. without the

Intel SR300 Depth Camera formats

Changelog for v2: 1. The patch has been rearranged, so instead of separation into "Code" and "Documentation" segments it is built around: - Adding new INZI format definition to V4L2_API - Adding support for SR300 camera formats. 2. Tables used in the documentation were

[PATCH 1/2 v2] media: Adding 'INZI' Depth data format to V4L2_API.

From: Aviv Greenberg This is a proprietary multi-plane format that provides Infrared and Depth data. The format is utilized by Intel SR300 depth camera. The patch comprises of the format definition to be introduced into V4L2_API via include/uapi/linux/videodev2.h, and the

Re: Enabling peer to peer device transactions for PCIe devices

On Tue, Dec 06, 2016 at 09:38:50AM -0700, Jason Gunthorpe wrote: > > > I'm not opposed to mapping /dev/nvmeX. However, the lookup is trivial > > > to accomplish in sysfs through /sys/dev/char to find the sysfs path of the > > > device-dax instance under the nvme device, or if you already have the

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

Hi Takashi, On 12/05/2016 11:50 PM, Takashi Iwai wrote: > On Wed, 30 Nov 2016 23:01:16 +0100, > Shuah Khan wrote: >> >> --- a/sound/usb/card.c >> +++ b/sound/usb/card.c > (snip) >> @@ -616,6 +617,11 @@ static int usb_audio_probe(struct usb_interface *intf, >> if (err < 0) >>

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: Wed Dec 7 05:00:17 CET 2016 media-tree git hash:365fe4e0ce218dc5ad10df17b150a366b6015499 media_build

Re: [PATCH 3/8] [media] lirc: LIRC_{G,S}ET_SEND_MODE fail if device cannot transmit

Reviewed-by: Andi Shyti On Fri, Dec 02, 2016 at 05:16:09PM +, Sean Young wrote: > These ioctls should not succeed if the device cannot send. Also make it > clear that these ioctls should return the lirc mode, although the actual > value does not change. > >

Re: [PATCH 1/8] [media] mceusb: LIRC_SET_SEND_CARRIER returns 0 on success

Reviewed-by: Andi Shyti On Fri, Dec 02, 2016 at 05:16:07PM +, Sean Young wrote: > LIRC_SET_SEND_CARRIER ioctl should not return the carrier used, it > should return 0. > > Signed-off-by: Sean Young > --- > drivers/media/rc/mceusb.c | 4 ++-- > 1 file

[PATCH v7 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 v7 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 --- No changes since v6 drivers/media/usb/au0828/au0828-core.c | 12

[PATCH v7 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

[PATCH v5 1/5] [media] davinci: VPIF: fix module loading, init errors

Fix problems with automatic module loading by adding MODULE_ALIAS. Also fix various load-time errors cause by incorrect or not present platform_data. Signed-off-by: Kevin Hilman --- drivers/media/platform/davinci/vpif.c | 5 -

[PATCH v5 0/5] davinci: VPIF: add DT support

Prepare the groundwork for adding DT support for davinci VPIF drivers. This series does some fixups/cleanups and then adds the DT binding and DT compatible string matching for DT probing. The controversial part from previous versions around async subdev parsing, and specifically hard-coding the

[PATCH v5 3/5] [media] davinci: vpif_capture: fix start/stop streaming locking

Video capture subdevs may be over I2C and may sleep during xfer, so we cannot do IRQ-disabled locking when calling the subdev. The IRQ-disabled locking is meant to protect the DMA queue list throughout the rest of the driver, so update the locking in [start|stop]_streaming to protect just this

[PATCH v5 2/5] [media] davinci: vpif_capture: remove hard-coded I2C adapter id

Remove hard-coded I2C adapter in favor of getting the ID from platform_data. Signed-off-by: Kevin Hilman --- drivers/media/platform/davinci/vpif_capture.c | 5 - include/media/davinci/vpif_types.h| 1 + 2 files changed, 5 insertions(+), 1 deletion(-) diff

[PATCH v5 4/5] [media] dt-bindings: add TI VPIF documentation

Acked-by: Rob Herring Signed-off-by: Kevin Hilman --- .../devicetree/bindings/media/ti,da850-vpif.txt| 67 ++ 1 file changed, 67 insertions(+) create mode 100644 Documentation/devicetree/bindings/media/ti,da850-vpif.txt diff --git

[PATCH v5 5/5] [media] davinci: VPIF: add basic support for DT init

Add basic support for initialization via DT Signed-off-by: Kevin Hilman --- drivers/media/platform/davinci/vpif.c | 9 + 1 file changed, 9 insertions(+) diff --git a/drivers/media/platform/davinci/vpif.c b/drivers/media/platform/davinci/vpif.c index

[PATCH v7 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

Re: [PATCH 2/8] [media] lirc_dev: LIRC_{G,S}ET_REC_MODE do not work

> Since "273b902 [media] lirc_dev: use LIRC_CAN_REC() define" these > ioctls no longer work. > > Signed-off-by: Sean Young > Cc: Andi Shyti > Cc: # v4.8+ mmhhh... yes, right! :) Reviewed-by: Andi Shyti

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

Laurent Pinchart writes: > 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. >> >>

Re: Enabling peer to peer device transactions for PCIe devices

> > I'm not opposed to mapping /dev/nvmeX. However, the lookup is trivial > > to accomplish in sysfs through /sys/dev/char to find the sysfs path of the > > device-dax instance under the nvme device, or if you already have the nvme > > sysfs path the dax instance(s) will appear under the "dax"

[PATCH 2/2 v2] uvcvideo : Add support for Intel SR300 depth camera

From: Aviv Greenberg Add support for Intel SR300 depth camera formats in uvc driver. This includes adding three uvc GUIDs for pixel formats advertised by device, and their mapping to the proper FourCC definitions. Signed-off-by: Aviv Greenberg Signed-off-by:

Re: Enabling peer to peer device transactions for PCIe devices

Hey, On 06/12/16 09:38 AM, Jason Gunthorpe wrote: >>> I'm not opposed to mapping /dev/nvmeX. However, the lookup is trivial >>> to accomplish in sysfs through /sys/dev/char to find the sysfs path of the >>> device-dax instance under the nvme device, or if you already have the nvme >>> sysfs path

Re: Enabling peer to peer device transactions for PCIe devices

On Tue, Dec 06, 2016 at 09:51:15AM -0700, Logan Gunthorpe wrote: > Hey, > > On 06/12/16 09:38 AM, Jason Gunthorpe wrote: > >>> I'm not opposed to mapping /dev/nvmeX. However, the lookup is trivial > >>> to accomplish in sysfs through /sys/dev/char to find the sysfs path of the > >>> device-dax

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

On Tue, 06 Dec 2016 19:41:37 +0100, Shuah Khan wrote: > > Hi Takashi, > > On 12/05/2016 11:50 PM, Takashi Iwai wrote: > > On Wed, 30 Nov 2016 23:01:16 +0100, > > Shuah Khan wrote: > >> > >> --- a/sound/usb/card.c > >> +++ b/sound/usb/card.c > > (snip) > >> @@ -616,6 +617,11 @@ static int

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

On Fri, Dec 02, 2016 at 10:15:27AM +0530, Shailendra Verma wrote: > 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 > --- >

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

On Tue, Dec 6, 2016 at 9:40 AM, Kevin Hilman wrote: > Hans Verkuil writes: > >> On 12/01/2016 10:16 AM, Laurent Pinchart wrote: >>> Hello, >>> >>> On Thursday 01 Dec 2016 09:57:31 Sakari Ailus wrote: On Wed, Nov 30, 2016 at 04:14:11PM -0800, Kevin

DVB CAM did not respond / DVBSky S960CI + SmarCAM-3 CI Plus

Hello everybody! This is my very first message here, so first of all, thank you all for your participation in this project. I really do appreciate it! Still I'm looking for some advice.. I bought DVBsky S960CI (DVB-S2), managed to install drivers, VDR, plugins etc on my Linux systems and I can

Re: [PATCH v2] v4l: async: make v4l2 coexist with devicetree nodes in a dt overlay

On Mon, Dec 05, 2016 at 10:13:38AM -0300, Javier Martinez Canillas wrote: > Hello Javi, > > On 12/05/2016 07:09 AM, Javi Merino wrote: > > In asds configured with V4L2_ASYNC_MATCH_OF, the v4l2 subdev can be > > part of a devicetree overlay, for example: > > > > _bridge { > > ... > >

[PATCH 0/4] v4l: vsp1: Fix suspend/resume and race on M2M pipelines

This small patchset helps rework the VSP1 driver to repair an issue on suspend/resume operations whereby the pipeline does not get reconfigured after it has been re-initialised following a resume operation. Along side this, there was an intrinsic race in the vsp1_video_start_streaming() function

[PATCH 3/4] v4l: vsp1: Use local display lists and remove global pipe->dl

The usage of pipe->dl is susceptible to races, and it is redundant to keep this pointer in a larger scoped context. Now that the calling order of vsp1_video_setup_pipeline() has been adapted, it is possible to remove the pipe->dl and pass the variable as required. Currently the pipe->dl is set

[PATCH 1/4] v4l: vsp1: Move vsp1_video_setup_pipeline()

Move the static vsp1_video_setup_pipeline() function in preparation for the callee updates so that the vsp1_video_pipeline_run() call can configure pipelines following suspend resume actions. This commit is just a code move for clarity performing no functional change. Signed-off-by: Kieran

[PATCH 2/4] v4l: vsp1: Refactor video pipeline configuration

With multiple inputs through the BRU it is feasible for the streams to race each other at stream-on. In the case of the video pipelines, this can present two serious issues. 1) A null-dereference if the pipe->dl is committed at the same time as the vsp1_video_setup_pipeline() is processing

[PATCH RFC 4/4] media: Catch null pipes on pipeline stop

media_entity_pipeline_stop() can be called through error paths with a NULL entity pipe object. In this instance, stopping is a no-op, so simply return without any action Signed-off-by: Kieran Bingham --- I've marked this patch as RFC, although if deemed

Re: Enabling peer to peer device transactions for PCIe devices

>>> I've already recommended that iopmem not be a block device and >>> instead be a device-dax instance. I also don't think it should claim >>> the PCI ID, rather the driver that wants to map one of its bars this >>> way can register the memory region with the device-dax core. >>> >>> I'm not sure

[PATCH v4 07/13] [media] rc: rc-ir-raw: Add pulse-distance modulation helper

From: James Hogan Add IR encoding helper for pulse-distance modulation as used by the NEC protocol. Signed-off-by: James Hogan Signed-off-by: Sean Young Cc: Antti Seppälä Cc: David Härdeman ---

[PATCH v4 11/13] [media] rc: rc-core: Add support for encode_wakeup drivers

From: James Hogan Add support in rc-core for drivers which implement the wakeup scancode filter by encoding the scancode using the raw IR encoders. This is by way of rc_dev::encode_wakeup which should be set to true to make the allowed wakeup protocols the same as the set of

[PATCH v4 04/13] [media] rc: raw IR drivers cannot handle cec, unknown or other

unknown and other are for IR protocols for which we have no decoder, so the raw IR drivers have no chance of generating them. cec is not an IR protocol. Signed-off-by: Sean Young --- drivers/hid/hid-picolcd_cir.c | 2 +- drivers/media/common/siano/smsir.c |

[PATCH v4 13/13] [media] rc: nuvoton-cir: Add support wakeup via sysfs filter callback

From: Antti Seppälä Nuvoton-cir utilizes the encoding capabilities of rc-core to convert scancodes from user space to pulse/space format understood by the underlying hardware. Converted samples are then written to the wakeup fifo along with other necessary configuration to

[PATCH v4 10/13] [media] rc: ir-nec-decoder: Add encode capability

From: James Hogan Add the capability to encode NEC scancodes as raw events. The scancode_to_raw is pretty much taken from the img-ir NEC filter() callback, and modulation uses the pulse distance helper added in a previous commit. Signed-off-by: James Hogan

[PATCH v4 03/13] [media] winbond-cir: use sysfs wakeup filter

Now that we can select the exact variant of the protocol for wakeup filter, the winbond-cir can use the wakeup filter rather than module parameters. Signed-off-by: Sean Young --- drivers/media/rc/winbond-cir.c | 252 - 1 file changed, 125

[PATCH v4 09/13] [media] rc: ir-rc6-decoder: Add encode capability

From: Antti Seppälä Add the capability to encode RC-6 and RC-6A scancodes as raw events. The protocol is chosen based on the specified protocol mask, and whether all the required bits are set in the scancode mask, and none of the unused bits are set in the scancode data.

[PATCH v4 00/13] Use sysfs filter for winbond & nuvoton wakeup

This patch series resurrects an earlier series with a new approach. I've modified wakeup_protocols so that only one protocol variant can be selected, and the ir_raw_encode_scancode() now takes an enum rc_type rather than a protocol bitmask. These changes make it possible for the winbond-cir to

[PATCH v4 01/13] [media] rc: change wakeup_protocols to list all protocol variants

No driver has ever created a wakeup_protocol sysfs file since no rc_dev driver implemented change_wakeup_protocol, so we are free to change it. For IR wakeup a driver has to program the hardware to wakeup at a specific IR sequence, so it makes no sense to allow multiple wakeup protocols to be

[PATCH v4 02/13] [media] rc: Add scancode validation

We need to valdiate that scancodes are valid for their protocol; an incorrect necx scancode could actually be a nec scancode, for example. Signed-off-by: Sean Young --- drivers/media/rc/rc-main.c | 66 +- 1 file changed, 65

[PATCH v4 05/13] [media] rc: rc-ir-raw: Add scancode encoder callback

From: James Hogan Add a callback to raw ir handlers for encoding and modulating a scancode to a set of raw events. This could be used for transmit, or for converting a wakeup scancode filter to a form that is more suitable for raw hardware wake up filters. Signed-off-by:

[PATCH v4 06/13] [media] rc: rc-ir-raw: Add Manchester encoder (phase encoder) helper

From: Antti Seppälä Adding a simple Manchester encoder to rc-core. Manchester coding is used by at least RC-5 and RC-6 protocols and their variants. Signed-off-by: Antti Seppälä Signed-off-by: James Hogan Signed-off-by: Sean Young

[PATCH v4 08/13] [media] rc: ir-rc5-decoder: Add encode capability

From: James Hogan Add the capability to encode RC-5, RC-5X and RC-5-SZ scancodes as raw events. The protocol is chosen based on the specified protocol mask, and whether all the required bits are set in the scancode mask, and none of the unused bits are set in the scancode

[PATCH v4 12/13] [media] rc: rc-loopback: Add loopback of filter scancodes

From: James Hogan Add the s_wakeup_filter callback to the rc-loopback driver, which instead of setting the filter just feeds the scancode back through the input device so that it can be verified. Signed-off-by: James Hogan Signed-off-by: Antti Seppälä

[PATCH 2/3] tc358743: Disable HDCP with "manual HDCP authentication" bit

From: Mats Randgaard Originally Toshiba told us that the only way to disable HDCP was to set the receiver in repeater mode, that would make the authentication fail because of missing software support. It has worked fine with all the sources we and our customers has used,

[PATCH 3/3] tc358743: ctrl_detect_tx_5v should always be updated

From: Mats Randgaard The control for +5V Power detection must also be updated when the EDID is not present. Signed-off-by: Mats Randgaard --- drivers/media/i2c/tc358743.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/media/i2c/tc358743.c

[PATCH 1/3] tc358743: Do not read number of CSI lanes in use from chip

From: Mats Randgaard The number of CSI lanes that should be used is set to the CSI_CONTROL register by indirectly writing to the CSI_CONFW register. When the number of lanes is read back from the CSI_CONTROL register the value is usually correct, but we have seen that it

Re: [PATCH v2 3/3] uvcvideo: add a metadata device node

Hi Laurent, On Tue, 6 Dec 2016, Laurent Pinchart wrote: > Hi Guennadi, > > On Monday 05 Dec 2016 23:13:53 Guennadi Liakhovetski wrote: > > Just one question: > > > > On Tue, 6 Dec 2016, Laurent Pinchart wrote: > > + /* > > + * Register a metadata node. TODO: shall this

Re: [PATCH v3 3/4] stk1160: Add module param for setting the record gain.

Em Mon, 5 Dec 2016 22:06:59 +0100 Marcel Hasler escreveu: > Hello > > 2016-12-05 16:38 GMT+01:00 Ezequiel Garcia : > > On 5 December 2016 at 09:12, Mauro Carvalho Chehab > > wrote: > >> Em Sun, 4 Dec 2016 15:25:25

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

Hi Shuah, On Monday 05 Dec 2016 17:38:23 Shuah Khan wrote: > On 12/05/2016 04:21 PM, Laurent Pinchart wrote: > > On Monday 05 Dec 2016 15:44:30 Shuah Khan wrote: > >> On 11/30/2016 03:01 PM, Shuah Khan wrote: > >>> Change ALSA driver to use Media Controller API to share media resources > >>> with

Re: [PATCH v2] v4l: async: make v4l2 coexist with devicetree nodes in a dt overlay

(resending, hopefully now it reaches the mailing lists) On 12/05/2016 11:09 AM, Javi Merino wrote: > Each time the overlay is applied, its of_node pointer will be > different. We are not interested in matching the pointer, what we > want to match is that the path is the one we are expecting.

Re: Enabling peer to peer device transactions for PCIe devices

Hey, > Okay, so clearly this needs a kernel side NVMe specific allocator > and locking so users don't step on each other.. Yup, ideally. That's why device dax isn't ideal for this application: it doesn't provide any way to prevent users from stepping on each other. > Or as Christoph says some

Re: Enabling peer to peer device transactions for PCIe devices

On Tue, Dec 6, 2016 at 1:47 PM, Logan Gunthorpe wrote: > Hey, > >> Okay, so clearly this needs a kernel side NVMe specific allocator >> and locking so users don't step on each other.. > > Yup, ideally. That's why device dax isn't ideal for this application: it > doesn't