Re: [PATCH 00/47] arch-removal: device drivers

Hi Arnd, On Wed, 14 Mar 2018 16:35:13 +0100 Arnd Bergmann wrote: > Hi driver maintainers, > > I just posted one series with the removal of eight architectures, > see https://lkml.org/lkml/2018/3/14/505 for details, or > https://lwn.net/Articles/748074/ for more background. > >

Re: [PATCH v3 07/12] staging: typec: tcpci: register port before request irq

On Tue, Mar 13, 2018 at 05:34:33PM +0800, Li Jun wrote: > With that we can clear any pending events and the port is registered > so driver can be ready to handle typec events once we request irq. > > Signed-off-by: Peter Chen > Signed-off-by: Li Jun > --- >

Re: [PATCH v3 08/12] staging: typec: tcpci: enable vbus detection

On Tue, Mar 13, 2018 at 05:34:34PM +0800, Li Jun wrote: > TCPCI implementation may need SW to enable VBUS detection to generate > power status events. > > Signed-off-by: Li Jun Makes sense to me. Only question might be if this should be dones before checking the power status at

Re: [PATCH v3 11/12] staging: typec: tcpci: Only touch target bit when enable vconn

On Tue, Mar 13, 2018 at 05:34:37PM +0800, Li Jun wrote: > We need regmap_update_bits to avoid touch any other bits when > enable or disable vconn. > > Signed-off-by: Li Jun Reviewed-by: Guenter Roeck > --- > drivers/staging/typec/tcpci.c | 9 +++-- > 1

Intel GemniLake xHCI connected devices can never wake up the system from suspend

Hi, I have a ASUS AIO V222GA and another Acer Desktop XC-830 both have Intel CPU J5005 and they both hit the same problem. The XHCI connected USB keyboard/mouse can never wakeup the system from suspend. It reminds me that similiar thing happens on ApolloLake too which needs the

DWC2 maintainership change

Hi Felipe, Greg, I won't be able to continue maintainership of dwc2. Minas Harutyunyan, has been doing most of the communication on linux-usb lately and much of the maintenance and development work. He has excellent knowledge of the controller, having worked with it since its inception many

Re: Debugging SCSI 'UNMAP' ("Logical Block Provisioning") failure on an SSD

Kashyap, > Sorry, I didn't give you complete information — with the previous > `dmesg` output, I actually attached the SSD (Samsung T5) via regular USB > "A Cable". > > Now, I re-attached the SSD via the "Thunderbolt" port on my other laptop > (Lenovo T470s), it _does_ show "UAS". Refer the

Re: [PATCH v4 13/15] usb: dwc3: Add workaround for isoc start transfer failure

Hi Felipe, On 3/14/2018 1:56 AM, Felipe Balbi wrote: > > Hi, > > Thinh Nguyen writes: >>> Thinh Nguyen writes: In DWC_usb31 version 1.70a-ea06 and prior, for highspeed and fullspeed isochronous IN, BIT[15:14] of the 16-bit

Re: [PATCH] lan78xx: Connect phy early

> @@ -2082,8 +2082,6 @@ static int lan78xx_phy_init(struct lan78xx_net *dev) > > dev->fc_autoneg = phydev->autoneg; > > - phy_start(phydev); > - > netif_dbg(dev, ifup, dev->net, "phy initialised successfully"); > > return 0; > @@ -2512,9 +2510,7 @@ static int

Re: Leak of queue heads in DWC2 driver?

On Tue, 13 Mar 2018 06:22:30 +, Minas Harutyunyan wrote: > Hi Paul, > > On 3/13/2018 6:26 AM, Paul Zimmerman wrote: > > Hi Minas, > > > > While ‌looking at the QH queuing in the DWC2 driver, I think I've found > > some places where the QH struct may not be

[PATCH] USB: misc: uss720: more vendor/product ID's

Reporting two more VID/PID pairs that work with this driver, having used an informational webpage as a buying guide now. The page listed additional working VID/PID pairs but did not include these two. None were upstreamed. Also taking this opportunity to sort the

Re: [PATCH v4 2/2] usb/gadget: Add driver for Aspeed SoC virtual hub

