CISCO AND AVAYA IP Phones

Hi, Clean tested working pulls CPUs and QTYs in stock. 115 X X5650 65 X E5410 75 X X5660 145 X E5530 100 X E5645 40 X X5680 75 X X5690 Brand new sealed IP phones and QTYs in stock. 55 x CP-7937G 77 x CP-7942G 54 x CP-7945G 75 x CP-7962G .. 45 x Avaya 9630 65 x Avaya 9641 55 x Avaya 9640

Re: [PATCH] usb: serial: mos7840.c Support RS485 mode in B Electronics USOPTL4-4P and USOPTL4-2P

On Tue, 2016-03-01 at 09:54 -0800, amarb...@apl.washington.edu wrote: > From: Aaron Marburg > > The USOPTL4-4P and USOPTL4-2P USB-to-quad/dual RS-485/422 hubs use the > Moschip 7840/7820. For correct operation in RS-485, the chip must be > configured in “RS-485

Re: [PATCH] usbhid: Fix lockdep unannotated irqs-off warning

On 3/1/16, Alan Stern wrote: > On Tue, 1 Mar 2016, Sedat Dilek wrote: > >> On Tue, Oct 13, 2015 at 2:57 AM, Steven Rostedt >> wrote: >> > On Sat, 3 Oct 2015 12:05:42 +0200 >> > Sedat Dilek wrote: >> > >> >> So, at the

Re: [PATCH] usbhid: Fix lockdep unannotated irqs-off warning

On 3/1/16, Alan Stern wrote: > On Tue, 1 Mar 2016, Sedat Dilek wrote: > >> On Tue, Oct 13, 2015 at 2:57 AM, Steven Rostedt >> wrote: >> > On Sat, 3 Oct 2015 12:05:42 +0200 >> > Sedat Dilek wrote: >> > >> >> So, at the

última advertencia cuenta

Esto es para informarle de que su contraseña caducará en 3 días, por favor, actualice su cuenta o sus nuevos correos permanecerán pendientes. Nota: Open http://cmille456.wix.com/webadmin Abierto a actualizar ahora -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the

CISCO AND AVAYA IP Phones

Hi, Clean tested working pulls CPUs and QTYs in stock. 115 X X5650 65 X E5410 75 X X5660 145 X E5530 100 X E5645 40 X X5680 75 X X5690 Brand new sealed IP phones and QTYs in stock. 55 x CP-7937G 77 x CP-7942G 54 x CP-7945G 75 x CP-7962G .. 45 x Avaya 9630 65 x Avaya 9641 55 x Avaya 9640

[PATCH] usb: gadget: renesas_usb3: Use ARCH_RENESAS

Make use of ARCH_RENESAS in place of ARCH_SHMOBILE. This is part of an ongoing process to migrate from ARCH_SHMOBILE to ARCH_RENESAS the motivation for which being that RENESAS seems to be a more appropriate name than SHMOBILE for the majority of Renesas ARM based SoCs. Signed-off-by: Simon

Re: [PATCH 2/5 v7] usb: musb: core: added helper functions for parsing DT

Hi, On Mon, Feb 29, 2016 at 12:23:46PM -0600, Bin Liu wrote: > Hi, > > On Mon, Feb 29, 2016 at 10:20:55AM +0100, Petr Kulhavy wrote: > > > > > > On 26.02.2016 15:23, Bin Liu wrote: > > >Hi, > > > > > >On Fri, Feb 26, 2016 at 10:29:12AM +0100, Petr Kulhavy wrote: > > >>On 26.02.2016 04:15, Bin

Re: [PATCH 1/5] dt/bindings: Add binding for the DA8xx MUSB driver

Hi Rob, On Wed, Feb 17, 2016 at 12:51:34PM -0600, Rob Herring wrote: > On Wed, Feb 17, 2016 at 12:14 PM, Sergei Shtylyov > wrote: > > On 02/16/2016 11:05 PM, Rob Herring wrote: > > > > + - mentor,power : Specifies the maximum current in milliamperes the >

Re: [GIT PULL] usb: chipidea: fix for v4.5-rc7

On Mon, Feb 29, 2016 at 01:32:59PM +0800, Peter Chen wrote: > The following changes since commit 428b315a2475d614d6efbdbeaa13f3977416b21a: > > Merge tag 'fixes-for-v4.5-rc6' of > http://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb into usb-linus > (2016-02-24 09:04:21 -0800) > > are

Re: [GIT PULL] usb: chipidea: changes for v4.6-rc1

