Re: [PATCH 2/3] usb: phy: Add USB charger support

Hi, On 28 June 2017 at 10:44, kbuild test robot <l...@intel.com> wrote: > Hi Baolin, > > [auto build test ERROR on balbi-usb/next] > [also build test ERROR on next-20170627] > [cannot apply to v4.12-rc7] > [if your patch is applied to the wrong git tree, please drop us a

Re: usb-related linux-next boot failures

On Tue, Jun 27, 2017 at 02:28:56PM -0400, Carlos Hernandez wrote: > Still seeing AM57xx/DRA72/DRA7x usb-related boot failures on linux-next... Is this a regression? If so, any specific commit that caused it? thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe

[PATCH v5] usb: host: ohci-pxa27x: Handle return value of clk_prepare_enable

clk_prepare_enable() can fail here and we must check its return value. Signed-off-by: Arvind Yadav --- Changes in v4: Change log was missing. Changes in v3: Change log correction. Added change log below '---'. Changes in v2:

Re: [PATCH 2/3] usb: phy: Add USB charger support

Hi Baolin, [auto build test ERROR on balbi-usb/next] [also build test ERROR on next-20170627] [cannot apply to v4.12-rc7] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Baolin-Wang/include-uapi

RE: [GIT PULL] usb: chipidea changes for v4.13-rc1

>> >> Linux 4.12-rc1 (2017-05-13 13:19:49 -0700) >> >> are available in the git repository at: >> >> git://git.kernel.org/pub/scm/linux/kernel/git/peter.chen/usb.git/ >> tags/usb-ci-v4.13-rc1 >> >> for you to fetch changes up to c4a0bbbdb7f6e3c37fa6deb3ef28c5ed99da6175: >> >> usb:

Re: [PATCH] usb: gadget: udc-xilinx: remove useless variable assignment in xudc_read_fifo()

On Tue, 2017-06-27 at 16:30:30 -0500, Gustavo A. R. Silva wrote: > Value assigned to variable bufferspace at line 637 is overwritten > at line 613, before it can be used. This makes such variable > assignment useless. > > Addresses-Coverity-ID: 1397677 > Signed-off-by: Gustavo A. R. Silva

Re: Moxa UPort 1150 and RS-422/485… what's the "proper" way to switch modes

On 27/06/17 22:08, Oliver Neukum wrote: > Am Dienstag, den 27.06.2017, 19:43 +1000 schrieb Stuart Longland: >> Maybe a good start would be a "standard" option (referring to the >> physical signalling standard, TTL/RS-232/RS-422/RS-485), that lists the >> available standards when read and shows the

[PATCH] usb: gadget: udc-xilinx: remove useless variable assignment in xudc_read_fifo()

Value assigned to variable bufferspace at line 637 is overwritten at line 613, before it can be used. This makes such variable assignment useless. Addresses-Coverity-ID: 1397677 Signed-off-by: Gustavo A. R. Silva --- drivers/usb/gadget/udc/udc-xilinx.c | 1 - 1 file

The #1 in weight-loss solution products introduces a brand-new game-changing formula

The all-natural, 100% trusted diet supplement that includes bioactive ingredients that play a key role in fat burning and energy metabolism. They're vital to the weight loss process, they are vital for the body's natural weight loss system. Overall, the aforementioned APIs play a lot of vital

usb:gadget:hid: [PATCH] Remote Wakeup Support

Currently linux HID gadgets do not support remote wakeup (the ability to wake up a host from suspend). This is an important feature for gadgets that want to properly emulate the normal operation of a mouse and keyboard. This feature has to be enabled/supported by the underlying UDC driver to

Re: [PATCH] net: usb: asix88179_178a: Add support for the Belkin B2B128

From: "Andrew F. Davis" Date: Mon, 26 Jun 2017 12:41:20 -0500 > The Belkin B2B128 is a USB 3.0 Hub + Gigabit Ethernet Adapter, the > Ethernet adapter uses the ASIX AX88179 USB 3.0 to Gigabit Ethernet > chip supported by this driver, add the USB ID for the same. > > This patch is

usb-related linux-next boot failures

Still seeing AM57xx/DRA72/DRA7x usb-related boot failures on linux-next... Complete boot log including sysrq traces at https://pastebin.ubuntu.com/24964903/ Starting kernel ... [0.00] Booting Linux on physical CPU 0x0 [0.00] Linux version 4.12.0-rc6-next-20170626

[PATCH 0/8] Bugs fixes and improvements to Broadcom BDC driver

Bug fixes and improvements to the USB Broadcom Device Controller (BDC) driver. Al Cooper (7): usb: gadget: bdc: Fix misleading register names usb: bdc: Add Device Tree binding document for Broadcom BDC driver usb: bdc: Add clock enable for new chips with a separate BDC clock usb: bdc:

[PATCH 2/8] usb: bdc: Add Device Tree binding document for Broadcom BDC driver

Add Device Tree binding document for Broadcom USB Device Controller (BDC). Signed-off-by: Al Cooper --- .../devicetree/bindings/usb/brcm,bdc-udc.txt | 28 ++ 1 file changed, 28 insertions(+) create mode 100644

[PATCH 1/8] usb: gadget: bdc: Fix misleading register names

The BDC endpoint status registers 0-7 were originally each going to be an array of regsiters. This was later changed to being a single register. The register definitions are being changed from: "#define BDC_EPSTS0(n) (0x60 + (n * 0x10))" to "#define BDC_EPSTS0 0x60" to reflect this change and

[PATCH 5/8] usb: gadget: bdc: hook a quick Device Tree compatible string

From: Florian Fainelli Allows Device Tree probing Signed-off-by: Florian Fainelli Signed-off-by: Al Cooper --- drivers/usb/gadget/udc/bdc/bdc_core.c | 8 1 file changed, 8 insertions(+) diff --git

[PATCH 6/8] usb: bdc: Add support for suspend/resume

Based on a previous commit by Danesh Petigara that added resume to solve the following problem: "The BDC driver will fail after resuming from S3 suspend and this will cause any upper layer gadget driver to fail." This commit also adds support for suspend and manages the

[PATCH 7/8] usb: bdc: fix "xsf for ep not enabled" errror

This patch essentially clears the port status change bits at the correct times. It is necessary because the driver was not handling the change bits correctly for events during device connection/disconnection and bus enumeration. So, one of them (PCC) was left stuck sometimes causing the "xsf for

[PATCH 8/8] usb: bdc: Enable in Kconfig for ARCH_BRCMSTB systems

Many ARM based Broadcom STB SoC's have a USB BDC controller so enable this driver for these systems. Signed-off-by: Al Cooper --- drivers/usb/gadget/udc/bdc/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/usb/gadget/udc/bdc/Kconfig

[PATCH 4/8] usb: bdc: Small code cleanup

Signed-off-by: Al Cooper --- drivers/usb/gadget/udc/bdc/bdc_core.c | 15 --- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/drivers/usb/gadget/udc/bdc/bdc_core.c b/drivers/usb/gadget/udc/bdc/bdc_core.c index 3bd82d2..621328f 100644 ---

[PATCH 3/8] usb: bdc: Add clock enable for new chips with a separate BDC clock

Newer SoC's have added a BDC clock to the Device Tree, so get and enable it. Signed-off-by: Al Cooper Signed-off-by: Florian Fainelli --- drivers/usb/gadget/udc/bdc/bdc_core.c | 15 +++ 1 file changed, 15 insertions(+) diff --git

[PATCH] Add USB quirk for HVR-950q to avoid intermittent device resets

The USB core and sysfs will attempt to enumerate certain parameters which are unsupported by the au0828 - causing inconsistent behavior and sometimes causing the chip to reset. Avoid making these calls. This problem manifested as intermittent cases where the au8522 would be reset on analog video

potentially missing USB patches from my queue

Hi all, I think I've now caught up with all pending USB patches sent to me. But given that I somehow just messed up my internal USB patch queue mbox, and hopefully restored it all properly (I blame the jet-lag), I might have missed some patches. So if I haven't applied any USB patches that

Re: [PATCH v4] usb: host: ohci-pxa27x: Handle return value of clk_prepare_enable

On Tue, Jun 27, 2017 at 10:47:28AM +0530, Arvind Yadav wrote: > clk_prepare_enable() can fail here and we must check its return value. > > Signed-off-by: Arvind Yadav > --- > drivers/usb/host/ohci-pxa27x.c | 10 +++--- > 1 file changed, 7 insertions(+), 3

Re: [PATCH] usbip: Fix uninitialized variable bug in vhci

On 06/27/2017 02:58 AM, Yuyang Du wrote: > The patch 03cd00d538a6: "usbip: vhci-hcd: Set the vhci structure up > to work" introduced a bug which uses a vairable without initialization > in error handling code. Fix it. > > Reported-by: Dan Carpenter > Signed-off-by:

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

On Wed, Jun 21, 2017 at 10:47:53AM +0800, Peter Chen wrote: > The following changes since commit 2ea659a9ef488125eb46da6eb571de5eae5c43f6: > > Linux 4.12-rc1 (2017-05-13 13:19:49 -0700) > > are available in the git repository at: > >

usb:gadget:hid: [PATCH] {SET,GET} protocol support

The current HID function driver doesn't support GET_PROCOTOL and SET_PROCOTOL commands, which are required to operate the HID gadget in BOOT mode. This change implements this feature for devices that have the same implementation for REPORT and BOOT mode Signed-off-by: Abdulhadi Mohamed

Re: Moxa UPort 1150 and RS-422/485… what's the "proper" way to switch modes

Am Dienstag, den 27.06.2017, 19:43 +1000 schrieb Stuart Longland: > Maybe a good start would be a "standard" option (referring to the > physical signalling standard, TTL/RS-232/RS-422/RS-485), that lists the > available standards when read and shows the "selected" standard in > brackets (like the

Re: Moxa UPort 1150 and RS-422/485… what's the "proper" way to switch modes

On 27/06/17 19:04, Johan Hovold wrote: >> What's the "proper" way to configure such ports for RS-422 and/or 4-wire >> RS-485? Is there an example driver in the tree that I can use as a >> guide to porting Moxa's mode-switch code over to the ti_usb_3410_5052 >> driver? > > I'm afraid not. We have

RE: [PATCH] net: usb: asix88179_178a: Add support for the Belkin B2B128

From: Andrew F. Davis > Sent: 26 June 2017 18:41 > The Belkin B2B128 is a USB 3.0 Hub + Gigabit Ethernet Adapter, the > Ethernet adapter uses the ASIX AX88179 USB 3.0 to Gigabit Ethernet > chip supported by this driver, add the USB ID for the same. ... I've just had a look at the current version

Re: Moxa UPort 1150 and RS-422/485… what's the "proper" way to switch modes

[ +CC: Alan and linux-usb ] On Fri, Jun 23, 2017 at 09:44:31AM +1000, Stuart Longland wrote: > Hi all, > > A silly question: I have a Moxa UPort 1150 USB serial interface that I > am trying to coax into either RS-422 or 4-wire RS-485 mode. Internally, > this is a TI USB 3410 device, and works

[PATCH] usbip: Fix uninitialized variable bug in vhci

The patch 03cd00d538a6: "usbip: vhci-hcd: Set the vhci structure up to work" introduced a bug which uses a vairable without initialization in error handling code. Fix it. Reported-by: Dan Carpenter Signed-off-by: Yuyang Du ---

Re: Linux USB-Serial and DSR flow control

On Tue, Jun 27, 2017 at 03:49:00AM +0200, Zaerc wrote: > Thanks Johan! > > TL;DR: I'm delighted to report that it *does* work with 4.12.0-rc7 I'm glad to hear that. > Below I've tried to answer your questions best as I could, probably moot > now but it's the least I can do for wasting your

[PATCH 3/3] power: wm831x_power: Support USB charger current limit management

Integrate with the newly added USB charger interface to limit the current we draw from the USB input based on the input device configuration identified by the USB stack, allowing us to charge more quickly from high current inputs without drawing more current than specified from others.

[PATCH 2/3] usb: phy: Add USB charger support

This patch introduces the usb charger support based on usb phy that makes an enhancement to a power driver. The basic conception of the usb charger is that, when one usb charger is added or removed by reporting from the extcon device state change, the usb charger will report to power user to set

[PATCH 1/3] include: uapi: usb: Introduce USB charger type and state definition

Introducing USB charger type and state definition can help to support USB charging which will be added in USB phy core. Signed-off-by: Baolin Wang --- include/uapi/linux/usb/charger.h | 31 +++ 1 file changed, 31 insertions(+) create mode

Re: [PATCH V5 2/2] usb: core: read USB ports from DT in the usbport LED trigger driver

On 8 June 2017 at 18:08, Rafał Miłecki wrote: > From: Rafał Miłecki > > This uses DT info to read relation description of LEDs and USB ports. If > DT has properly described LEDs, trigger will know when to turn them on. > > Signed-off-by: Rafał Miłecki