On Wed, 2018-03-14 at 10:54 +0200, Felipe Balbi wrote: > Hi, > > Benjamin Herrenschmidt writes: > > On Tue, 2018-03-13 at 09:35 +1100, Benjamin Herrenschmidt wrote: > > > On Fri, 2018-03-09 at 11:20 +0200, Felipe Balbi wrote: > > > > > > > > > diff --git

Re: [RFC v3] Add support for Sony PS2 OHCI

On Wed, 14 Mar 2018, Fredrik Noring wrote: > Hi Alan Stern, > > > > > What happened to the changes to ohci_run() and ohci_irq() that were in > > > > v2 of this RFC? Did you decide they weren't needed? > > > > > > In v3 Jürgen Urban folded those changes into the driver functions > > > > > >

uvc-gadget created with configfs sets all bFrameIndex to 1

I am currently working on an application for my master thesis that does transparent inline modification of frames received from a uvc webcam which are served to the actual host through a uvc gadget mimicking the underlying webcam. I recently noticed that the host side v4l2 driver would only ever

Re: [RFC v3] Add support for Sony PS2 OHCI

Hi Alan Stern, > > > What happened to the changes to ohci_run() and ohci_irq() that were in > > > v2 of this RFC? Did you decide they weren't needed? > > > > In v3 Jürgen Urban folded those changes into the driver functions > > > > ohci_ps2_enable(), > > ohci_ps2_disable(), > >

Re: [PATCH v3 09/12] typec: tcpm: add starting value for drp toggling

On Tue, Mar 13, 2018 at 05:34:35PM +0800, Li Jun wrote: > As DRP port autonomously toggles the Rp/Rd need a start value to > begin with, so add one parameter for it in tcpm_start_drp_toggling. > > Signed-off-by: Li Jun Reviewed-by: Guenter Roeck > --- >

Re: WARN_ON(irqs_disabled()) in dma_free_attrs?

On 13/03/18 13:17, Christoph Hellwig wrote: On Tue, Mar 13, 2018 at 12:11:49PM +, Robin Murphy wrote: Taking a step back, though, provided the original rationale about dma_declare_coherent_memory() is still valid, I wonder if we should simply permit the USB code to call

Re: [PATCH 38/47] usb: musb: remove blackfin port

Hi, On Wed, Mar 14, 2018 at 04:35:51PM +0100, Arnd Bergmann wrote: > The blackfin architecture is getting removed, so we can clean up > all the special cases in the musb driver. > > Signed-off-by: Arnd Bergmann > --- > drivers/usb/musb/Kconfig| 10 +- >

Re: [PATCH 37/47] usb: host: remove tilegx platform glue

On Wed, 14 Mar 2018, Greg Kroah-Hartman wrote: > On Wed, Mar 14, 2018 at 04:35:50PM +0100, Arnd Bergmann wrote: > > The tile architecture is getting removed, so the ehci and ohci platform > > glue drivers are no longer needed. In case of ohci, this is the last > > one to define a PLATFORM_DRIVER

Re: [PATCH 38/47] usb: musb: remove blackfin port

On Wed, Mar 14, 2018 at 04:35:51PM +0100, Arnd Bergmann wrote: > The blackfin architecture is getting removed, so we can clean up > all the special cases in the musb driver. > > Signed-off-by: Arnd Bergmann > --- > drivers/usb/musb/Kconfig| 10 +- >

Re: [PATCH 37/47] usb: host: remove tilegx platform glue

On Wed, Mar 14, 2018 at 04:35:50PM +0100, Arnd Bergmann wrote: > The tile architecture is getting removed, so the ehci and ohci platform > glue drivers are no longer needed. In case of ohci, this is the last > one to define a PLATFORM_DRIVER macro, so we can remove even more. > > Signed-off-by:

Re: [PATCH 2/2] usb: host: xhci-plat: Fix clock resource by adding a register clock

Hi Rob, (resent because of malformed cc list) On mer., févr. 28 2018, Mathias Nyman wrote: > On 14.02.2018 18:16, Gregory CLEMENT wrote: >> On Armada 7K/8K we need to explicitly enable the register clock. This >> clock is optional because not all the SoCs using this

[PATCH 38/47] usb: musb: remove blackfin port

The blackfin architecture is getting removed, so we can clean up all the special cases in the musb driver. Signed-off-by: Arnd Bergmann --- drivers/usb/musb/Kconfig| 10 +- drivers/usb/musb/Makefile | 1 - drivers/usb/musb/blackfin.c | 623