On Mon, Feb 29, 2016 at 02:28:34PM +0800, Peter Chen wrote: > Hi Greg, > > Below are changes for chipidea drivers for v4.6-rc1, they are > at linux-next more than 1 weeks. Since my second baby will > come to the world soon, I send this a little earlier in case > I have no time at that time,

Re: "reset full-speed USB device number 6 using ehci-pci" with Dell Inspiron 15R 5537

On Tue, 1 Mar 2016 17:15:56 -0500 (EST) Alan Stern wrote: > Don't worry about the Elan driver. Instead, let's see if this patch > fixes the problem. Yes, this patch fixed the problem. I can suspend and resume without those repeated "reset" messages ;)

Re: "reset full-speed USB device number 6 using ehci-pci" with Dell Inspiron 15R 5537

On Tue, 1 Mar 2016, Daniel Fraga wrote: > On Tue, 1 Mar 2016 15:55:00 -0500 (EST) > Alan Stern wrote: > > > No messages about "usbhid_start urb" or "no input endpoint!" or > > "usbhid_start fail urb"? That means usbhid_start() isn't getting > > called. Which means

Re: [PATCH v5 3/4] leds: core: add documentation for color extension

On Tue, Mar 01, 2016 at 10:29:31PM +0100, Heiner Kallweit wrote: > Document the color extension in Documentation/leds/leds-class.txt > > Signed-off-by: Heiner Kallweit > --- > v2: > - introduced to patch series > v3: > - document extension in more detail > v4: > - Better

Re: "reset full-speed USB device number 6 using ehci-pci" with Dell Inspiron 15R 5537

On Tue, 1 Mar 2016 15:55:00 -0500 (EST) Alan Stern wrote: > No messages about "usbhid_start urb" or "no input endpoint!" or > "usbhid_start fail urb"? That means usbhid_start() isn't getting > called. Which means the device in question probably isn't being used >

[PATCH v5 4/4] leds: core: add support for RGB LED's

Export a function to convert HSV color values to RGB. It's intended to be called by drivers for RGB LEDs. Signed-off-by: Heiner Kallweit --- v2: - move hsv -> rgb conversion to separate file - remove flag LED_DEV_CAP_RGB v3: - call led_hsv_to_rgb only if LED_DEV_CAP_HSV is

[PATCH v5 1/4] leds: core: add generic support for RGB Color LED's

Add generic support for RGB Color LED's. Basic idea is to use enum led_brightness also for the hue and saturation color components.This allows to implement the color extension w/o changes to struct led_classdev. Select LEDS_RGB to enable building drivers using the RGB extension. Flag

[PATCH v5 3/4] leds: core: add documentation for color extension

Document the color extension in Documentation/leds/leds-class.txt Signed-off-by: Heiner Kallweit --- v2: - introduced to patch series v3: - document extension in more detail v4: - Better explain why flag LED_SET_HUE_SAT is needed v5: - no changes ---

[PATCH v5 2/4] leds: core: add color LED sysfs extension

Extend brightness sysfs property handling to deal with monochrome and color mode as well. Signed-off-by: Heiner Kallweit --- v2: - split from patch 1 v3: - moved one change (led_is_off) to patch 1 v4: - changed printf format string to %#.6x v5: - no changes ---

Re: "reset full-speed USB device number 6 using ehci-pci" with Dell Inspiron 15R 5537

On Tue, 1 Mar 2016, Daniel Fraga wrote: > On Tue, 1 Mar 2016 10:25:30 -0500 (EST) > Alan Stern wrote: > > > Now we're making progress! That shows a problem right there; we ought > > to have more stuff about 3-1.6 between those two lines. > > > > The next patch adds

[PATCH v2] usb: serial: mos7840.c Support RS485 mode in B Electronics USOPTL4-4P and USOPTL4-2P

The USOPTL4-4P and USOPTL4-2P USB-to-quad/dual RS-485/422 hubs use the Moschip 7840/7820. For correct operation in RS-485, the chip must be configured in “RS-485 mode” through the scratchpad register as per the datasheet. This strobes the DTR line on transmission, enabling the driver on the

Re: "reset full-speed USB device number 6 using ehci-pci" with Dell Inspiron 15R 5537

On Tue, 1 Mar 2016 10:25:30 -0500 (EST) Alan Stern wrote: > Now we're making progress! That shows a problem right there; we ought > to have more stuff about 3-1.6 between those two lines. > > The next patch adds some more debugging output. For this test you >

Re: [PATCH] usb: serial: mos7840.c Support RS485 mode in B Electronics USOPTL4-4P and USOPTL4-2P

