Hi Jan, linux-usb list,
I'm hitting this warning consistently on my Raspberry Pi 3 running kernel
v4.10.1 with some unrelated device tree changes, and a debug print (below).
The device identifies as "GlobeTrotter HSDPA Modem", VID: 0af0, PID: 6971.
The warning triggers consistently on first writ
On 2/27/2017 11:55 PM, Francesco Lavra wrote:
> Hi,
>
> On 02/23/2017 08:27 PM, Heiko Stuebner wrote:
>> Hi Francesco,
>>
>> Am Donnerstag, 23. Februar 2017, 19:11:37 CET schrieb Francesco Lavra:
>>> I'm having trouble getting the RK3288 OTG controller (the one at
>>> ff58) to work in periphera
The email address of Jan Dumon bounces, and there is not relevant information
in the linked website.
Signed-off-by: Baruch Siach
---
MAINTAINERS | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 056f157122c9..e65f709cb795 100644
--- a/MAINTA
Brauchen Sie ein Darlehen, um eine Rechnung zu bezahlen oder ein Geschäft zu
gründen? Schreiben Sie uns eine E-Mail
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo
Dear Linux folks,
The USB Bluetooth device 8087:0a2b is used in quite a lot of portable
devices. In my case it’s the TUXEDO Book BU1406 [1]. I am trying to
decrease the overall (suspend and) resume time of the Linux kernel.
```
$ more /proc/version
Linux version 4.10.0+ (helmuth@helmuth-N24-
Dear Greg,
On 02/28/17 12:00, Greg KH wrote:
On Tue, Feb 28, 2017 at 11:20:11AM +0100, Paul Menzel wrote:
Is there a way to debug and optimize that – besides taking the device out –
to get resume times on par with other devices like Google Chromebooks or
Apple MacBooks?
A Chromebook is runni
On Tue, Feb 28, 2017 at 11:20:11AM +0100, Paul Menzel wrote:
> Is there a way to debug and optimize that – besides taking the device out –
> to get resume times on par with other devices like Google Chromebooks or
> Apple MacBooks?
A Chromebook is running the same Linux kernel as your desktop, so
On Mo, 2017-02-27 at 16:27 -0600, Rob Herring wrote:
> On Mon, Feb 27, 2017 at 3:48 AM, Jan Lübbe wrote:
> > On Di, 2017-02-21 at 15:57 +0100, Richard Leitner wrote:
> >> >>> This is a lot of properties. Are you really finding a need for all of
> >> >>> them? Is this to handle h/w designers too ch
Dear mailing list,
first a short summary of my hardware, the system and the issue itself.
Hardware: Fujitsu S920 Thin Client
CPU/SOC: AMD GX-217GC SOC
Mainboard: FUJITSU Mainboard D3313-S, [1]
Connected usb devices: FTS keyboard 0bf8:100c, Logitech mouse 046d:c077
Currently I am using kernel 4.
Hi Vardan,
On 02/28/2017 09:41 AM, Vardan Mikayelyan wrote:
On 2/27/2017 11:55 PM, Francesco Lavra wrote:
Hi,
On 02/23/2017 08:27 PM, Heiko Stuebner wrote:
Hi Francesco,
Am Donnerstag, 23. Februar 2017, 19:11:37 CET schrieb Francesco Lavra:
I'm having trouble getting the RK3288 OTG controll
Hi,
Alan Stern writes:
>> So I am not sure how the Gadget driver can figure out that it needs to
>> usb_ep_queue() another request for status stage when handling the
>> no-data control?
>
> Gadget drivers already queue status-stage requests for no-data
> control-OUT requests. The difficulty com
Hi linux-usb list,
(Dropped Jan's bouncing address, added Rpi3 platform lists)
On Tue, Feb 28, 2017 at 10:28:10AM +0200, Baruch Siach wrote:
> Hi linux-usb list,
>
> I'm hitting this warning consistently on my Raspberry Pi 3 running kernel
> v4.10.1 with some unrelated device tree changes, and
Dear Greg,
On 02/28/17 13:39, Greg KH wrote:
On Tue, Feb 28, 2017 at 12:06:38PM +0100, Paul Menzel wrote:
On 02/28/17 12:00, Greg KH wrote:
On Tue, Feb 28, 2017 at 11:20:11AM +0100, Paul Menzel wrote:
Is there a way to debug and optimize that – besides taking the device out –
to get resume
On Tue, Feb 28, 2017 at 12:06:38PM +0100, Paul Menzel wrote:
> Dear Greg,
>
>
> On 02/28/17 12:00, Greg KH wrote:
> > On Tue, Feb 28, 2017 at 11:20:11AM +0100, Paul Menzel wrote:
> > > Is there a way to debug and optimize that – besides taking the device out
> > > –
> > > to get resume times on
When binding a gadget to a device, "name" is stored in gi->udc_name, but
this does not happen when unregistering and the string is leaked.
Signed-off-by: John Keeping
---
drivers/usb/gadget/configfs.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/gadget/configfs.c b/drivers/usb
The "event_char" device attribute value, when written, is interpreted as
an enable bit in bit 8, and an "event character" in bits 7 to 0. Return
an error for out-of-range values.
Signed-off-by: Ian Abbott
---
drivers/usb/serial/ftdi_sio.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/d
Valid latency timer values are between 1 ms and 255 ms in 1 ms steps.
The store function for the "latency_timer" device attribute currently
allows any value, although only the lower 8-bits will be written to the
latency timer. Return an error for out-of-range values.
Signed-off-by: Ian Abbott
--
The 'store' function for the "event_char" device attribute currently
expects a base 10 value. The value is composed of an enable bit in bit
8 and an 8-bit "event character" code in bits 7 to 0. It seems
reasonable to allow hexadecimal and octal numbers to be written to the
device attribute in add
Some patches to skip accessing the FTDI latency timer on chips that
don't support it, detect "BM" chips with iSerialNumber bug, validate
written device attribute values, and allow hex and octal "event_char"
values.
1) USB: serial: ftdi_sio: don't access latency timer on old chips
2) USB: serial: f
The latency timer was introduced with the FT232BM and FT245BM chips. Do
not bother attempting to read or write it for older chip versions.
Signed-off-by: Ian Abbott
---
drivers/usb/serial/ftdi_sio.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/usb/serial/ftdi_sio.c b/driver
If a BM type chip has iSerialNumber set to 0 in its EEPROM, an incorrect
value is read from the bcdDevice field of the USB descriptor, making it
look like an AM type chip. Attempt to correct this in
ftdi_determine_type() by attempting to read the latency timer for an AM
type chip. If that succeed
Replace the obsolete simple_strtoul() calls with kstrtouint() calls.
Signed-off-by: Ian Abbott
---
drivers/usb/serial/ftdi_sio.c | 14 +++---
1 file changed, 11 insertions(+), 3 deletions(-)
diff --git a/drivers/usb/serial/ftdi_sio.c b/drivers/usb/serial/ftdi_sio.c
index 2662fc3b49c5..e
From: Colin Ian King
The call to asix_write_medium_mode is not updating the return code ret
and yet ret is being checked for an error. Fix this by assigning ret to
the return code from the call asix_write_medium_mode.
Detected by CoverityScan, CID#1357148 ("Logically Dead Code")
Signed-off-by:
On 2/28/2017 3:44 PM, Francesco Lavra wrote:
> Hi Vardan,
>
> On 02/28/2017 09:41 AM, Vardan Mikayelyan wrote:
>> On 2/27/2017 11:55 PM, Francesco Lavra wrote:
>>> Hi,
>>>
>>> On 02/23/2017 08:27 PM, Heiko Stuebner wrote:
Hi Francesco,
Am Donnerstag, 23. Februar 2017, 19:11:37 CET sc
On 28/02/17 10:55, John Keeping wrote:
When binding a gadget to a device, "name" is stored in gi->udc_name, but
this does not happen when unregistering and the string is leaked.
Signed-off-by: John Keeping
---
drivers/usb/gadget/configfs.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/dr
On Sat, Feb 25, 2017 at 9:20 AM, Chanwoo Choi wrote:
> 2017-02-25 12:46 GMT+09:00 Chanwoo Choi :
>> Hi,
>>
>> 2017-02-24 21:02 GMT+09:00 Roger Quadros :
>>> +Chanwoo
>>>
>>> Hi Vivek,
>>>
>>> On 23/02/17 10:34, Vivek Gautam wrote:
On 02/16/2017 06:36 PM, Roger Quadros wrote:
> d
From: Ian Abbott
> Sent: 28 February 2017 12:51
> The 'store' function for the "event_char" device attribute currently
> expects a base 10 value. The value is composed of an enable bit in bit
> 8 and an 8-bit "event character" code in bits 7 to 0. It seems
> reasonable to allow hexadecimal and oc
On 28/02/17 14:21, David Laight wrote:
From: Ian Abbott
Sent: 28 February 2017 12:51
The 'store' function for the "event_char" device attribute currently
expects a base 10 value. The value is composed of an enable bit in bit
8 and an 8-bit "event character" code in bits 7 to 0. It seems
reason
On 25/02/17 05:35, Chanwoo Choi wrote:
> Hi Roger,
>
> [snip]
>
>> /* dwc->lock must be held */
>> static void dwc3_otg_core_exit(struct dwc3 *dwc)
>> {
>> + if (dwc->edev)
>> + return;
>> +
>> /* disable all otg irqs */
>> dwc3_otg_disable_events(dwc, DWC3_
From: Baruch Siach
Date: Tue, 28 Feb 2017 10:39:48 +0200
> The email address of Jan Dumon bounces, and there is not relevant information
> in the linked website.
>
> Signed-off-by: Baruch Siach
This patch is fine and I will apply it later, however I will make a
general statement that we list U
On 02/23/2017 08:51 AM, Greg KH wrote:
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/20
On Tue, 2017-02-28 at 14:01 +0200, Baruch Siach wrote:
> Hi linux-usb list,
>
> (Dropped Jan's bouncing address, added Rpi3 platform lists)
>
> On Tue, Feb 28, 2017 at 10:28:10AM +0200, Baruch Siach wrote:
> > Hi linux-usb list,
> >
> > I'm hitting this warning consistently on my Raspberry Pi 3
Hi Baruch,
Am 28.02.2017 um 13:01 schrieb Baruch Siach:
Hi linux-usb list,
(Dropped Jan's bouncing address, added Rpi3 platform lists)
On Tue, Feb 28, 2017 at 10:28:10AM +0200, Baruch Siach wrote:
Hi linux-usb list,
I'm hitting this warning consistently on my Raspberry Pi 3 running kernel
v4
On Tue, 28 Feb 2017, Peter Chen wrote:
> When the user does device unbind and rebind test, the kernel will
> show below dump due to usb_gadget memory region is dirty after unbind.
> Clear usb_gadget region for every new probe.
>
> root@imx6qdlsolo:/sys/bus/platform/drivers/dummy_udc# echo dummy_u
On Feb 25 2017 or thereabouts, Tobias Jakobi wrote:
> For mouse devices we can currently change the polling interval
> via usbhid.mousepoll. Implement the same thing for joysticks, so
> users can reduce input latency this way.
>
> This has been tested with a Logitech RumblePad 2 with jspoll=2,
> r
On Feb 15 2017 or thereabouts, Jaejoong Kim wrote:
> When HID device connected to the PC, HID device driver announces which
> driver is loaded with a kernel info message. In this case, hiddev's minor
> number is always '0' even though hiddev's real minor number is not zero.
>
> To display hiddev w
Hi,
well, not to undermine your work, I am not a big fan of this kind of
patches. Yes, it's nice to follow checkpatch, but on some rare case, we
just ignore the warning because the end result would be too ugly (I
haven't read the patch, so I am not judging how you solved the issues
raised here and
On Tue, Feb 28, 2017 at 10:38:44AM -0500, David Miller wrote:
> From: Baruch Siach
> Date: Tue, 28 Feb 2017 10:39:48 +0200
>
> > The email address of Jan Dumon bounces, and there is not relevant
> > information
> > in the linked website.
> >
> > Signed-off-by: Baruch Siach
>
> This patch is f
Hi Baruch,
> Baruch Siach hat am 28. Februar 2017 um 19:07 geschrieben:
>
>
> Hi Stefan,
>
> On Tue, Feb 28, 2017 at 05:21:18PM +0100, Stefan Wahren wrote:
> > Am 28.02.2017 um 13:01 schrieb Baruch Siach:
> > > On Tue, Feb 28, 2017 at 10:28:10AM +0200, Baruch Siach wrote:
> > > > I'm hitting t
On Tue, 28 Feb 2017, Felipe Balbi wrote:
>
> Hi,
>
> Alan Stern writes:
> >> So I am not sure how the Gadget driver can figure out that it needs to
> >> usb_ep_queue() another request for status stage when handling the
> >> no-data control?
> >
> > Gadget drivers already queue status-stage requ
Hi Stefan,
On Tue, Feb 28, 2017 at 05:21:18PM +0100, Stefan Wahren wrote:
> Am 28.02.2017 um 13:01 schrieb Baruch Siach:
> > On Tue, Feb 28, 2017 at 10:28:10AM +0200, Baruch Siach wrote:
> > > I'm hitting this warning consistently on my Raspberry Pi 3 running
> > > kernel
> > > v4.10.1 with some
Remove the useless variable 'partial' storing the actual length
transferred. Nothing was done with it, so simply get rid of it
as usb_stor_bulk_transfer_buf can handle having NULL instead.
This also fixes the following sparse issues (-Wtypesign):
drivers/usb/storage/karma.c:122:51: warning: incorr
On Tue, 28 Feb 2017, Tobias Jakobi wrote:
> This USB-SATA bridge chip is used in a StarTech enclosure for
> optical drives.
>
> Without the quirk MakeMKV fails during the key exchange with an
> installed BluRay drive:
> > Error 'Scsi error - ILLEGAL REQUEST:COPY PROTECTION KEY EXCHANGE FAILURE -
This adds a new configfs attribute named `use_ms_rndiscmp`. It is a
boolean value that is used to select the class/subclass/protocol used
by the RNDIS function interface association descriptor. By default,
this is 0x02 (Comm), 0x06 (Ethernet), 0xff (None). When the
use_ms_rndiscmp attribute is set
On Tue, Feb 28, 2017 at 11:07:08AM -0500, Alan Stern wrote:
> On Tue, 28 Feb 2017, Peter Chen wrote:
>
> > When the user does device unbind and rebind test, the kernel will
> > show below dump due to usb_gadget memory region is dirty after unbind.
> > Clear usb_gadget region for every new probe.
>
dwc3_log_msg trace class isn't used any more. Suggest to remove it.
Signed-off-by: Lu Baolu
---
drivers/usb/dwc3/trace.h | 25 -
1 file changed, 25 deletions(-)
diff --git a/drivers/usb/dwc3/trace.h b/drivers/usb/dwc3/trace.h
index 2b124f9..69671e4 100644
--- a/drivers/u
On Tue, Feb 28, 2017 at 04:57:46PM +0100, Krzysztof Opasiak wrote:
> >On Thu, Feb 23, 2017 at 07:43:23AM +, Du, Yuyang wrote:
> >>Oh, then let me try to simplify it, what if it's an only USB 3.0 device?
> >
> >I have a USB keyboard around here somewhere that is a "USB 3.0" device,
> >that is ru
On 02/28/2017 02:44 PM, Vardan Mikayelyan wrote:
On 2/28/2017 3:44 PM, Francesco Lavra wrote:
Hi Vardan,
On 02/28/2017 09:41 AM, Vardan Mikayelyan wrote:
On 2/27/2017 11:55 PM, Francesco Lavra wrote:
Hi,
On 02/23/2017 08:27 PM, Heiko Stuebner wrote:
Hi Francesco,
Am Donnerstag, 23. Februar
48 matches
Mail list logo