[PATCH 37/47] usb: host: remove tilegx platform glue

The tile architecture is getting removed, so the ehci and ohci platform glue drivers are no longer needed. In case of ohci, this is the last one to define a PLATFORM_DRIVER macro, so we can remove even more. Signed-off-by: Arnd Bergmann --- drivers/usb/host/ehci-hcd.c| 5 -

Re: [PATCH 2/3] usb: host: pci: introduce PCI vendor ID for Netlogic

On 03/14/2018 04:27 PM, Oliver Neukum wrote: > Am Mittwoch, den 14.03.2018, 14:31 +0100 schrieb Richard Leitner: >> Hi Oliver, >> thank you for your feedback! >> >> On 03/14/2018 01:17 PM, Oliver Neukum wrote: >>> Am Mittwoch, den 14.03.2018, 11:29 +0100 schrieb Richard Leitner: From:

[PATCH 00/47] arch-removal: device drivers

Hi driver maintainers, I just posted one series with the removal of eight architectures, see https://lkml.org/lkml/2018/3/14/505 for details, or https://lwn.net/Articles/748074/ for more background. These are the device drivers that go along with them. I have already picked up the drivers for

Re: [PATCH 2/3] usb: host: pci: introduce PCI vendor ID for Netlogic

Am Mittwoch, den 14.03.2018, 14:31 +0100 schrieb Richard Leitner: > Hi Oliver, > thank you for your feedback! > > On 03/14/2018 01:17 PM, Oliver Neukum wrote: > > Am Mittwoch, den 14.03.2018, 11:29 +0100 schrieb Richard Leitner: > > > From: Richard Leitner > > > > >

RE: [PATCH] lan78xx: Connect phy early

Hi Alexander, Thanks for patch. We will look into it if there is any corner case Such as plug in/out while operations. Woojung > -Original Message- > From: Alexander Graf [mailto:ag...@suse.de] > Sent: Wednesday, March 14, 2018 10:55 AM > To: Woojung Huh - C21699

[PATCH] lan78xx: Connect phy early

When using wicked with a lan78xx device attached to the system, we end up with ethtool commands issued on the device before an ifup got issued. That lead to the following crash: Unable to handle kernel NULL pointer dereference at virtual address 039c pgd = 800035b3

[PATCH 11/16] treewide: simplify Kconfig dependencies for removed archs

A lot of Kconfig symbols have architecture specific dependencies. In those cases that depend on architectures we have already removed, they can be omitted. Signed-off-by: Arnd Bergmann --- block/bounce.c | 2 +- drivers/ide/Kconfig | 2 +-

[PATCH 00/16] remove eight obsolete architectures

Here is the collection of patches I have applied to my 'asm-generic' tree on top of the 'metag' removal. This does not include any of the device drivers, I'll send those separately to a someone different list of people. The removal came out of a discussion that is now documented at

Re: [PATCH v1 2/2] usb: dwc3: Add Qualcomm DWC3 glue driver

Hi, On Wed, Mar 14, 2018 at 10:50:12AM +0200, Felipe Balbi wrote: > >>> - Support to replace pip3 clock going to DWC3 with utmi clock > >>>for hardware configuration where SSPHY is not used with DWC3. > >> Is that SW configurable? Really? In any case seems like this and SESSVLD > >> valid

Re: [PATCH 2/3] usb: host: pci: introduce PCI vendor ID for Netlogic

Hi Oliver, thank you for your feedback! On 03/14/2018 01:17 PM, Oliver Neukum wrote: > Am Mittwoch, den 14.03.2018, 11:29 +0100 schrieb Richard Leitner: >> From: Richard Leitner >> >> Replace the hardcoded PCI vendor ID of Netlogic with a definition in >> pci_ids.h >

Re: [PATCH] usb: dwc2: Fix interval type issue

On 3/14/2018 2:12 PM, Minas Harutyunyan wrote: > On 2/6/2018 7:07 PM, Grigor Tovmasyan wrote: >> The maximum value that unsigned char can hold is 255, meanwhile >> the maximum value of interval is 2^(bIntervalMax-1)=2^15. >> >> Signed-off-by: Grigor Tovmasyan >> --- >>

