Re: solo6010 modprobe lockup since e1ceb25a (v4.3 regression)

On Thu, 15 Sep 2016 16:19:52 +0300 Andrey Utkin wrote: > On Thu, Sep 15, 2016 at 03:15:53PM +0200, Hans Verkuil wrote: > > It could be related to the fact that a PCI write may be delayed unless > > it is followed by a read (see also the comments in > >

Re: [very-RFC 0/8] TSN driver for the kernel

On Mon, 13 Jun 2016 21:51:36 +0200 Richard Cochran wrote: > On Mon, Jun 13, 2016 at 01:47:13PM +0200, Richard Cochran wrote: > > 3. ALSA support for tunable AD/DA clocks. The rate of the Listener's > >DA clock must match that of the Talker and the other Listeners.

Re: Kernel docs: muddying the waters a bit

> DocBook is a means to an end; nobody really wants DocBook itself as far > as I can tell. We only have docbook because it was the tool of choice rather a lot of years ago to then get useful output formats. It was just inherited when borrowed the original scripts from Gnome/Gtk. It's still the

Re: [RFC] How implement Secure Data Path ?

dma-buf user handles are fds, which means anything allocated can be passed around nicely already. The question really is whether we'll have one ioctl on top of a special dev node or a syscall. I thought that in these cases where the dev node is only ever used to allocate the real thing, a

Re: [RFC] How implement Secure Data Path ?

On Thu, 7 May 2015 15:52:12 +0200 Daniel Vetter dan...@ffwll.ch wrote: On Thu, May 07, 2015 at 03:22:20PM +0200, Thierry Reding wrote: On Wed, May 06, 2015 at 03:15:32PM +0200, Daniel Vetter wrote: Yes the idea would be a special-purpose allocater thing like ion. Might even want that to

Re: [RFC] How implement Secure Data Path ?

First what is Secure Data Path ? SDP is a set of hardware features to garanty that some memories regions could only be read and/or write by specific hardware IPs. You can imagine it as a kind of memory firewall which grant/revoke accesses to memory per devices. Firewall configuration must be

Re: [RFC PATCH 0/2] managed token devres interfaces

- Construct string with (dev is struct em28xx *dev) format: tuner:%s-%s-%d with the following: dev_name(dev-udev-dev) dev-udev-bus-bus_name dev-tuner_addr What guarantees this won't get confused by hot

Re: [RFC PATCH 0/2] managed token devres interfaces

For example, some devices provide standard USB Audio Class, handled by snd-usb-audio for the audio stream, while the video stream is handled via a separate driver, like some em28xx devices. Which is what mfd is designed to handle. There are even more complex devices that provide 3G modem,