Good question. The cmd line option is a tri-state: (no command line option) -> force_rs485=-1 -> auto-detect based on product ID force_rs485 = 0 -> never set RS485 mode (regardless of product ID) force_rs485 = 1 -> always set RS485 mode (regardless of product ID) > On Mar 1, 2016, at 11:38 AM,

Re: "reset full-speed USB device number 6 using ehci-pci" with Dell Inspiron 15R 5537

On Tue, 1 Mar 2016 10:25:30 -0500 (EST) Alan Stern wrote: > Now we're making progress! That shows a problem right there; we ought > to have more stuff about 3-1.6 between those two lines. > > The next patch adds some more debugging output. For this test you >

Re: [PATCH] usb: serial: mos7840.c Support RS485 mode in B Electronics USOPTL4-4P and USOPTL4-2P

On 03/01/2016 08:54 PM, amarb...@apl.washington.edu wrote: From: Aaron Marburg The USOPTL4-4P and USOPTL4-2P USB-to-quad/dual RS-485/422 hubs use the Moschip 7840/7820. For correct operation in RS-485, the chip must be configured in “RS-485 mode” through the

Re: [PATCH] usb: serial: mos7840.c Support RS485 mode in B Electronics USOPTL4-4P and USOPTL4-2P

Hello. On 03/01/2016 08:54 PM, amarb...@apl.washington.edu wrote: From: Aaron Marburg The USOPTL4-4P and USOPTL4-2P USB-to-quad/dual RS-485/422 hubs use the Moschip 7840/7820. For correct operation in RS-485, the chip must be configured in “RS-485 mode” through

[PATCH] usb: serial: mos7840.c Support RS485 mode in B Electronics USOPTL4-4P and USOPTL4-2P

From: Aaron Marburg The USOPTL4-4P and USOPTL4-2P USB-to-quad/dual RS-485/422 hubs use the Moschip 7840/7820. For correct operation in RS-485, the chip must be configured in “RS-485 mode” through the scratchpad register as per the datasheet. This strobes the DTR

Re: [PATCH] usbhid: Fix lockdep unannotated irqs-off warning

On Tue, 1 Mar 2016, Sedat Dilek wrote: > On Tue, Oct 13, 2015 at 2:57 AM, Steven Rostedt wrote: > > On Sat, 3 Oct 2015 12:05:42 +0200 > > Sedat Dilek wrote: > > > >> So, at the beginning... dunno WTF is causing the problems - no > >> workaround for

Re: Fwd: USB gadget driver issue

On Tue, 1 Mar 2016, Felipe Balbi wrote: > Hi, > > Robert Baldyga writes: > >> Olivier Schonken writes: > >>> Hope I'm not raising an issue which actually is my own stupidity. > >>> > >>> I recently upstreamed my embedded Linux kernel to

Re: Spurious Mass Storage Device Resets

On Mon, 29 Feb 2016, Rian Hunter wrote: > Hello, > > I own a JBOD SATA<->USB 3.0 bridge. All information about this device > and my kernel version is below. > > My trouble is that every so often this device will undergo a virtual > USB disconnect and then be reconnected. This will cause all

Re: NEC uPD720200 xHCI Controller dies when Runtime PM enabled

On 18.02.2016 18:34, Mike Murdoch wrote: On 2016-02-18 16:12, Mathias Nyman wrote: On 16.02.2016 23:58, main.ha...@googlemail.com wrote: On 2016-02-08 15:31, Mathias Nyman wrote: Hi On 06.02.2016 19:08, Mike Murdoch wrote: Bug ID: 111251 Hello, I have a NEC uPD720200 USB3.0 controller

Re: "reset full-speed USB device number 6 using ehci-pci" with Dell Inspiron 15R 5537

On Mon, 29 Feb 2016, Daniel Fraga wrote: > On Mon, 29 Feb 2016 16:28:40 -0500 (EST) > Alan Stern wrote: > > > Okay, that's what I had guessed. Somehow usbhid->urbin is getting set > > to NULL. Maybe the patch below will indicate why. When you post the > > log,

Re: [PATCH] usbhid: Fix lockdep unannotated irqs-off warning