[PATCH v8 00/12] USB Type-C device-connection, mux and switch support

Hi, This is version 8 of series we prepare with Hans where we are introducing support for USB muxes and generic device connections. The only change in this version is to patch 1/12 (the device connections), where we are no longer using rcu. Greg pointed out that we are not doing anything heavy

[PATCH v8 01/12] drivers: base: Unified device connection lookup

Several frameworks - clk, gpio, phy, pmw, etc. - maintain lookup tables for describing connections and provide custom API for handling them. This introduces a single generic lookup table and API for the connections. The motivation for this commit is centralizing the connection lookup, but the

[PATCH v8 05/12] usb: typec: tcpm: Set USB role switch to device mode when configured as such

From: Hans de Goede Setting the mux to MUX_NONE and the switch to USB_SWITCH_DISCONNECT when the data-role is device is not correct. Plenty of devices support operating as USB device through a (separate) USB device controller. We really need 2 different versions of

[PATCH v8 04/12] usb: typec: Separate the definitions for data and power roles

USB Type-C specification v1.2 separated the power and data roles more clearly. Dual-Role-Data term was introduced, and the meaning of DRP was changed from "Dual-Role-Port" to "Dual-Role-Power". In order to allow the port drivers to describe the capabilities of the ports more clearly according to

[PATCH v8 06/12] usb: typec: tcpm: Use new Type-C switch/mux and usb-role-switch functions

From: Hans de Goede Remove the unused (not implemented anywhere) tcpc_mux_dev abstraction and replace it with calling the new typec_set_orientation, usb_role_switch_set and typec_set_mode functions. Signed-off-by: Hans de Goede Reviewed-by: Guenter

[PATCH v8 07/12] xhci: Add option to get next extended capability in list by passing id = 0

From: Mathias Nyman Modify xhci_find_next_ext_cap(base, offset, id) to return the next capability offset if 0 is passed for id. Otherwise it will behave as previously and return the offset of the next capability with matching id capability id 0 is not used by xHCI

[PATCH v8 08/12] xhci: Add Intel extended cap / otg phy mux handling

From: Hans de Goede The xHCI controller on various Intel SoCs has an extended cap mmio-range which contains registers to control the muxing to the xHCI (host mode) or the dwc3 (device mode) and vbus-detection for the otg usb-phy. Having a role-sw driver included in the xHCI

[PATCH v8 12/12] extcon: axp288: Set USB role where necessary

From: Hans de Goede The AXP288 BC1.2 charger detection / extcon code may seem like a strange place to add code to control the USB role-switch on devices with an AXP288, but there are 2 reasons to do this inside the axp288 extcon code: 1) On many devices the USB role is

[PATCH v8 10/12] usb: typec: driver for Pericom PI3USB30532 Type-C cross switch

From: Hans de Goede Add a driver for the Pericom PI3USB30532 Type-C cross switch / mux chip found on some devices with a Type-C port. Signed-off-by: Hans de Goede Reviewed-by: Andy Shevchenko Signed-off-by: Heikki Krogerus

[PATCH v8 09/12] usb: roles: Add Intel xHCI USB role switch driver

From: Hans de Goede Various Intel SoCs (Cherry Trail, Broxton and others) have an internal USB role switch for swiching the OTG USB data lines between the xHCI host controller and the dwc3 gadget controller. Note on some Cherry Trail systems there is ACPI/AML code listening

[PATCH v8 11/12] platform/x86: intel_cht_int33fe: Add device connections for the Type-C port

From: Hans de Goede We need to add device-connections for the Type-C mux/switch and usb-role code to be able to find the PI3USB30532 Type-C cross-switch and the device/host role-switch integrated in the CHT SoC. Signed-off-by: Hans de Goede

[PATCH v8 03/12] usb: common: Small class for USB role switches

USB role switch is a device that can be used to choose the data role for USB connector. With dual-role capable USB controllers, the controller itself will be the switch, but on some platforms the USB host and device controllers are separate IPs and there is a mux between them and the connector. On

[PATCH v8 02/12] usb: typec: API for controlling USB Type-C Multiplexers

USB Type-C connectors consist of various muxes and switches that route the pins on the connector to the right locations. The USB Type-C drivers need to be able to control the muxes, as they are the ones that know things like the cable plug orientation, and the current mode that was negotiated with

