From: Krzysztof Opasiak
Device qualifier descriptor is now generated by composite.c
code. So let's fix this old comment by removing parts which
are no longer valid.
Signed-off-by: Krzysztof Opasiak
Signed-off-by: Krzysztof Opasiak
---
drivers/usb/gadget/function/storage_common.c | 4 +---
1 f
From: Krzysztof Opasiak
This descriptor is never used. Currently device qualifier
descriptor is generated by compossite code so no need to
keep it in function file.
Signed-off-by: Krzysztof Opasiak
Signed-off-by: Krzysztof Opasiak
---
drivers/usb/gadget/function/f_uac2.c | 12
1
From: Krzysztof Opasiak
This descriptor is never used. Currently device qualifier
descriptor is generated by compossite code, so no need to
keep it in function file.
Signed-off-by: Krzysztof Opasiak
Signed-off-by: Krzysztof Opasiak
---
drivers/usb/gadget/function/f_printer.c | 8
1 f
Submitters of device tree binding documentation may forget to CC
the subsystem maintainer if this is missing.
Signed-off-by: Geert Uytterhoeven
Cc: Greg Kroah-Hartman
Cc: linux-usb@vger.kernel.org
---
Please apply this patch directly if you want to be involved in device
tree binding documentatio
With commit 198de51dbc3454d95b015ca0a055b673f85f01bb, uas no longer
set `queue_depth` with scsi_change_queue_depth(), so now `queue_depth`
of UAS drives are 1. Even though `can_queue` is set to
`devinfo->qdepth - 2`, but apparently that does not help, since I can
see performance impact.
Suppose li
Btw, I suppose `.can_queue = MAX_CMNDS` in the host template is
unnecessary (unless we are going to revert `shost->can_queue =
devinfo->qdepth - 2`)?
On 22 May 2016 at 18:39, Tom Yan wrote:
> With commit 198de51dbc3454d95b015ca0a055b673f85f01bb, uas no longer
> set `queue_depth` with scsi_change_
v3.20 doesn't exist, it is actually v4.0.
Signed-off-by: Alexandre Belloni
---
Resend using correct address for Felipe
Documentation/ABI/testing/configfs-usb-gadget-uvc | 58 +++
1 file changed, 29 insertions(+), 29 deletions(-)
diff --git a/Documentation/ABI/testing/config
Hi Oliver,
On 05/20/2016 11:43 PM, Oliver Neukum wrote:
On Fri, 2016-05-20 at 22:51 -0700, Guenter Roeck wrote:
On 05/20/2016 06:37 AM, Oliver Neukum wrote:
On Fri, 2016-05-20 at 14:24 +0300, Heikki Krogerus wrote:
On Thu, May 19, 2016 at 04:47:17PM +0200, Oliver Neukum wrote:
Please explai
http://lkml.iu.edu/hypermail/linux/kernel/1512.0/04117.html
http://lkml.iu.edu/hypermail/linux/kernel/1512.0/04831.html
Same issue here with kernel 4.4.10 and 4.5.4 and r8153. Mine is an USB 3.0
Hub with Gigabit Ethernet, so the common point seems to be USB 3.0. For me
it only happens when play
On Sat, May 21, 2016 at 10:29:40AM +0800, Peter Chen wrote:
> On Thu, May 19, 2016 at 10:32:44AM +0300, Roger Quadros wrote:
> > On 18/05/16 17:46, Jun Li wrote:
> > >
> > >
> >
> > I didn't want to have complex Kconfig so decided to have otg as
> > built-in only.
> > What do
On Sun, 2016-05-22 at 08:54 -0700, Guenter Roeck wrote:
> Hi Oliver,
>
> On 05/20/2016 11:43 PM, Oliver Neukum wrote:
> > On Fri, 2016-05-20 at 22:51 -0700, Guenter Roeck wrote:
> >> On 05/20/2016 06:37 AM, Oliver Neukum wrote:
> >>> On Fri, 2016-05-20 at 14:24 +0300, Heikki Krogerus wrote:
>
It's unlikely that we will ever know the avg so
instead of assuming it'll be something really large,
we will calculate the avg as we go as mentioned in
XHCI specification section 4.14.1.1.
Signed-off-by: Felipe Balbi
---
drivers/usb/host/xhci-mem.c | 34 --
drive
when getting endpoint type a switch statement looks
better than a series of if () branches. There are no
functional changes with this patch, cleanup only.
Signed-off-by: Felipe Balbi
---
drivers/usb/host/xhci-mem.c | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/dr
13 matches
Mail list logo