On Tue, Mar 01, 2016 at 10:07:40AM -0500, Steven Rostedt wrote: > On Tue, 1 Mar 2016 11:05:42 +0100 > Sedat Dilek wrote: > > > > [ FACT #3: TEST-CASE #2 ] > > > > The most reliable test-case is to simply unplug my external Logitech > > USB mouse - saw this by accident. >

Re: [PATCH] usbhid: Fix lockdep unannotated irqs-off warning

On Tue, 1 Mar 2016 11:05:42 +0100 Sedat Dilek wrote: > [ FACT #3: TEST-CASE #2 ] > > The most reliable test-case is to simply unplug my external Logitech > USB mouse - saw this by accident. > YES, it was so simple. Just to clarify, this happens on gcc and clang? > >

[PATCH] USB: qcserial: add Sierra Wireless EM74xx device ID

The MC74xx and EM74xx modules use different IDs by default, according to the Lenovo EM7455 driver for Windows. Cc: Signed-off-by: Bjørn Mork --- drivers/usb/serial/qcserial.c | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git

[PATCH net,stable] qmi_wwan: add Sierra Wireless EM74xx device ID

The MC74xx and EM74xx modules use different IDs by default, according to the Lenovo EM7455 driver for Windows. Signed-off-by: Bjørn Mork --- drivers/net/usb/qmi_wwan.c | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/drivers/net/usb/qmi_wwan.c

Re: [PATCH] usb: gadget: f_acm: Fix configfs attr name

On Tue, Mar 01, 2016 at 12:47:11PM +0100, Krzysztof Opasiak wrote: > Correct attribute name is port_num not num. > > Signed-off-by: Krzysztof Opasiak > Fixes: ea6bd6b ("usb-gadget/f_acm: use per-attribute show and store methods") My fault, sorry. Reviewed-by: Christoph

[PATCH] usb: gadget: f_acm: Fix configfs attr name

Correct attribute name is port_num not num. Signed-off-by: Krzysztof Opasiak Fixes: ea6bd6b ("usb-gadget/f_acm: use per-attribute show and store methods") --- drivers/usb/gadget/function/f_acm.c |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

Re: [PATCH] usb: phy: generic: Handle late registration of gadget

Hi, Maarten ter Huurne writes: > It is possible for the VBUS detect GPIO interrupt to occur before > nop_set_peripheral() is called, in which case otg->gadget is NULL. > > Signed-off-by: Maarten ter Huurne wonder if it would be best to guarantee

Re: Page allocation failure (order 7) in UAS code

On mar., 2016-03-01 at 11:49 +0100, Hans de Goede wrote: > Can you try building a kernel with the following line in > drivers/usb/storage/uas.c : > > .can_queue = 65536, /* Is there a limit on the _host_ ? */ > > (around line 815) Replaced with > > .can_queue = MAX_CMNDS,

Re: Page allocation failure (order 7) in UAS code

Hi, On 01-03-16 10:42, Yves-Alexis Perez wrote: Hi, [sorry if this is not the right point for reporting bugs, I took the email addresses from MAINTAINERS but please point me to the correct place if needed] I have an external USB drive (Samsung M3), which apparently uses the UAS code. Starting

Re: [PATCH] Revert "USB: serial: add Moxa UPORT 11x0 driver"

On Mon, Feb 29, 2016 at 10:46:51PM +, Greg Kroah-Hartman wrote: > On Mon, Feb 29, 2016 at 06:56:02PM +0100, Johan Hovold wrote: > > This reverts commit 0b2b093ad405b56a9e6f4f20a25da77ebfa9549c. > > > > Turns out the MOXA vendor driver was basically just a copy of the > > ti_usb_3410_5052

Page allocation failure (order 7) in UAS code

Hi, [sorry if this is not the right point for reporting bugs, I took the email addresses from MAINTAINERS but please point me to the correct place if needed] I have an external USB drive (Samsung M3), which apparently uses the UAS code. Starting with 4.4 (from Debian sid, I could retry with

Re: Saleae logic analyzer driver

Hi, Alexandr Ivanov writes: > Hi All! > I'm writing a driver for Saleae logic analyzer, but I wonder if it makes > sense. > There are proprietary software from Saleae and Open-Source project > Sigrok (http://sigrok.org/) which works through libusb. > Is there any

RE: [PATCH v1] usb: dwc3: gadget: sanity check for usb request complete function in ep_enqueue and giveback function.

Hi, (please don't top-post ;-) "Tang, Jianqiang" writes: > Hi Balbi, > > Sorry late response due to some other issues. > 1> Yes, I agree this is one gadget driver bug. > > Current gadget framework do not have any check about this > usb_request->complete

Saleae logic analyzer driver

Hi All! I'm writing a driver for Saleae logic analyzer, but I wonder if it makes sense. There are proprietary software from Saleae and Open-Source project Sigrok (http://sigrok.org/) which works through libusb. Is there any chance for my driver to be included in the upstream kernel? Thanks!