Re: bug : Specific USB activity causes crash

On Wed, Aug 17, 2016 at 09:56:02PM +0200, Filip Ayazi wrote: > Forwarding bug report from bugzilla #153211 as requested: > > System crashes completely during or immediately after installing APK to > android > phone over usb using android studio. I was unable to reproduce this bug any > other

Re: [PATCH v9 4/4] arm64: dts: rockchip: configure usb2-phy support for rk3399-evb

On 2016/8/17 18:02, Heiko Stübner wrote: Am Freitag, 22. Juli 2016, 15:00:46 schrieb Frank Wang: Add vcc5v0_host regulator for usb2-phy and enable host-port support. Signed-off-by: Frank Wang applied to ny dts64 branch [0] with some changes: - the pin is named

Fast Loans

Apply for a loan at 2% reply to this Email for more Info -- 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-info.html

Re: [PATCH v5 2/2] usb: typec: add driver for Intel Whiskey Cove PMIC USB Type-C PHY

On Wed, Aug 17, 2016 at 03:53:24PM +0300, Felipe Balbi wrote: > > Hi, > > Heikki Krogerus writes: > > [...] > > > +static struct platform_driver wcove_typec_driver = { > > + .driver = { > > + .name = "bxt_wcove_usbc", > > + }, > > +

Re: [PATCH V2 RFC 6/6] ARM: dts: bcm2835: Add Raspberry Pi Zero

Hi John, > John Youn hat am 17. August 2016 um 23:21 > geschrieben: > > > ... > Ok, yeah, that seems better. > > Can you check if applying just patch 2 and 3 solves the issue? If so I > think we can send those upstream. unfortunately not: [2.280719]

[RFC PATCH v2 3/4] usb: typec: USB Type-C Port Manager (tcpm)

This driver implements the USB Type-C Power Delivery state machine for both source and sink ports. Alternate mode support is not fully implemented. The driver attaches to the USB Type-C class code implemented in the following patches. usb: typec: add driver for Intel Whiskey Cove PMIC

[RFC PATCH v2 4/4] usb: typec: Type-C Port Controller Interface driver (tcpci)

The port controller interface driver interconnects the Type-C Port Manager with a Type-C Port Controller Interface (TCPCI) compliant port controller. Signed-off-by: Guenter Roeck --- v2: - Adjust to modified callbacks into tcpm code drivers/usb/typec/Kconfig | 9 +

[RFC PATCH v2 2/4] usb: typec: Do not update modes in class driver

Mode updates need to be triggered and reported by underlying drivers. Also add missing "if (ret)". Signed-off-by: Guenter Roeck --- v2: Added fixup patch drivers/usb/typec/typec.c | 11 +-- 1 file changed, 1 insertion(+), 10 deletions(-) diff --git

[RFC PATCH v2 1/4] usb: typec: Do not check if connected when setting roles

The connection status can change after the connection status was checked. Leave it up to the driver to perform the necessary checks. Signed-off-by: Guenter Roeck --- v2: Rebased to v5 of Type-C class code drivers/usb/typec/typec.c | 6 -- 1 file changed, 6 deletions(-)

[RFC PATCH v2 0/4] Type-C Port Manager

The following series of patches implements a USB Type-C Port Manager using the pending USB Type-C class code as basis. The code is still WIP, but I think it is important to get feedback from the community at this point. There are four patches in the series. The first two patches make necessary

Re: [PATCH V2 RFC 6/6] ARM: dts: bcm2835: Add Raspberry Pi Zero

On 8/17/2016 12:11 PM, Stefan Wahren wrote: > Hi, > >> John Youn hat am 17. August 2016 um 00:07 >> geschrieben: >> >> >> On 8/16/2016 12:58 PM, Stefan Wahren wrote: >>> Hi John, >>> ... >>> >>> like in host mode i took the default values in otg mode for the last two >>>

[PATCH v3 0/3] USB Audio Gadget refactoring

I came to this patch series when wanted to do two things: - use UAC1 as virtual ALSA sound card on gadget side, just like UAC2 is used so it's possible to do rate resampling - have both playback/capture support in UAC1 Since I wanted to have same behavior for both UAC1/UAC2, obviously

[PATCH v3 1/3] usb: gadget: f_uac2: remove platform driver/device creation

Simplify f_uac2 by removing platform driver/device creation; use composite's usb_gadget device as parent for sound card and for debug prints. This removes extra layer of code without any functional change. Signed-off-by: Ruslan Bilovol ---

[PATCH v3 3/3] usb: gadget: add f_uac1 variant based on new u_audio api

This patch adds new function f_uac1_newapi that uses recently created u_audio api. This makes f_uac1_newapi implementation much simpler by reusing existing u_audio core utilities. This also drops previous f_uac1 approach (write audio samples directly to existing ALSA sound card) and moves to more

[PATCH v3 2/3] usb: gadget: f_uac2: split out audio core

Abstract the peripheral side ALSA sound card code from the f_uac2 function into a component that can be called by various functions, so the various flavors can be split apart and selectively reused. Visible changes: - add uac_params structure to pass audio paramteres for g_audio_setup - make

bug : Specific USB activity causes crash

Forwarding bug report from bugzilla #153211 as requested: System crashes completely during or immediately after installing APK to android phone over usb using android studio. I was unable to reproduce this bug any other way. The only way to recover after the crash is a hard restart, netconsole

Re: [PATCH V2 RFC 6/6] ARM: dts: bcm2835: Add Raspberry Pi Zero

Hi, > John Youn hat am 17. August 2016 um 00:07 > geschrieben: > > > On 8/16/2016 12:58 PM, Stefan Wahren wrote: > > Hi John, > > ... > > > > like in host mode i took the default values in otg mode for the last two > > here > > (please refer to the logs). The BCM2835

Re: [PATCH v5 1/2] usb: USB Type-C connector class

On Wed, Aug 17, 2016 at 01:34:40PM +0300, Heikki Krogerus wrote: > The purpose of USB Type-C connector class is to provide > unified interface for the user space to get the status and > basic information about USB Type-C connectors on a system, > control over data role swapping, and when the port

Re: [PATCH v5 1/2] usb: USB Type-C connector class

On Wed, Aug 17, 2016 at 01:34:40PM +0300, Heikki Krogerus wrote: > The purpose of USB Type-C connector class is to provide > unified interface for the user space to get the status and > basic information about USB Type-C connectors on a system, > control over data role swapping, and when the port

Re: [Umap2][4/11][0557:2002] NULL pointer dereference

On 2016-08-17 21:07, Binyamin Sharet wrote: The issue was found on raspbian with kernel 4.4.6, and was not found on ubuntu 16.04 with mainline kernel 4.8-rc2, I don't have much experience with compiling kernels, so it will take me some time to build mainline kernel for the raspberry pi.

Re: [Umap2][5/11][22b8:2d93] NULL pointer dereference

On 08/17/2016 04:26 PM, Oliver Neukum wrote: > On Tue, 2016-08-16 at 16:46 +0300, Binyamin Sharet wrote: >> Kernel version: raspberrypi 4.4.6-v7+ #871 >> Driver source file: drivers/usb/class/cdc-acm.c >> Umap2 command line: umap2vsscan -P -s 22b8:2d93 > Hi, > > could you retest this kernel with

Re: [Umap2][4/11][0557:2002] NULL pointer dereference

On 08/17/2016 05:19 PM, Oliver Neukum wrote: > On Wed, 2016-08-17 at 17:07 +0300, Binyamin Sharet wrote: >> The issue was found on raspbian with kernel 4.4.6, and was not found >> on >> ubuntu 16.04 with mainline kernel 4.8-rc2, I don't have much >> experience >> with compiling kernels, so it will

Re: [Umap2][4/11][0557:2002] NULL pointer dereference

On Wed, 2016-08-17 at 17:07 +0300, Binyamin Sharet wrote: > The issue was found on raspbian with kernel 4.4.6, and was not found > on > ubuntu 16.04 with mainline kernel 4.8-rc2, I don't have much > experience > with compiling kernels, so it will take me some time to build mainline > kernel for

Re: [Umap2][4/11][0557:2002] NULL pointer dereference

On 08/17/2016 04:18 PM, Oliver Neukum wrote: > On Wed, 2016-08-17 at 14:26 +0300, Binyamin Sharet wrote: >> On 08/16/2016 06:02 PM, Alan Stern wrote: >>> On Tue, 16 Aug 2016, Binyamin Sharet wrote: >>> Kernel version: raspberrypi 4.4.6-v7+ #871 Driver source file:

Re: [PATCH v5 1/2] usb: USB Type-C connector class

Hi, On Wed, Aug 17, 2016 at 03:14:03PM +0200, Frans Klaver wrote: > On Wed, Aug 17, 2016 at 12:34 PM, Heikki Krogerus > > +static const char * const typec_partner_types[] = { > > + [TYPEC_PARTNER_USB] = "USB", > > + [TYPEC_PARTNER_CHARGER] = "Charger", > > +

[PATCH v2 1/2] kaweth: fix firmware download

This fixes the oops discovered by the Umap2 project and Alan Stern. The intf member needs to be set before the firmware is downloaded. Signed-off-by: Oliver Neukum --- drivers/net/usb/kaweth.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git

[PATCH v2 0/2]fixes to kaweth in response to Umap2 testing

These patches fix an oops in firmware downloading and an oops due to a memory allocation failure -- 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-info.html

[PATCH v2 2/2] kaweth: fix oops upon failed memory allocation

Just return an error upon failure. Signed-off-by: Oliver Neukum --- drivers/net/usb/kaweth.c | 7 ++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/drivers/net/usb/kaweth.c b/drivers/net/usb/kaweth.c index 37bf715..528b9c9 100644 ---

Re: [PATCH v5 1/2] usb: USB Type-C connector class

On Wed, Aug 17, 2016 at 3:53 PM, Heikki Krogerus wrote: > Hi, > > On Wed, Aug 17, 2016 at 03:14:03PM +0200, Frans Klaver wrote: >> On Wed, Aug 17, 2016 at 12:34 PM, Heikki Krogerus >> > +static const char * const typec_partner_types[] = { >> > +

Re: [PATCH v5 1/2] usb: USB Type-C connector class

Hi, On Wed, Aug 17, 2016 at 06:30:35AM -0700, Guenter Roeck wrote: > On 08/17/2016 03:34 AM, Heikki Krogerus wrote: > > The purpose of USB Type-C connector class is to provide > > unified interface for the user space to get the status and > > basic information about USB Type-C connectors on a

Re: [PATCH 2/2] kaweth: fix oops upon failed memory allocation

On Wed, 2016-08-17 at 15:15 +0200, Bjørn Mork wrote: > Oliver Neukum writes: > Eh, that should be "goto err_free_netdev;", shouldn't it? Right, thanks. Fixed version coming up. Regards Oliver -- To unsubscribe from this list: send the line

Re: [PATCH v5 2/2] usb: typec: add driver for Intel Whiskey Cove PMIC USB Type-C PHY

On Wed, Aug 17, 2016 at 03:53:24PM +0300, Felipe Balbi wrote: > Heikki Krogerus writes: > > [...] > > > +static struct platform_driver wcove_typec_driver = { > > + .driver = { > > + .name = "bxt_wcove_usbc", > > + }, > > + .probe

Re: [PATCH v5 1/2] usb: USB Type-C connector class

On 08/17/2016 03:34 AM, Heikki Krogerus wrote: The purpose of USB Type-C connector class is to provide unified interface for the user space to get the status and basic information about USB Type-C connectors on a system, control over data role swapping, and when the port supports USB Power

Re: [Umap2][5/11][22b8:2d93] NULL pointer dereference

On Tue, 2016-08-16 at 16:46 +0300, Binyamin Sharet wrote: > Kernel version: raspberrypi 4.4.6-v7+ #871 > Driver source file: drivers/usb/class/cdc-acm.c > Umap2 command line: umap2vsscan -P -s 22b8:2d93 Hi, could you retest this kernel with the attached fix, so I know whether it can go into

Re: [PATCH 2/2] kaweth: fix oops upon failed memory allocation

Oliver Neukum writes: > Just return an error upon failure. > > Signed-off-by: Oliver Neukum > --- > drivers/net/usb/kaweth.c | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/drivers/net/usb/kaweth.c b/drivers/net/usb/kaweth.c > index

Re: [PATCH v5 1/2] usb: USB Type-C connector class

On Wed, Aug 17, 2016 at 12:34 PM, Heikki Krogerus wrote: > The purpose of USB Type-C connector class is to provide > unified interface for the user space to get the status and > basic information about USB Type-C connectors on a system, > control over data role

Re: [PATCH 2/2] usb: gadget: f_ncm: add support for scatter/gather SKB to enable GSO

Hello, 16.08.2016, 14:02, Felipe Balbi kirjoitti: > > Hi again, > > Felipe Balbi writes: > Enabling SG allows enabling GSO (generic segmentation offload) feature > of linux networking layer. This increases TCP throughput with NCM > on Cortex-A15+USB3380 based

Re: [PATCH v5 2/2] usb: typec: add driver for Intel Whiskey Cove PMIC USB Type-C PHY

Hi, Heikki Krogerus writes: [...] > +static struct platform_driver wcove_typec_driver = { > + .driver = { > + .name = "bxt_wcove_usbc", > + }, > + .probe = wcove_typec_probe, > + .remove =

[PATCH] usb: core: setup dma_pfn_offset for USB devices

If dma_pfn_offset is not inherited correctly from the host controller, it might result in sub-optimal configuration as bounce buffer limit might be set to less than optimal level. e.g. On Keystone 2 systems, dma_max_pfn() is 0x87 and dma_mask_pfn is 0xF. Consider a mass storage use case:

[PATCH 1/1] ARM: dma: fix dma_max_pfn()

Since commit 6ce0d2001692 ("ARM: dma: Use dma_pfn_offset for dma address translation"), dma_to_pfn() already returns the PFN with the physical memory start offset so we don't need to add it again. This fixes USB mass storage lock-up problem on systems that can't do DMA over the entire physical

[PATCH 0/1] ARM: Keystone: Fix USB Mass storage on K2E

Hi, USB mass storage devices lock up on K2E or any Keystone2 system with more than 2GB RAM. Test case: 1) Plug in USB pen drive 2) mount udisks --mount /dev/sda1 Mounted /org/freedesktop/UDisks/devices/sda at /media/PENDRIVE 3) write to medium cp blobs/1M.bin /media/PENDRIVE 4)

Re: [Umap2][11/11][9022:d483] kernel is unable to handle paging address

On 08/17/2016 02:39 PM, Binyamin Sharet wrote: > On 08/16/2016 04:52 PM, Binyamin Sharet wrote: >> Kernel version: raspberrypi 4.4.6-v7+ #871 >> Driver source file: drivers/media/usb/dvb-usb/dw2102.c >> Umap2 command line: umap2vsscan -P -s 9022:d483 >> >> After connecting such a device, kernel

Re: [Umap2][11/11][9022:d483] kernel is unable to handle paging address

On 08/16/2016 04:52 PM, Binyamin Sharet wrote: > Kernel version: raspberrypi 4.4.6-v7+ #871 > Driver source file: drivers/media/usb/dvb-usb/dw2102.c > Umap2 command line: umap2vsscan -P -s 9022:d483 > > After connecting such a device, kernel oops: kernel is unable to handle > paging address. > >

Re: [Umap2][9/11][05c5:0002] NULL pointer dereference

On 08/17/2016 09:45 AM, Johan Hovold wrote: > On Wed, Aug 17, 2016 at 09:37:02AM +0300, Binyamin Sharet wrote: >> Hi >> >> On 08/16/2016 06:04 PM, Johan Hovold wrote: >>> On Tue, Aug 16, 2016 at 10:47:44AM -0400, Alan Stern wrote: On Tue, 16 Aug 2016, Binyamin Sharet wrote: > Kernel

Re: [Umap2][8/11][076d:0006] NULL pointer dereference

On 08/16/2016 04:49 PM, Binyamin Sharet wrote: > Kernel version: raspberrypi 4.4.6-v7+ #871 > Driver source file: drivers/staging/vt6656/main_usb.c > Umap2 command line: umap2vsscan -P -s 076d:0006 > > After connecting such a device, NULL pointer dereference in the kernel. > > Binyamin Sharet >

Re: [Umap2][7/11][160a:3184] NULL pointer dereference

On 08/16/2016 04:48 PM, Binyamin Sharet wrote: > Kernel version: raspberrypi 4.4.6-v7+ #871 > Driver source file: drivers/staging/vt6656/main_usb.c > Related file: drivers/staging/comedi/drivers/usbduxsigma.c > Umap2 command line: umap2vsscan -P -s 160a:3184 > > After connecting such a device,

Re: [Umap2][6/11][3923:718a] NULL pointer dereference

On 08/16/2016 04:57 PM, Binyamin Sharet wrote: > Kernel version: 4.4.0-24-generic #43-Ubuntu SMP > Driver source file: drivers/staging/comedi/drivers/ni_usb6501.c > Umap2 command line: umap2vsscan -P -s 3923:718a > > After connecting such a device, there's a NULL pointer dereference in > the

Re: [Umap2][5/11][22b8:2d93] NULL pointer dereference

On 08/17/2016 01:18 PM, Binyamin Sharet wrote: > On 08/17/2016 01:06 PM, Oliver Neukum wrote: >> On Tue, 2016-08-16 at 16:46 +0300, Binyamin Sharet wrote: >>> Kernel version: raspberrypi 4.4.6-v7+ #871 >>> Driver source file: drivers/usb/class/cdc-acm.c >>> Umap2 command line: umap2vsscan -P -s

Re: [Umap2][3/11][0471:0602] NULL pointer dereference

On 08/17/2016 10:16 AM, Binyamin Sharet wrote: > Hi, > > On 08/17/2016 10:07 AM, Greg KH wrote: >> On Wed, Aug 17, 2016 at 09:05:34AM +0200, Greg KH wrote: >>> On Wed, Aug 17, 2016 at 09:26:18AM +0300, Binyamin Sharet wrote: Hi, On 08/16/2016 05:39 PM, Alan Stern wrote: > On

Re: [Umap2][4/11][0557:2002] NULL pointer dereference

On 08/16/2016 06:02 PM, Alan Stern wrote: > On Tue, 16 Aug 2016, Binyamin Sharet wrote: > >> Kernel version: raspberrypi 4.4.6-v7+ #871 >> Driver source file: drivers/net/usb/kaweth.c >> Umap2 command line: umap2vsscan -P -s 0557:2002 >> >> After connecting such a device, NULL pointer dereference

Re: [Umap2][2/11][10cf:5500] NULL pointer dereference

On 08/17/2016 09:32 AM, Binyamin Sharet wrote: > Hi > > On 08/16/2016 04:44 PM, Binyamin Sharet wrote: >> Kernel version: 4.4.0-24-generic #43-Ubuntu SMP >> Driver source file: drivers/staging/comedi/drivers/vmk80xx.c >> Umap2 command line: umap2vsscan -P -s 10cf:5500 >> >> After connecting such

Re: [Umap2][1/11][0aa8:8001] USB stack hang

On 08/17/2016 09:29 AM, Binyamin Sharet wrote: > Hi > > On 08/16/2016 06:15 PM, Binyamin Sharet wrote: >> On 08/16/2016 05:49 PM, Greg KH wrote: >>> On Tue, Aug 16, 2016 at 04:42:23PM +0300, Binyamin Sharet wrote: Kernel version: raspberrypi 4.4.6-v7+ #871 Kernel version:

Re: [PATCH v3 7/8] usb: ulpi: make ops struct constant

On Tue, Aug 16, 2016 at 07:04:52PM +0300, Tal Shorer wrote: > None of the core ulpi functions perform any changes to the operations > struct, and logically as a struct that contains function pointers > there's no reason it shouldn't be constant. > > Signed-off-by: Tal Shorer

Re: [PATCH v3 8/8] usb: dwc3: ulpi: make dwc3_ulpi_ops constant

On Tue, Aug 16, 2016 at 07:04:53PM +0300, Tal Shorer wrote: > ulpi_register_interface() accepts a const struct ulpi_ops and dwc3 > doesn't perform any changes to this struct at runtime, so there's no > reason it shouldn't be constant. > > Signed-off-by: Tal Shorer

Re: [PATCH v3 6/8] usb: ulpi: remove "dev" field from struct ulpi_ops

On Tue, Aug 16, 2016 at 07:04:51PM +0300, Tal Shorer wrote: > Operations now use ulpi->dev.parent directly instead of via the > ulpi_ops struct, making this field unused. Remove it. > > Signed-off-by: Tal Shorer Acked-by: Heikki Krogerus

Re: [PATCH v3 4/8] usb: ulpi: remove calls to old api callbacks

On Tue, Aug 16, 2016 at 07:04:49PM +0300, Tal Shorer wrote: > Now that all users use the new api callbacks, remove the old api > callbacks and force new interface drivers to use the new api. > > Signed-off-by: Tal Shorer Acked-by: Heikki Krogerus

Re: [PATCH v3 5/8] usb: ulpi: rename operations {read|write}_dev to simply {read|write}

On Tue, Aug 16, 2016 at 07:04:50PM +0300, Tal Shorer wrote: > With the removal of the old {read|write} operations, we can now safely > rename the new api operations {read|write}_dev to use the shorter and > clearer names {read|write}, respectively. > > Signed-off-by: Tal Shorer

Re: [PATCH v3 3/8] usb: dwc3: ulpi: use new api

On Tue, Aug 16, 2016 at 07:04:48PM +0300, Tal Shorer wrote: > The old read, write callbacks in struct ulpi_ops have been deprecated > in favor of new callbacks that pass the parent device directly. > Replace the used callbacks in dwc3's ulpi component with the new api. > > Signed-off-by: Tal

Re: [PATCH v3 1/8] usb: ulpi: move setting of ulpi->dev parent up in ulpi_register()

On Tue, Aug 16, 2016 at 07:04:46PM +0300, Tal Shorer wrote: > Once ulpi operations use the parent device directly, this will be > needed during the operations used in ulpi_register() itself, so set > the parent field before calling any ulpi operations. > > Signed-off-by: Tal Shorer

Re: [PATCH v3 2/8] usb: ulpi: add new api functions, {read|write}_dev()

On Tue, Aug 16, 2016 at 07:04:47PM +0300, Tal Shorer wrote: > Add these two new api callbacks to struct ulpi_ops. These are different > than read, write in that they pass the parent device directly instead > of via the ops argument. > They are intended to replace the old api functions. > > If the

[PATCH] USB: Gadget: UVC: Add missing call for additional setup data

Some UVC commands require additional data (non zero uvc->event_length). Add usb_ep_queue() call, so uvc_function_ep0_complete() can be called and send received data to the userspace. Signed-off-by: Petr Cvek --- drivers/usb/gadget/function/f_uvc.c | 7 +++ 1 file changed,

[PATCH v5 2/2] usb: typec: add driver for Intel Whiskey Cove PMIC USB Type-C PHY

This adds driver for the USB Type-C PHY on Intel WhiskeyCove PMIC which is available on some of the Intel Broxton SoC based platforms. Signed-off-by: Heikki Krogerus --- drivers/usb/typec/Kconfig | 14 ++ drivers/usb/typec/Makefile | 1 +

[PATCH v5 1/2] usb: USB Type-C connector class

The purpose of USB Type-C connector class is to provide unified interface for the user space to get the status and basic information about USB Type-C connectors on a system, control over data role swapping, and when the port supports USB Power Delivery, also control over power role swapping and

[PATCH v5 0/2] USB Type-C Connector class

Hi, The USB Type-C class is meant to provide unified interface to the userspace to present the USB Type-C ports in a system. Changes since v4: - Remove the port lock completely Changes since v3: - Documentation cleanup as proposed by Roger Quadros - Setting partner altmodes member to NULL on

Re: [Umap2][5/11][22b8:2d93] NULL pointer dereference

On Wed, 2016-08-17 at 13:18 +0300, Binyamin Sharet wrote: > I have retested this issue with ubuntu 16.04, using kernel 4.7-rc2 > and it was not reproduced. Hi, thanks a lot, that was most informative. I'll make a patch for the stable series. The current fix cannot be backported. Thanks

Re: [PATCH] phy: rockchip-inno-usb2: add COMMON_CLK dependency

Am Dienstag, 16. August 2016, 09:31:50 schrieb Guenter Roeck: > On Tue, Aug 16, 2016 at 02:02:00PM +0800, Frank Wang wrote: > > On kernel builds without COMMON_CLK, the newly added rockchip-inno-usb2 > > driver fails to build: > > > > drivers/phy/phy-rockchip-inno-usb2.c:124:16: error: field

Re: [Umap2][5/11][22b8:2d93] NULL pointer dereference

On 08/17/2016 01:06 PM, Oliver Neukum wrote: > On Tue, 2016-08-16 at 16:46 +0300, Binyamin Sharet wrote: >> Kernel version: raspberrypi 4.4.6-v7+ #871 >> Driver source file: drivers/usb/class/cdc-acm.c >> Umap2 command line: umap2vsscan -P -s 22b8:2d93 >> >> After connecting such a device, NULL

Re: [Umap2][5/11][22b8:2d93] NULL pointer dereference

On Tue, 2016-08-16 at 16:46 +0300, Binyamin Sharet wrote: > Kernel version: raspberrypi 4.4.6-v7+ #871 > Driver source file: drivers/usb/class/cdc-acm.c > Umap2 command line: umap2vsscan -P -s 22b8:2d93 > > After connecting such a device, NULL pointer dereference in the kernel > and USB stops

[PATCH 1/2] kaweth: fix firmware download

This fixes the oops discovered by the Umap2 project and Alan Stern. The intf member needs to be set before the firmware is downloaded. Signed-off-by: Oliver Neukum --- drivers/net/usb/kaweth.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git

[PATCH 2/2] kaweth: fix oops upon failed memory allocation

Just return an error upon failure. Signed-off-by: Oliver Neukum --- drivers/net/usb/kaweth.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/net/usb/kaweth.c b/drivers/net/usb/kaweth.c index 37bf715..3cd6906 100644 --- a/drivers/net/usb/kaweth.c +++

Re: [PATCH v9 4/4] arm64: dts: rockchip: configure usb2-phy support for rk3399-evb

Am Freitag, 22. Juli 2016, 15:00:46 schrieb Frank Wang: > Add vcc5v0_host regulator for usb2-phy and enable host-port support. > > Signed-off-by: Frank Wang applied to ny dts64 branch [0] with some changes: - the pin is named vcc5v0_host_en not host_vbus_drv in the

Re: [PATCH v9 3/4] arm64: dts: rockchip: add usb2-phy support for rk3399

Am Freitag, 22. Juli 2016, 15:00:45 schrieb Frank Wang: > Add usb2-phy nodes and specify phys phandle for ehci. > > Signed-off-by: Frank Wang applied to my arm64 dts branch for 4.9 Thanks Heiko -- To unsubscribe from this list: send the line "unsubscribe linux-usb"

Re: [PATCH v5 0/5] da8xx USB PHY platform devices and clocks (was "da8xx UBS clocks")

Hi Kevin, On Saturday 13 August 2016 02:54 AM, Kevin Hilman wrote: > On Wed, May 25, 2016 at 6:18 AM, Sekhar Nori wrote: >> On Monday 23 May 2016 08:44 PM, David Lechner wrote: >>> On 05/09/2016 06:46 PM, David Lechner wrote: v5 changes: renamed "usbphy" to "usb_phy" or

Re: [PATCHv4 0/2] USB Type-C Connector class

On Tue, Aug 16, 2016 at 09:40:16AM -0700, Guenter Roeck wrote: > On Tue, Aug 16, 2016 at 10:38:26AM +0300, Heikki Krogerus wrote: > > Hi guys, > > > > Sorry for the long silence. I just returned from paternal leave. > > > > On Wed, Aug 10, 2016 at 10:19:25AM +0200, Oliver Neukum wrote: > > > On

Re: [PATCH v4 1/2] mfd: ti-smusbdig: Add support for the TI SM-USB-DIG

On Tue, 16 Aug 2016, Andrew F. Davis wrote: > On 08/09/2016 10:27 AM, Lee Jones wrote: > > On Tue, 09 Aug 2016, Andrew F. Davis wrote: > > > >> The TI SM-USB-DIG is a USB to SPI/I2C/1Wire/GPIO adapter. > >> Add MFD core support. > >> > >> Signed-off-by: Andrew F. Davis > >> --- >

Re: [Umap2][3/11][0471:0602] NULL pointer dereference

Hi, On 08/17/2016 10:07 AM, Greg KH wrote: > On Wed, Aug 17, 2016 at 09:05:34AM +0200, Greg KH wrote: >> On Wed, Aug 17, 2016 at 09:26:18AM +0300, Binyamin Sharet wrote: >>> Hi, >>> >>> On 08/16/2016 05:39 PM, Alan Stern wrote: On Tue, 16 Aug 2016, Binyamin Sharet wrote: > Kernel

Re: [Umap2][10/11][1a0a:0102] USB host stops communicating

On Tue, Aug 16, 2016 at 04:51:26PM +0300, Binyamin Sharet wrote: > Kernel version: raspberrypi 4.4.6-v7+ #871 > Umap2 command line: umap2vsscan -P -s 1a0a:0102 > > After connecting such a device, the USB host stops communicating. > > From dmesg: > > [ 5924.751650] usb 1-1.4: new high-speed USB

Re: [Umap2][3/11][0471:0602] NULL pointer dereference

On Wed, Aug 17, 2016 at 09:05:34AM +0200, Greg KH wrote: > On Wed, Aug 17, 2016 at 09:26:18AM +0300, Binyamin Sharet wrote: > > Hi, > > > > On 08/16/2016 05:39 PM, Alan Stern wrote: > > > On Tue, 16 Aug 2016, Binyamin Sharet wrote: > > > > > >> Kernel version: raspberrypi 4.4.6-v7+ #871 > > >>

[PATCH v2] usb3: Fixed usb3 device is not detected in s0 when hotplug usb3 disk under S3

From: Huki Huang When end user inserts a usb3 device and put dut to s3. Then hotplug the usb3 disk under s3. The device will be lost upon resuming from s3. There is a corner case that the hub->change_bits for the usb3 port is not set when usb port change event happens.

Re: [Umap2][3/11][0471:0602] NULL pointer dereference

On Wed, Aug 17, 2016 at 09:26:18AM +0300, Binyamin Sharet wrote: > Hi, > > On 08/16/2016 05:39 PM, Alan Stern wrote: > > On Tue, 16 Aug 2016, Binyamin Sharet wrote: > > > >> Kernel version: raspberrypi 4.4.6-v7+ #871 > >> Driver source file: drivers/input/misc/ati_remote2.c > >> Umap2 command

[PATCH v2] usb3: Fixed usb3 device is not detected in s0 when hotplug usb3 disk under S3

From: Huki Huang When end user inserts a usb3 device and put dut to s3. Then hotplug the usb3 disk under s3. The device will be lost upon resuming from s3. There is a corner case that the hub->change_bits for the usb3 port is not set when usb port change event happens.

[PATCH v2] usb3: Fixed usb3 device is not detected in s0 when hotplug usb3 disk under S3

When end user inserts a usb3 device and put dut to s3. Then hotplug the usb3 disk under s3. The device will be lost upon resuming from s3. There is a corner case that the hub->change_bits for the usb3 port is not set when usb port change event happens. This will cause hub driver ignore the device

[PATCH v2] usb3: Fixed usb3 device is not detected in s0 when hotplug usb3 disk under S3

When end user inserts a usb3 device and put dut to s3. Then hotplug the usb3 disk under s3. The device will be lost upon resuming from s3. There is a corner case that the hub->change_bits for the usb3 port is not set when usb port change event happens. This will cause hub driver ignore the device

[PATCH v2] usb3: Fixed usb3 device is not detected in s0 when hotplug usb3 disk under S3 usb3: Fixed usb3 device is not detected in s0 when hotplug usb3 disk under S3

When end user inserts a usb3 device and put dut to s3. Then hotplug the usb3 disk under s3. The device will be lost upon resuming from s3. There is a corner case that the hub->change_bits for the usb3 port is not set when usb port change event happens. This will cause hub driver ignore the device

Re: [Umap2][9/11][05c5:0002] NULL pointer dereference

On Wed, Aug 17, 2016 at 09:37:02AM +0300, Binyamin Sharet wrote: > Hi > > On 08/16/2016 06:04 PM, Johan Hovold wrote: > > On Tue, Aug 16, 2016 at 10:47:44AM -0400, Alan Stern wrote: > >> On Tue, 16 Aug 2016, Binyamin Sharet wrote: > >> > >>> Kernel version: raspberrypi 4.4.6-v7+ #871 > >>> Driver

[PATCH v2] usb3: Fixed usb3 device is not detected in s0 when hotplug usb3 disk under S3

When end user inserts a usb3 device and put dut to s3. Then hotplug the usb3 disk under s3. The device will be lost upon resuming from s3. There is a corner case that the hub->change_bits for the usb3 port is not set when usb port change event happens. This will cause hub driver ignore the device

Re: [Umap2][9/11][05c5:0002] NULL pointer dereference

Hi On 08/16/2016 06:04 PM, Johan Hovold wrote: > On Tue, Aug 16, 2016 at 10:47:44AM -0400, Alan Stern wrote: >> On Tue, 16 Aug 2016, Binyamin Sharet wrote: >> >>> Kernel version: raspberrypi 4.4.6-v7+ #871 >>> Driver source file: drivers/usb/serial/digi_acceleport.c >>> Umap2 command line:

[PATCH v2] usb3: Fixed usb3 device is not detected in s0 when hotplug usb3 disk under S3

When end user inserts a usb3 device and put dut to s3. Then hotplug the usb3 disk under s3. The device will be lost upon resuming from s3. There is a corner case that the hub->change_bits for the usb3 port is not set when usb port change event happens. This will cause hub driver ignore the device

[PATCH] usb3: Fixed usb3 device is not detected in s0 when hotplug usb3 disk under S3

When end user inserts a usb3 device and put dut to s3. Then hotplug the usb3 disk under s3. The device will be lost upon resuming from s3. There is a corner case that the hub->change_bits for the usb3 port is not set when usb port change event happens. This will cause hub driver ignore the device

[PATCH v2] usb3: Fixed usb3 device is not detected in s0 when hotplug usb3 disk under S3

When end user inserts a usb3 device and put dut to s3. Then hotplug the usb3 disk under s3. The device will be lost upon resuming from s3. There is a corner case that the hub->change_bits for the usb3 port is not set when usb port change event happens. This will cause hub driver ignore the device

Re: [Umap2][2/11][10cf:5500] NULL pointer dereference

Hi On 08/16/2016 04:44 PM, Binyamin Sharet wrote: > Kernel version: 4.4.0-24-generic #43-Ubuntu SMP > Driver source file: drivers/staging/comedi/drivers/vmk80xx.c > Umap2 command line: umap2vsscan -P -s 10cf:5500 > > After connecting such a device, there's oops due to NULL pointer > dereference.

Re: [Umap2][1/11][0aa8:8001] USB stack hang

Hi On 08/16/2016 06:15 PM, Binyamin Sharet wrote: > On 08/16/2016 05:49 PM, Greg KH wrote: >> On Tue, Aug 16, 2016 at 04:42:23PM +0300, Binyamin Sharet wrote: >>> Kernel version: raspberrypi 4.4.6-v7+ #871 >>> Kernel version: 4.4.0-24-generic #43-Ubuntu SMP >>> Driver source file:

[PATCH v2] usb3: Fixed usb3 device is not detected in s0 when hotplug usb3 disk under S3

When end user inserts a usb3 device and put dut to s3. Then hotplug the usb3 disk under s3. The device will be lost upon resuming from s3. There is a corner case that the hub->change_bits for the usb3 port is not set when usb port change event happens. This will cause hub driver ignore the device

Re: [Umap2][3/11][0471:0602] NULL pointer dereference

Hi, On 08/16/2016 05:39 PM, Alan Stern wrote: > On Tue, 16 Aug 2016, Binyamin Sharet wrote: > >> Kernel version: raspberrypi 4.4.6-v7+ #871 >> Driver source file: drivers/input/misc/ati_remote2.c >> Umap2 command line: umap2vsscan -P -s 0471:0602 >> >> After connecting such a device, NULL

[PATCH v2] usb3: Fixed usb3 device is not detected in s0 when hotplug usb3 disk under S3

When end user inserts a usb3 device and put dut to s3. Then hotplug the usb3 disk under s3. The device will be lost upon resuming from s3. There is a corner case that the hub->change_bits for the usb3 port is not set when usb port change event happens. This will cause hub driver ignore the device