[PATCH v3 2/2] phy: mediatek: add XS-PHY driver

Support XS-PHY for MediaTek SoCs with USB3.1 GEN2 controller Signed-off-by: Chunfeng Yun --- drivers/phy/mediatek/Kconfig |9 + drivers/phy/mediatek/Makefile|1 + drivers/phy/mediatek/phy-mtk-xsphy.c | 600 ++ 3

Add MediaTek XS-PHY driver

>From 2ca1243f228633ca9dd96d3e4068af9e2936cd51 Mon Sep 17 00:00:00 2001 From: Chunfeng Yun Date: Thu, 10 May 2018 13:55:52 +0800 Subject: [PATCH v3 0/2] Add MediaTek XS-PHY driver This patch series support the SuperSpeedPlus XS-PHY transceiver for USB3.1 GEN2

[PATCH v3 1/2] dt-bindings: add MediaTek XS-PHY binding

Add a DT binding documentation of XS-PHY for MediaTek SoCs with USB3.1 GEN2 controller Signed-off-by: Chunfeng Yun --- .../devicetree/bindings/phy/phy-mtk-xsphy.txt | 110 1 file changed, 110 insertions(+) create mode 100644

Re: dwc2 (on Meson8b) doesn't detect "hot-plugged" USB devices

Hello Minas, On Mon, May 7, 2018 at 3:27 PM, Minas Harutyunyan wrote: > Hi Martin, > > On 5/7/2018 12:28 AM, Martin Blumenstingl wrote: >> Hello, >> >> I was a bit surprised to see that hot-plugging USB devices on Amlogic >> Meson8b (for example: Odroid-C1) is

Re: [PATCH v2 2/2] usb: dwc3: support clocks and resets for DWC3 core

Hi Martin, 2018-04-28 23:20 GMT+09:00 Martin Blumenstingl : > (adding Yixun from Amlogic to this mail) > > On Sat, Apr 28, 2018 at 4:41 AM, Masahiro Yamada > wrote: >> Hi Martin, >> >> >> 2018-04-24 2:44 GMT+09:00 Martin

Re: [PATCH v3 2/2] usb: misc: xapea00x: perform platform initialization of TPM

On Tue, May 8, 2018 at 10:36 AM, James Bottomley wrote: > > On Tue, 2018-05-08 at 10:29 -0500, David R. Bild wrote: > > On Tue, May 8, 2018 at 10:25 AM, James Bottomley > > wrote: > > > > > > I don't see any reason to

Re: [PATCH v3 2/2] usb: misc: xapea00x: perform platform initialization of TPM

On Wed, May 9, 2018 at 8:59 PM, Jarkko Sakkinen wrote: > On Tue, May 08, 2018 at 08:36:25AM -0700, James Bottomley wrote: >> Early boot means userspace. for a hot pluggable device, this would >> probably be something in udev if you follow the no-daemon model and

[PATCH] USB: rndis: Fix for handling garbled messages

From: Michel Pollet A message can be forged to crash the stack; here we make sure we don't completely break the system if this occurs Signed-off-by: Michel Pollet --- drivers/usb/gadget/function/rndis.c | 3 +++ 1 file changed, 3

Re: [PATCH v3 2/2] usb: misc: xapea00x: perform platform initialization of TPM

On Wed, May 9, 2018 at 8:44 PM, Jarkko Sakkinen wrote: > On Tue, May 08, 2018 at 10:29:41AM -0500, David R. Bild wrote: >> On Tue, May 8, 2018 at 10:25 AM, James Bottomley >> wrote: >> > >> > > On Fri, May 04, 2018 at

usbcore: NULL pointer dereference after detaching USB disk with linux 4.17

Hello, Detaching plugged external usb disk with: "udisksctl power-off --block-device " causes NULL pointer dereference and kernel hang. Tested with 4.17-rc4 on Manjaro Linux config and my own custom config with two different usb disks. It doesn't happen with 4.16.x. Below are logs registered

Re: [PATCH v3 2/2] usb: misc: xapea00x: perform platform initialization of TPM

On Tue, May 8, 2018 at 5:47 AM, Jarkko Sakkinen wrote: > > On Fri, May 04, 2018 at 08:00:22AM -0500, David R. Bild wrote: > > Normally the system platform (i.e., BIOS/UEFI for x86) is responsible > > for performing initialization of the TPM. For these modules,

RE: [PATCH v2 0/6] usb: gadget: udc: renesas_usb3: fix some major issues

Hi Felipe, > From: Yoshihiro Shimoda, Sent: Tuesday, April 10, 2018 2:39 PM > > This patch set is based on v4.16. Would you review this patch set? I checked this is able to be applied on your testing/fixes branch. Best regards, Yoshihiro Shimoda > Changes from v1: > - Add Reviewed-by in

Re: [PATCH v3 2/2] usb: misc: xapea00x: perform platform initialization of TPM

On Thu, 2018-05-10 at 09:25 -0500, David R. Bild wrote: > On Tue, May 8, 2018 at 10:36 AM, James Bottomley > wrote: > > > > On Tue, 2018-05-08 at 10:29 -0500, David R. Bild wrote: > > > On Tue, May 8, 2018 at 10:25 AM, James Bottomley > > >

Re: [PATCH v3 2/2] usb: misc: xapea00x: perform platform initialization of TPM

On Thu, May 10, 2018 at 9:47 AM, James Bottomley wrote: > On Thu, 2018-05-10 at 09:25 -0500, David R. Bild wrote: >> The TPM holds access credentials for connecting to the Xaptum >> network. > > OK, so these are effectively DevId keys. However, what makes

Re: [PATCH v3 2/2] usb: misc: xapea00x: perform platform initialization of TPM

On Tue, May 8, 2018 at 5:55 AM, Jarkko Sakkinen wrote: > On Fri, May 04, 2018 at 02:56:25PM -0500, David R. Bild wrote: >> On Fri, May 4, 2018 at 2:06 PM, Jason Gunthorpe wrote: >> > >> > On Fri, May 04, 2018 at 08:00:22AM -0500, David R. Bild

Race related to e04a0442d33b "HID: core: remove the absolute need of hid_have_special_driver[]"

Due to some other issue with one devices supported by hid-led I figured out that it's no longer needed to list devices with own driver in hid_have_special_driver[]. So I removed the entries for the hid-led devices and got the following. When I plugged in the device first the device-specific

Re: [PATCH v3 1/2] usb: dwc2: alloc dma aligned buffer for isoc split in

Hi, On Wed, May 9, 2018 at 1:55 AM, wlf wrote: > + } else if (hsotg->params.host_dma) { Are you sure this is "else if"? Can't you have descriptor DMA enabled in the controller and still need to do a normal DMA transfer if you plug in a hub?

Re: [PATCH v4 1/2] usb: dwc2: alloc dma aligned buffer for isoc split in

Hi, On Wed, May 9, 2018 at 3:11 AM, William Wu wrote: > The commit 3bc04e28a030 ("usb: dwc2: host: Get aligned DMA in > a more supported way") rips out a lot of code to simply the > allocation of aligned DMA. However, it also introduces a new > issue when use isoc