Re: [PATCH v4 0/3] Introduce USB charger support in USB phy

Hi Felipe, On 27 July 2017 at 13:14, Baolin Wang wrote: > Currently the Linux kernel does not provide any standard integration of this > feature that integrates the USB subsystem with the system power regulation > provided by PMICs meaning that either vendors must add

[PATCH v2 4/4] dt-bindings: phy-mt65xx-usb: supports PCIe, SATA and rename file

add support for PCIe and SATA, also add some new compatibles. due to phy-mt65xx-usb.txt holds the bindings for all mediatek SoCs with T-PHY controller, change the name to phy-mtk-tphy.txt to reflect that. Signed-off-by: Chunfeng Yun --- .../phy/{phy-mt65xx-usb.txt =>

[PATCH v2 1/4] phy: phy-mt65xx-usb3: add PCIe PHY support

From: Ryder Lee This patch adds PCIe PHY setting part. Signed-off-by: Ryder Lee Signed-off-by: Chunfeng Yun --- drivers/phy/phy-mt65xx-usb3.c | 228 ++ 1 file changed, 206

[PATCH v2 3/4] phy: phy-mt65xx-usb3: add mediatek directory and rename file

The driver is actually for T-PHY which supports USB3.0, PCIe and SATA, and supports more SoCs now, but not just only for series of mt65xx SoCs, so the name of file, data struct, functions etc with 'mt65xx' may cause misunderstanding when new SoCs are supported. Here rename them to reflect the real

[PATCH v2 2/4] phy: phy-mt65xx-usb3: add SATA PHY support

From: Ryder Lee This patch adds SATA setting part. Signed-off-by: Ryder Lee Signed-off-by: Chunfeng Yun --- drivers/phy/phy-mt65xx-usb3.c | 133 -- 1 file changed, 129

Re: new usb LTE modem device

On 8/9/2017 02:33, Bjørn Mork wrote: The qmi_wwan part looks fine to me. But you will need to split it in two patches since the two drivers are parts of different subsystems. The option driver use interface blacklists instead of multiple match entries. You should probably follow the same

Re: [PATCH net,stable] qmi_wwan: fix NULL deref on disconnect

From: Bjørn Mork Date: Tue, 8 Aug 2017 18:02:11 +0200 > qmi_wwan_disconnect is called twice when disconnecting devices with > separate control and data interfaces. The first invocation will set > the interface data to NULL for both interfaces to flag that the > disconnect has

Re: [PATCH v2 2/4] usb: common: Move u_serial from gadget/function to usb/common

Hi, On 08/08/2017 02:14 PM, Felipe Balbi wrote: > Hi, > > Lu Baolu writes: >>> Lu Baolu writes: The component u_serial provides a glue layer between TTY layer and a USB gadget device needed to provide a basic serial port

[PATCH v2] usb: dwc2: skip L2 state of hcd if work in device mode

The gadget may fail to enqueue request if the controller has enter L2 state. This patch prevent enter L2 state in hcd driver if the controller works in device mode. Change in v2:None, resend to addition maintainer Meng Dongyang (1): usb: dwc2: skip L2 state of hcd if controller work in device

[PATCH v2] usb: dwc2: skip L2 state of hcd if controller work in device mode

In the case hcd autosuspend is enabled, the hcd will enter L2 state if no device connected. But if the controller works in otg mode, the gadget driver still works in L0 state if connected with host. This may result in transfer fail when gadget enqueue new request but the hcd driver has set the

Re: [PATCH 4/4] dt-bindings: phy-mt65xx-usb: supports PCIe, SATA and rename file

On Tue, 2017-08-08 at 17:44 +0530, Kishon Vijay Abraham I wrote: > Chunfeng > > On Thursday 03 August 2017 03:50 PM, Chunfeng Yun wrote: > > hi, > > > > I made a mistake, please ignore the patches with Change-Id, very sorry > > No problem. However can you resend the series after fixing all

[PATCH] usb: ehci-omap: fix error return code in ehci_hcd_omap_probe()

platform_get_irq() returns an error code, but the ehci-omap driver ignores it and always returns -ENODEV. This is not correct and, prevents -EPROBE_DEFER from being propagated properly. Also, notice that platform_get_irq() no longer returns 0 on error:

[PATCH] usb: gadget: udc: renesas_usb3: fix error return code in renesas_usb3_probe()

platform_get_irq() returns an error code, but the renesas_usb3 driver ignores it and always returns -ENODEV. This is not correct and, prevents -EPROBE_DEFER from being propagated properly. Also, notice that platform_get_irq() no longer returns 0 on error:

Re: AW: new usb LTE modem device

On Tue, 2017-08-08 at 22:22 +0200, Giuseppe Lippolis wrote: > > The option driver use interface blacklists instead of multiple > > match entries. > > You should probably follow the same style there. But this is up to > > Johan... > > Can I ask what ist he difference between .sendsetup and

AW: new usb LTE modem device

> The option driver use interface blacklists instead of multiple match entries. > You should probably follow the same style there. But this is up to Johan... Can I ask what ist he difference between .sendsetup and .reserved and how to use the bitmask in drivers/usb/serial/option.c ? Thanks,

[PATCH] USB: serial: pl2303: add new ATEN device id

This adds a new ATEN device id for a new pl2303-based device. Reported-by: Peter Kuo Cc: stable Signed-off-by: Greg Kroah-Hartman --- Peter, can you test this patch and verify it works for you? Is there a better name

Re: BUG/PATCH: cp210x.c - reenable support for chips which don't report a partnum

On Tue, Aug 08, 2017 at 08:59:01PM +0200, Sebastian Frei wrote: > Hi, > > I own a data cable for Siemens mobile phones: > 10ab:10c5 USI Co., Ltd Sony-Ericsson / Samsung DataCable > > The cp210x chip of this cable seems to not give an answer to the > CP210X_GET_PARTNUM command. So since this

Re: new usb LTE modem device

On August 8, 2017 9:22:29 PM CEST, Giuseppe Lippolis wrote: >> But we already have many Sierra devices with 2 QMI interfaces (the >3rd one >> is documented and verified non-functional for unknown reasons). And >these >> tend to come with multiple OEM device IDs. So a

AW: new usb LTE modem device

> But we already have many Sierra devices with 2 QMI interfaces (the 3rd one > is documented and verified non-functional for unknown reasons). And these > tend to come with multiple OEM device IDs. So a whitelist method could > reduce the number of matching entries considerably. Feel free to

BUG/PATCH: cp210x.c - reenable support for chips which don't report a partnum

Hi, I own a data cable for Siemens mobile phones: 10ab:10c5 USI Co., Ltd Sony-Ericsson / Samsung DataCable The cp210x chip of this cable seems to not give an answer to the CP210X_GET_PARTNUM command. So since this commit: 2016-10-24 USB: serial: cp210x: Adding GPIO support for CP2105

Re: [PATCH v3] dma-mapping: skip USB devices when configuring DMA during probe

On Sat, Aug 05, 2017 at 10:38:07AM +0200, Christoph Hellwig wrote: > I think the root problem is that the code added by > " of/acpi: Configure dma operations at probe time for platform/amba/pci bus > devices" > > is completely bogus and needs to be reverted. We can't simply iterate > over all

[PATCH 10/35] net: usb: catc: constify usb_device_id and fix space before '[' error

usb_device_id are not supposed to change at runtime. All functions working with usb_device_id provided by work with const usb_device_id. So mark the non-const structs as const. Fix checkpatch.pl error: ERROR: space prohibited before open square bracket '['. Signed-off-by: Arvind Yadav

[PATCH 12/35] net: usb: ipheth: constify usb_device_id

usb_device_id are not supposed to change at runtime. All functions working with usb_device_id provided by work with const usb_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/net/usb/ipheth.c | 2 +- 1 file changed, 1

[PATCH 11/35] net: usb: cdc-phonet: constify usb_device_id

usb_device_id are not supposed to change at runtime. All functions working with usb_device_id provided by work with const usb_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/net/usb/cdc-phonet.c | 2 +- 1 file changed, 1

[PATCH net,stable] qmi_wwan: fix NULL deref on disconnect

qmi_wwan_disconnect is called twice when disconnecting devices with separate control and data interfaces. The first invocation will set the interface data to NULL for both interfaces to flag that the disconnect has been handled. But the matching NULL check was left out when qmi_wwan_disconnect

[PATCH 13/35] net: usb: kaweth: constify usb_device_id

usb_device_id are not supposed to change at runtime. All functions working with usb_device_id provided by work with const usb_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/net/usb/kaweth.c | 2 +- 1 file changed, 1

[PATCH 14/35] net: usb: r8152: constify usb_device_id

usb_device_id are not supposed to change at runtime. All functions working with usb_device_id provided by work with const usb_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/net/usb/r8152.c | 2 +- 1 file changed, 1

[PATCH 15/35] net: usb: rtl8150: constify usb_device_id

usb_device_id are not supposed to change at runtime. All functions working with usb_device_id provided by work with const usb_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/net/usb/rtl8150.c | 2 +- 1 file changed, 1

Re: [PATCH] usb: gadget: f_uac2: calculate wMaxPacketSize before endpoint match

On Tuesday 08 August 2017 07:50 PM, Roger Quadros wrote: > On 17/05/17 11:15, Sekhar Nori wrote: >> Calculate wMaxPacketSize before endpoint matching the >> descriptor is found. >> >> This allows audio gadget to be used with controllers >> which have a shortage or unavailability of endpoints >>

Re: [PATCH] usb: gadget: f_uac2: calculate wMaxPacketSize before endpoint match

On 17/05/17 11:15, Sekhar Nori wrote: > Calculate wMaxPacketSize before endpoint matching the > descriptor is found. > > This allows audio gadget to be used with controllers > which have a shortage or unavailability of endpoints > that can handle max packet size of 1023 (FS) or 1024 > (HS). > >

Re: [PATCH v2 2/3] usb: chipidea: Hook into mux framework to toggle usb switch

On 2017-08-08 03:51, Stephen Boyd wrote: > Quoting Peter Rosin (2017-07-31 03:33:22) >> On 2017-07-14 23:40, Stephen Boyd wrote: >>> @@ -1964,16 +1965,26 @@ void ci_hdrc_gadget_destroy(struct ci_hdrc *ci) >>> >>> static int udc_id_switch_for_device(struct ci_hdrc *ci) >>> { >>> + int ret =

Re: [PATCH 4/4] dt-bindings: phy-mt65xx-usb: supports PCIe, SATA and rename file

Chunfeng On Thursday 03 August 2017 03:50 PM, Chunfeng Yun wrote: > hi, > > I made a mistake, please ignore the patches with Change-Id, very sorry No problem. However can you resend the series after fixing all checkpatch warnings? Thanks Kishon -- To unsubscribe from this list: send the line

[PATCH] usb/dwc3:constify dev_pm_ops

dev_pm_ops is not supposed to change at runtime. Marking it constant. Signed-off-by: Doug Wilson --- drivers/usb/dwc3/dwc3-pci.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/usb/dwc3/dwc3-pci.c b/drivers/usb/dwc3/dwc3-pci.c index

[PATCH v3] usb: quirks: Add no-lpm quirk for Moshi USB to Ethernet Adapter

Moshi USB to Ethernet Adapter internally uses a Genesys Logic hub to connect to Realtek r8153. The Realtek r8153 ethernet does not work on the internal hub, no-lpm quirk can make it work. Since another r8153 dongle at my hand does not have the issue, so add the quirk to the Genesys Logic hub

RE: [PATCH v2 1/1] usbip: auto retry for concurrent attach

Hello, > -Original Message- > From: Shuah Khan [mailto:sh...@kernel.org] > Sent: Thursday, August 03, 2017 2:27 AM > To: fx IWATA NOBUO ; > valentina.mane...@gmail.com; gre...@linuxfoundation.org; > linux-usb@vger.kernel.org > Cc: fx MICHIMURA TADAO

Re: [PATCH v2] usb: quirks: Add no-lpm quirk for Moshi USB to Ethernet Adapter

On Tue, Aug 8, 2017 at 4:28 PM, Oliver Neukum wrote: > Am Dienstag, den 08.08.2017, 14:32 +0800 schrieb Kai-Heng Feng: >> Moshi USB to Ethernet Adapter internally uses a Genesys Logic hub to >> connect to Realtek r8153. >> >> The Realtek r8153 ethernet does not work on the

Re: [PATCH] append Qualcomm GOBI 2K chipset ID for Panasonic CF-U1 Toughbook

Johan Hovold writes: > On Mon, Aug 07, 2017 at 04:22:27PM +0200, Oleg Kokorin wrote: >> From 336f8adb0292a25ea41f0515a80850031f814b9b Mon Sep 17 00:00:00 2001 >> From: Oleg Kokorin >> Date: Mon, 7 Aug 2017 15:35:53 +0200 >> Subject: [PATCH] append Qualcomm

Re: [PATCH v2] usb: quirks: Add no-lpm quirk for Moshi USB to Ethernet Adapter

Am Dienstag, den 08.08.2017, 14:32 +0800 schrieb Kai-Heng Feng: > Moshi USB to Ethernet Adapter internally uses a Genesys Logic hub to > connect to Realtek r8153. > > The Realtek r8153 ethernet does not work on the internal hub, no-lpm quirk > can make it work. > > Since another r8153 dongle at

Re: new usb LTE modem device

"Giuseppe Lippolis" writes: > Hi all, > I'm working to port OpenWRT/LEDE on a new router with embedded usb LTE > modem. > The modem have 3 qmi_wwan interfaces and 2 option. > > I would like to prepare the patch, but before I would like to know if using > the

[PATCH v2] usb: quirks: Add no-lpm quirk for Moshi USB to Ethernet Adapter

Moshi USB to Ethernet Adapter internally uses a Genesys Logic hub to connect to Realtek r8153. The Realtek r8153 ethernet does not work on the internal hub, no-lpm quirk can make it work. Since another r8153 dongle at my hand does not have the issue, so add the quirk to the hub instead.

Re: [PATCH v2 2/4] usb: common: Move u_serial from gadget/function to usb/common

Hi, Lu Baolu writes: >> Lu Baolu writes: >>> The component u_serial provides a glue layer between TTY layer >>> and a USB gadget device needed to provide a basic serial port >>> functionality. Currently, u_serial sits under gadget/function