Re: Debugging SCSI 'UNMAP' ("Logical Block Provisioning") failure on an SSD

On Wed, Mar 14, 2018 at 12:29:50PM +0100, Oliver Neukum wrote: > Am Mittwoch, den 14.03.2018, 11:22 +0100 schrieb Kashyap Chamarthy: > > I see.  So I ran `dmesg -w`, as I attached the disk & see the following: > > UAS and no quirk for your device. It looks like it indeed just does > not support

Re: [PATCH v7 01/12] drivers: base: Unified device connection lookup

On Wed, Mar 14, 2018 at 02:13:23PM +0200, Heikki Krogerus wrote: > > Sorry I missed this the last review cycles. > > Np. I'll prepare v8. This will not affect the other patches, so is it > enough if I just update this patch? Or do you prefer that I re-send > the whole series? Resending the whole

Re: [PATCH 2/3] usb: host: pci: introduce PCI vendor ID for Netlogic

Am Mittwoch, den 14.03.2018, 11:29 +0100 schrieb Richard Leitner: > From: Richard Leitner > > Replace the hardcoded PCI vendor ID of Netlogic with a definition in > pci_ids.h Hi, in general, why? Does this patch generate any benefit for any developer reading the

Re: [PATCH v7 01/12] drivers: base: Unified device connection lookup

On Wed, Mar 14, 2018 at 12:16:05PM +0100, Greg Kroah-Hartman wrote: > On Mon, Mar 12, 2018 at 05:34:20PM +0300, Heikki Krogerus wrote: > > Several frameworks - clk, gpio, phy, pmw, etc. - maintain > > lookup tables for describing connections and provide custom > > API for handling them. This

Re: [PATCH 2/3] usb: host: pci: introduce PCI vendor ID for Netlogic

On Wed, Mar 14, 2018 at 12:36:17PM +0100, Richard Leitner wrote: > > On 03/14/2018 11:48 AM, Greg KH wrote: > > On Wed, Mar 14, 2018 at 11:29:32AM +0100, Richard Leitner wrote: > >> From: Richard Leitner > >> > >> Replace the hardcoded PCI vendor ID of Netlogic with

Re: [PATCH 2/3] usb: host: pci: introduce PCI vendor ID for Netlogic

On 03/14/2018 11:48 AM, Greg KH wrote: > On Wed, Mar 14, 2018 at 11:29:32AM +0100, Richard Leitner wrote: >> From: Richard Leitner >> >> Replace the hardcoded PCI vendor ID of Netlogic with a definition in >> pci_ids.h > > Why? It's only being used in one file, so

Re: [PATCH 3/3] usb: host: pci: replace hardcoded renesas PCI IDs

On 03/14/2018 11:49 AM, Greg KH wrote: > On Wed, Mar 14, 2018 at 11:29:33AM +0100, Richard Leitner wrote: >> From: Richard Leitner >> >> Introduce Renesas uPD72020{1,2} PCI device IDs in pci_ids.h and replace >> the harcoded values with them. >> >> Signed-off-by:

Re: Debugging SCSI 'UNMAP' ("Logical Block Provisioning") failure on an SSD

Am Mittwoch, den 14.03.2018, 11:22 +0100 schrieb Kashyap Chamarthy: > I see.  So I ran `dmesg -w`, as I attached the disk & see the following: UAS and no quirk for your device. It looks like it indeed just does not support TRIM. Sorry Oliver -- To unsubscribe from this

[GIT PULL] USB fixes for 4.16-rc6

The following changes since commit 4a3928c6f8a53fa1aed28ccba227742486e8ddcb: Linux 4.16-rc3 (2018-02-25 18:50:41 -0800) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/ tags/usb-4.16-rc6 for you to fetch changes up to

Re: [PATCH v7 01/12] drivers: base: Unified device connection lookup

On Mon, Mar 12, 2018 at 05:34:20PM +0300, Heikki Krogerus wrote: > Several frameworks - clk, gpio, phy, pmw, etc. - maintain > lookup tables for describing connections and provide custom > API for handling them. This introduces a single generic > lookup table and API for the connections. > > The

Re: [PATCH 2/3] usb: host: pci: introduce PCI vendor ID for Netlogic

On Wed, Mar 14, 2018 at 11:29:32AM +0100, Richard Leitner wrote: > From: Richard Leitner > > Replace the hardcoded PCI vendor ID of Netlogic with a definition in > pci_ids.h Why? It's only being used in one file, so it should not be in pci_ids.h, right? thanks,

Re: [PATCH 3/3] usb: host: pci: replace hardcoded renesas PCI IDs

On Wed, Mar 14, 2018 at 11:29:33AM +0100, Richard Leitner wrote: > From: Richard Leitner > > Introduce Renesas uPD72020{1,2} PCI device IDs in pci_ids.h and replace > the harcoded values with them. > > Signed-off-by: Richard Leitner >

Re: [PATCH 1/3] usb: host: pci: use existing Intel PCI ID macros

On Wed, Mar 14, 2018 at 11:29:31AM +0100, Richard Leitner wrote: > From: Richard Leitner > > Instead of the hardcoded hexadecimal PCI IDs use the existing macros > from pci_ids.h for Intel IDs. You also did something else in this patch, yet failed to mention it

Re: [PATCH v1 2/2] usb: dwc3: Add Qualcomm DWC3 glue driver

Hi Manu, Thank you for the patch! Yet something to improve: [auto build test ERROR on v4.16-rc4] [also build test ERROR on next-20180314] [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/Manu

Re: [RFC PATCH] usb: typec: tcpm: match source fixed pdo with sink variable pdo

Hi, On 14-03-18 10:32, Jun Li wrote: Hi -Original Message- From: Hans de Goede [mailto:hdego...@redhat.com] Sent: 2018年3月13日 19:36 To: Jun Li ; gre...@linuxfoundation.org; li...@roeck-us.net; heikki.kroge...@linux.intel.com; adam.thomson.opensou...@diasemi.com;

Re: [PATCH 0/2] USB 3.2 initial support

Am Dienstag, den 13.03.2018, 19:22 +0200 schrieb Mathias Nyman: > My understanding is that Gen XxY notion is only used for symmetric devices > where tx lanes = rx lanes. Only SSIC devices can be asymmetric. > > USB 3.2 spec mentions the (Gen 1x1, 1x2, 2x1 and 2x2) alternatives, nothing > more.

[PATCH 1/3] usb: host: pci: use existing Intel PCI ID macros

From: Richard Leitner Instead of the hardcoded hexadecimal PCI IDs use the existing macros from pci_ids.h for Intel IDs. Signed-off-by: Richard Leitner --- drivers/usb/host/pci-quirks.c | 10 +- drivers/usb/host/xhci-pci.c |

[PATCH 2/3] usb: host: pci: introduce PCI vendor ID for Netlogic

From: Richard Leitner Replace the hardcoded PCI vendor ID of Netlogic with a definition in pci_ids.h Signed-off-by: Richard Leitner --- drivers/usb/host/pci-quirks.c | 2 +- include/linux/pci_ids.h | 2 ++ 2 files changed, 3

[PATCH 3/3] usb: host: pci: replace hardcoded renesas PCI IDs

From: Richard Leitner Introduce Renesas uPD72020{1,2} PCI device IDs in pci_ids.h and replace the harcoded values with them. Signed-off-by: Richard Leitner --- drivers/usb/host/pci-quirks.c | 6 -- drivers/usb/host/xhci-pci.c | 4

[PATCH 0/3] usb: host: pci: PCI ID consolidation

From: Richard Leitner Centralize some hardcoded PCI IDs as definitions in the global include/linux/pci_ids.h file. This is done to reduce the amount of scattered PCI ID definitions and hardcoded values across the kernel. Richard Leitner (3): usb: host: pci: use

Re: Debugging SCSI 'UNMAP' ("Logical Block Provisioning") failure on an SSD

On Wed, Mar 14, 2018 at 10:52:36AM +0100, Oliver Neukum wrote: > Am Dienstag, den 13.03.2018, 12:50 +0100 schrieb Kashyap Chamarthy: > > Earlier, I didn't know which list to email, so I wrote to Martin K. > > Petersen (who pointed me to the lists when I asked where I can post > > publicly), and he

Re: [PATCH] usb: dwc2: Fix interval type issue

On 2/6/2018 7:07 PM, Grigor Tovmasyan wrote: > The maximum value that unsigned char can hold is 255, meanwhile > the maximum value of interval is 2^(bIntervalMax-1)=2^15. > > Signed-off-by: Grigor Tovmasyan > --- > drivers/usb/dwc2/core.h | 2 +- > 1 file changed, 1

Re: [PATCH v3 04/12] usb: typec: add API to get typec basic port power and data config

Hi, On Tue, Mar 13, 2018 at 05:34:30PM +0800, Li Jun wrote: > +/** > + * typec_get_power_type - Get the typec port power type > + * @fwnode: Firmware node to get the property of > + * > + * This routine is used by typec hardware driver to read property > + * port power type from the device

Re: Debugging SCSI 'UNMAP' ("Logical Block Provisioning") failure on an SSD

Am Dienstag, den 13.03.2018, 12:50 +0100 schrieb Kashyap Chamarthy: > Earlier, I didn't know which list to email, so I wrote to Martin K. > Petersen (who pointed me to the lists when I asked where I can post > publicly), and he made this observation on the above quoted text: > >     "Linux can

Re: 4.14.13: Kernel panic, NULL pointer dereference in xhci_hcd

Am Dienstag, den 13.03.2018, 17:53 +0200 schrieb Juho Tykkälä : > This is originally raised as Debian bug but the more I investigate > it seems to trace back to 4.14.x xhci. Hi, does vanilla 4.14.0 work? Could you bisect? Regards Oliver -- To unsubscribe from this list:

[PATCH v3] usb: core: introduce per-port over-current counters

From: Richard Leitner For some userspace applications information on the number of over-current conditions at specific USB hub ports is relevant. In our case we have a series of USB hardware (using the cp210x driver) which communicates using a proprietary protocol.

RE: [PATCH v3 01/12] dt-bindings: connector: add properties for typec

> -Original Message- > From: linux-usb-ow...@vger.kernel.org > [mailto:linux-usb-ow...@vger.kernel.org] On Behalf Of Heikki Krogerus > Sent: 2018年3月14日 17:40 > To: Jun Li > Cc: robh...@kernel.org; mark.rutl...@arm.com; > gre...@linuxfoundation.org; a.ha...@samsung.com;

Re: [PATCH v3 01/12] dt-bindings: connector: add properties for typec

On Tue, Mar 13, 2018 at 05:34:27PM +0800, Li Jun wrote: > Add bingdings supported by current typec driver, so user can pass > all those properties via dt. > > Signed-off-by: Li Jun > --- > Change for v3: > - port-type change to be power-type which only for power. > - add

RE: [RFC PATCH] usb: typec: tcpm: match source fixed pdo with sink variable pdo

Hi > -Original Message- > From: Hans de Goede [mailto:hdego...@redhat.com] > Sent: 2018年3月13日 19:36 > To: Jun Li ; gre...@linuxfoundation.org; li...@roeck-us.net; > heikki.kroge...@linux.intel.com; adam.thomson.opensou...@diasemi.com; > bad...@google.com > Cc:

Re: [PATCH 0/2] USB 3.2 initial support

On 13.03.2018 21:58, Adrian Bocaniciu wrote: On Tue, 13 Mar 2018 17:27:21 +0200 Mathias Nyman wrote: Example for clarification: Gen 1x1 = 5Gbps, SuperSpeed, one lane, same as USB3.0, and USB 3.1 Gen1 Gen 2x1 = 10Gbps, SuperSpeedPlus, one lane, same as USB 3.1

RE: [PATCH v3 10/12] staging: typec: tcpci: keep the not connecting cc line open

Hi Jun, -Original Message- From: Li Jun [mailto:jun...@nxp.com] Sent: Tuesday, March 13, 2018 5:35 PM To: robh...@kernel.org; mark.rutl...@arm.com; gre...@linuxfoundation.org; heikki.kroge...@linux.intel.com Cc: a.ha...@samsung.com; jun...@nxp.com; li...@roeck-us.net; yue...@google.com;

Re: [PATCH][usb-next] usb: dwc2: ix spelling mistake: "genereted" -> "generated"

Hi, Colin King writes: > From: Colin Ian King > > Trivial fix to spelling mistake in dev_warn warning message text. > > Signed-off-by: Colin Ian King seems like we need a patch to fix your subject ;-) I'll fix it

Re: [PATCH v4 13/15] usb: dwc3: Add workaround for isoc start transfer failure

Hi, Thinh Nguyen writes: >> Thinh Nguyen writes: >>> In DWC_usb31 version 1.70a-ea06 and prior, for highspeed and fullspeed >>> isochronous IN, BIT[15:14] of the 16-bit microframe number reported by >>> the XferNotReady event are invalid.

Re: [PATCH v4 2/2] usb/gadget: Add driver for Aspeed SoC virtual hub

Hi, Benjamin Herrenschmidt writes: > On Tue, 2018-03-13 at 09:35 +1100, Benjamin Herrenschmidt wrote: >> On Fri, 2018-03-09 at 11:20 +0200, Felipe Balbi wrote: >> > >> > > diff --git a/drivers/usb/gadget/udc/aspeed-vhub/core.c >> > >

Re: [PATCH v1 2/2] usb: dwc3: Add Qualcomm DWC3 glue driver

Hi, Manu Gautam writes: > Hi, > > > On 3/13/2018 4:38 PM, Felipe Balbi wrote: >> Hi, >> >> +Andy >> >> Manu Gautam writes: >>> DWC3 controller on Qualcomm SOCs has a Qscratch wrapper. >>> Some of its uses are described below resulting in need to

Re: [PATCH] usb: misc: supports Apple Carplay driver

On Wed, 2018-03-14 at 07:16 +0100, Greg Kroah-Hartman wrote: > On Wed, Mar 14, 2018 at 02:02:36PM +0800, Chunfeng Yun wrote: > > The driver is used to support Apple carplay feature by a debugfs > > interface which can force the driver to send a USB Vendor Request > > of "Apple Device to Host Mode

Re: [PATCH] Add Apple Carplay driver

On Tue, 2018-03-13 at 23:53 -0700, Matthew Dharm wrote: > Why is this a kernel-level driver, rather than a userspace application > that uses libusb to send the single vendor-specific command required? > Since this command would be applicable to many CarPlay devices, with > many different VID/PIDs,

Re: [PATCH] usb: misc: supports Apple Carplay driver

On Wed, Mar 14, 2018 at 02:02:36PM +0800, Chunfeng Yun wrote: > The driver is used to support Apple carplay feature by a debugfs > interface which can force the driver to send a USB Vendor Request > of "Apple Device to Host Mode Switch" to switch Apple Device > into host mode. While I am all for

Re: [PATCH] Add Apple Carplay driver

Why is this a kernel-level driver, rather than a userspace application that uses libusb to send the single vendor-specific command required? Since this command would be applicable to many CarPlay devices, with many different VID/PIDs, it would seem to make more sense as a userspace app that took a

Re: [PATCH v2 3/3] dt-bindings: phy-mtk-tphy: add properties for U2 slew rate calibrate

On Wed, 2018-03-14 at 00:21 +0100, Matthias Brugger wrote: > > On 03/12/2018 06:25 AM, Chunfeng Yun wrote: > > Add two properties of ref_clk and coefficient used by U2 slew rate > > calibrate which may vary on different SoCs > > > > Signed-off-by: Chunfeng Yun > >

Re: [PATCH v2 2/3] phy: phy-mtk-tphy: add configurable parameters for slew rate calibrate

On Wed, 2018-03-14 at 00:21 +0100, Matthias Brugger wrote: > > On 03/12/2018 06:25 AM, Chunfeng Yun wrote: > > There are two parameters, ref_clk and coefficient, for U2 slew rate > > calibrate which may vary on different SoCs, here allow them to be > > configurable > > > > Signed-off-by:

[PATCH] Add Apple Carplay driver

>From bf48dcd9cb254576cfea373c9a5d2ab996408895 Mon Sep 17 00:00:00 2001 From: Chunfeng Yun Date: Tue, 13 Mar 2018 11:47:38 +0800 Subject: [PATCH] Add Apple Carplay driver Some Apple devices which support Carplay can enter USB Host Mode from USB Device Mode after

[PATCH] usb: misc: supports Apple Carplay driver

The driver is used to support Apple carplay feature by a debugfs interface which can force the driver to send a USB Vendor Request of "Apple Device to Host Mode Switch" to switch Apple Device into host mode. Signed-off-by: Chunfeng Yun --- drivers/usb/misc/Kconfig |