Re: [PATCH v3 05/12] usb: typec: add API to get sink and source config

Hi, On 2018-03-13 10:34, Li Jun wrote: This patch add 2 APIs to get sink and source power config from firmware description in case the port supports PD. Signed-off-by: Li Jun --- drivers/usb/typec/tcpm.c | 47 +++

[PATCH] usb: chipidea: move extcon initial state read

Any extcon events between the initial state read and ci_extcon_register are "lost". This patch doesn't fix the issue entirely but reduces the chance of the controller entering a bad state. Signed-off-by: Jonathan Marek --- drivers/usb/chipidea/core.c | 35

Re: [PATCH] usb: chipidea: move extcon initial state read

On Thu, Mar 15, 2018 at 11:41:23AM -0400, Jonathan wrote: > Any extcon events between the initial state read and ci_extcon_register are > "lost". This patch doesn't fix the issue entirely but reduces the chance of > the controller entering a bad state. > > Signed-off-by: Jonathan Marek

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

On Thu, Mar 15, 2018 at 04:46:30PM +0100, Kashyap Chamarthy wrote: > (Sorry, accidentally dropped the lists. Adding it back & re-posting my > off-list response.) (Now add the missing linux-usb@vger.kernel.org list for real. Not trimming the full e-mail intentionally as I missed to Cc

Re: rfc: remove print_vma_addr ? (was Re: [PATCH 00/16] remove eight obsolete architectures)

On Thu, Mar 15, 2018 at 09:56:46AM -0700, Joe Perches wrote: > I have a patchset that creates a vsprintf extension for > print_vma_addr and removes all the uses similar to the > print_symbol() removal. > > This now avoids any possible printk interleaving. > > Unfortunately, without some #ifdef

Re: rfc: remove print_vma_addr ? (was Re: [PATCH 00/16] remove eight obsolete architectures)

On Thu, 2018-03-15 at 10:08 -0700, Matthew Wilcox wrote: > On Thu, Mar 15, 2018 at 09:56:46AM -0700, Joe Perches wrote: > > I have a patchset that creates a vsprintf extension for > > print_vma_addr and removes all the uses similar to the > > print_symbol() removal. > > > > This now avoids any

Bluetooth controller falling off USB bus after an hour of continuous BT headset usage

Dear linux-usb list, I'm having a recurring issue with my on-board Bluetooth controller falling off USB bus after about an hour of continuous usage: [91080.440903] usb 2-6: USB disconnect, device number 24 [91080.450545] Bluetooth: hci0: setting interface failed (19) [91080.685270] usb 2-6: new

rfc: remove print_vma_addr ? (was Re: [PATCH 00/16] remove eight obsolete architectures)

On Thu, 2018-03-15 at 10:48 +0100, Geert Uytterhoeven wrote: > Hi David, > > On Thu, Mar 15, 2018 at 10:42 AM, David Howells wrote: > > Do we have anything left that still implements NOMMU? > > Sure: arm, c6x, m68k, microblaze, and sh. I have a patchset that creates a

Re: [PATCH v5 1/6] dt-bindings: add bindings for USB physical connector

On 15/03/18 13:46, Robin Murphy wrote: > On 12/03/18 10:41, Roger Quadros wrote: > [...] > @@ -0,0 +1,75 @@ > +USB Connector > += > + > +USB connector node represents physical USB connector. It should be > +a child of USB interface controller. > + >

Re: [PATCH v3 02/12] dt-bindings: usb: add documentation for typec port controller(TCPCI)

Hi, On 2018-03-13 10:34, Li Jun wrote: TCPCI stands for typec port controller interface, its implementation has full typec port control with power delivery support, it's a standard i2c slave with GPIO input as irq interface, detail see spec "Universal Serial Bus Type-C Port Controller

Re: [PATCH] net: drivers/net: Remove unnecessary skb_copy_expand OOM messages

From: Joe Perches Date: Mon, 12 Mar 2018 08:07:12 -0700 > skb_copy_expand without __GFP_NOWARN already does a dump_stack > on OOM so these messages are redundant. > > Signed-off-by: Joe Perches Ok, applied to net-next, thanks. -- To unsubscribe from this

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

On Thu, 2018-03-15 at 08:03 +1100, Benjamin Herrenschmidt wrote: > > > Do you have more comments for the rest of the driver or that's it ? > > > > so far, that's it. > > Ok. I'll re-send. So I'll resend in a minute, doing a few more tests, however, I've noticed something which I wont' have time

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

The Aspeed BMC SoCs support a "virtual hub" function. It provides some HW support for a top-level USB2 hub behind which sit 5 gadget "ports". This driver adds support for the full functionality, emulating the hub standard requests and exposing 5 UDC gadget drivers corresponding to the ports. The

Re: [PATCH 1/2] usb: dwc3: use local copy of resource to fix-up register offset

On Thu, 15 Mar 2018 20:39:57 +0900 Masahiro Yamada wrote: > It is not a good idea to modify the resource from the platform device. > Modify its local copy to pass it to devm_ioremap_resource() so that we > do not need to restore it in the failure path and the

Re: [PATCH 2/2] usb: dwc3: add clock and resets

On Thu, 15 Mar 2018 20:39:58 +0900 Masahiro Yamada wrote: > dwc3-of-simple.c only handles arbitrary number of clocks and resets. > They are both generic enough to be put into the dwc3 core. For simple > cases, a nested node structure like follows: > > dwc3-glue

Re: [PATCH 00/16] remove eight obsolete architectures

Hi, On Thu, Mar 15, 2018 at 10:56:48AM +0100, Arnd Bergmann wrote: > On Thu, Mar 15, 2018 at 10:42 AM, David Howells wrote: > > Do we have anything left that still implements NOMMU? Please don't kill !MMU. > Yes, plenty. > I've made an overview of the remaining

RE: [PATCH] usb: chipidea: move extcon initial state read

> > Any extcon events between the initial state read and ci_extcon_register are > "lost". > This patch doesn't fix the issue entirely but reduces the chance of the > controller > entering a bad state. It seems you have already known the rare cases the lost for extcon exents, why not fix it

[PATCH v5 1/2] usb/gadget: Add an EP dispose() callback for EP lifetime tracking

Some UDC may want to allocate endpoints dynamically, either because the HW supports an arbitrary large number or because (like the Aspeed BMC SoCs), the pool of HW endpoints is shared between multiple gadgets. The allocation side can be done rather easily using the existing match_ep() UDC hook.

About patchwork for linux-usb

Hi Greg, At some situations, we may need to save reviewing patches from web, but I can't find linux-usb at https://patchwork.kernel.org/, any there any patchworks for linux-usb mailist at Internet? Thanks. Peter -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in

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

On 15.03.2018 15:28, Chris Chiu wrote: On Thu, Mar 15, 2018 at 7:46 PM, Mathias Nyman wrote: On 15.03.2018 06:40, Chris Chiu wrote: 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.

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

Am Donnerstag, den 15.03.2018, 09:33 +0200 schrieb Mathias Nyman: > On 14.03.2018 12:29, Oliver Neukum wrote: > > > > We should also export all raw data we have. User space can be trusted > > to get a multiplication right and it is not the kernels job > > to interpret such data. > > Do I

Re: [PATCH 00/16] remove eight obsolete architectures

On Thu, Mar 15, 2018 at 10:42 AM, David Howells wrote: > Do we have anything left that still implements NOMMU? Yes, plenty. I was wondering the same thing, but it seems that the architectures we remove are almost completely representative of what we support overall, except

Re: [PATCH 00/16] remove eight obsolete architectures

On 03/15/2018 10:42 AM, David Howells wrote: > Do we have anything left that still implements NOMMU? > RISC-V ? (evil grin :-) Cheers, Hannes -- Dr. Hannes ReineckeTeamlead Storage & Networking h...@suse.de +49 911 74053 688 SUSE LINUX GmbH,

Re: [PATCH 00/16] remove eight obsolete architectures

Do we have anything left that still implements NOMMU? David -- 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 00/16] remove eight obsolete architectures

Hi David, On Thu, Mar 15, 2018 at 10:42 AM, David Howells wrote: > Do we have anything left that still implements NOMMU? Sure: arm, c6x, m68k, microblaze, and sh. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32

Re: DWC2 maintainership change

On Thu, Mar 15, 2018 at 04:00:25AM +, John Youn wrote: > 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 >

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

On Wed, Mar 14, 2018 at 11:43:55PM -0400, Martin K. Petersen wrote: > > Kashyap, Hi Martin, > > 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

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

On 03/15/2018 10:26 AM, Oliver Neukum wrote: > Am Mittwoch, den 14.03.2018, 16:44 +0100 schrieb Richard Leitner: >> On 03/14/2018 04:27 PM, Oliver Neukum wrote: >>> Am Mittwoch, den 14.03.2018, 14:31 +0100 schrieb Richard Leitner: >>> Well, but it does not. Removing a redundant definition is

Re: DWC2 maintainership change

Hi, "Greg Kroah-Hartman (gre...@linuxfoundation.org)" writes: > On Thu, Mar 15, 2018 at 04:00:25AM +, John Youn wrote: >> Hi Felipe, Greg, >> >> I won't be able to continue maintainership of dwc2. >> >> Minas Harutyunyan, has been doing most of the

Re: [PATCH 00/16] remove eight obsolete architectures

On Thu, Mar 15, 2018 at 10:59 AM, Hannes Reinecke wrote: > On 03/15/2018 10:42 AM, David Howells wrote: >> Do we have anything left that still implements NOMMU? >> > RISC-V ? > (evil grin :-) Is anyone producing a chip that includes enough of the Privileged ISA spec to have things

Re: [PATCH v5 1/6] dt-bindings: add bindings for USB physical connector

On 12.03.2018 11:41, Roger Quadros wrote: > Andrezej, > > Why don't you have any of the USB maintainers in to/cc? > > Greg Kroah-Hartman (supporter:USB SUBSYSTEM) > Felipe Balbi (maintainer:USB GADGET/PERIPHERAL SUBSYSTEM) Serious omission, sorry

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

> -Original Message- > From: shufan_lee(李��帆) [mailto:shufan_...@richtek.com] > Sent: 2018年3月14日 16:59 > To: Jun Li ; robh...@kernel.org; mark.rutl...@arm.com; > gre...@linuxfoundation.org; heikki.kroge...@linux.intel.com > Cc: a.ha...@samsung.com; li...@roeck-us.net;

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

On Thu, Mar 15, 2018 at 12:19:11PM +0100, Douglas Gilbert wrote: > On 2018-03-15 10:47 AM, Kashyap Chamarthy wrote: > > On Wed, Mar 14, 2018 at 11:43:55PM -0400, Martin K. Petersen wrote: > > > > > > Kashyap, > > > > Hi Martin, > > > > > > Sorry, I didn't give you complete information — with

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

Kashyap, > /me naively wonders if it has anything to do with accessing it via > Linux. I'm guessing that the drive doesn't actually support SCSI UNMAP. I have a T3 that reports all the right things in the bl/lbpv VPD pages but also has lbpme set to 0. Interestingly enough, my T3 does appear to

Re: Webcams not recognized on a Dell Latitude 5285 laptop

Hi Andy and Frédéric, On Tue, Mar 13, 2018 at 06:11:00PM +0200, Andy Shevchenko wrote: > On Sun, Mar 11, 2018 at 2:38 PM, FRÉDÉRIC PARRENIN > wrote: > > Dear Oliver and all, > > > > So I was expecting linux-4.16 to recognize my webcams, thanks to this

Re: [PATCH v5 1/6] dt-bindings: add bindings for USB physical connector

On 12/03/18 10:41, Roger Quadros wrote: [...] @@ -0,0 +1,75 @@ +USB Connector += + +USB connector node represents physical USB connector. It should be +a child of USB interface controller. + +Required properties: +- compatible: describes type of the connector, must be one of: +

Re: [PATCH v3 05/12] usb: typec: add API to get sink and source config

Hi, A small nitpick. The subject lines seem to be a little bit inconsistent in this series. This patch for example does not mention tcpm at all in its subject or even commit message, even though it only modifies tcpm.c. Please change the subject lines of all the patches in this series mainly

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

Arnd Bergmann writes: > 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 [...] > drivers/net/wireless/cisco/Kconfig

Re: [PATCH v3 05/12] usb: typec: add API to get sink and source config

On Tue, Mar 13, 2018 at 05:34:31PM +0800, Li Jun wrote: > This patch add 2 APIs to get sink and source power config from firmware > description in case the port supports PD. > > Signed-off-by: Li Jun > --- > drivers/usb/typec/tcpm.c | 47

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

On 2018-03-15 10:47 AM, Kashyap Chamarthy wrote: On Wed, Mar 14, 2018 at 11:43:55PM -0400, Martin K. Petersen wrote: Kashyap, Hi Martin, 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".

[PATCH 1/2] usb: dwc3: use local copy of resource to fix-up register offset

It is not a good idea to modify the resource from the platform device. Modify its local copy to pass it to devm_ioremap_resource() so that we do not need to restore it in the failure path and the remove hook. Signed-off-by: Masahiro Yamada ---

[PATCH 2/2] usb: dwc3: add clock and resets

dwc3-of-simple.c only handles arbitrary number of clocks and resets. They are both generic enough to be put into the dwc3 core. For simple cases, a nested node structure like follows: dwc3-glue { compatible = "foo,dwc3"; clocks = ...; resets = ...; ...

Re: [PATCH v3 06/12] staging: typec: tcpci: support port config passed via dt

On Tue, Mar 13, 2018 at 05:34:32PM +0800, Li Jun wrote: > User can define the typec port properties in tcpci node to setup > the port config. > > Signed-off-by: Li Jun > --- > drivers/staging/typec/tcpci.c | 63 > +++ > 1 file changed, 63

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

On 15.03.2018 06:40, Chris Chiu wrote: 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

Re: WARN_ON(irqs_disabled()) in dma_free_attrs?

On Wed, Mar 14, 2018 at 05:43:46PM +, Robin Murphy wrote: >> Looking back I don't really understand why we even indirect the "classic" >> per-device dma_declare_coherent_memory use case through the DMA API. > > It certainly makes sense for devices which can exist in both shared-memory > and

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

Hi, On 3/14/2018 2:20 PM, Felipe Balbi wrote: > Hi, > > Manu Gautam writes: > [snip] - 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

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

Am Mittwoch, den 14.03.2018, 16:44 +0100 schrieb Richard Leitner: > On 03/14/2018 04:27 PM, Oliver Neukum wrote: > > Am Mittwoch, den 14.03.2018, 14:31 +0100 schrieb Richard Leitner: > > > > > Well, but it does not. Removing a redundant definition is a clear > > benefit. But you are not removing

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

Hi Jun, -Original Message- From: Jun Li [mailto:jun...@nxp.com] Sent: Thursday, March 15, 2018 3:00 PM To: shufan_lee(李��帆); robh...@kernel.org; mark.rutl...@arm.com; gre...@linuxfoundation.org; heikki.kroge...@linux.intel.com Cc: a.ha...@samsung.com; li...@roeck-us.net;

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

On 14.03.2018 12:29, Oliver Neukum wrote: 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

RE: [PATCH] lan78xx: Connect phy early

Hi Alexander, Thanks for the patch. > @@ -2575,13 +2571,7 @@ static int lan78xx_stop(struct net_device *net) > if (timer_pending(>stat_monitor)) > del_timer_sync(>stat_monitor); > > - phy_unregister_fixup_for_uid(PHY_KSZ9031RNX, 0xfff0); > -

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

On Wed, Mar 14, 2018 at 6:12 PM, Bin Liu wrote: > On Wed, Mar 14, 2018 at 04:35:51PM +0100, Arnd Bergmann wrote: >> diff --git a/drivers/usb/musb/Kconfig b/drivers/usb/musb/Kconfig >> index 5506a9c03c1f..490990e8b015 100644 >> --- a/drivers/usb/musb/Kconfig >> +++

Re: [PATCH 00/16] remove eight obsolete architectures

On Thu, Mar 15, 2018 at 11:42:25AM +0100, Arnd Bergmann wrote: > Is anyone producing a chip that includes enough of the Privileged ISA spec > to have things like system calls, but not the MMU parts? Various SiFive SOCs seem to support M and U mode, but no S mode or iommu. That should be enough

Re: WARN_ON(irqs_disabled()) in dma_free_attrs?

On 15/03/18 07:58, Christoph Hellwig wrote: On Wed, Mar 14, 2018 at 05:43:46PM +, Robin Murphy wrote: Looking back I don't really understand why we even indirect the "classic" per-device dma_declare_coherent_memory use case through the DMA API. It certainly makes sense for devices which

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

On Thu, Mar 15, 2018 at 7:46 PM, Mathias Nyman wrote: > On 15.03.2018 06:40, Chris Chiu wrote: >> >> 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

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

On 2018-03-15 01:45 PM, Martin K. Petersen wrote: Kashyap, /me naively wonders if it has anything to do with accessing it via Linux. I'm guessing that the drive doesn't actually support SCSI UNMAP. I have a T3 that reports all the right things in the bl/lbpv VPD pages but also has lbpme set

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

On Thu, Mar 15, 2018 at 08:45:05AM -0400, Martin K. Petersen wrote: > > Kashyap, > > > /me naively wonders if it has anything to do with accessing it via > > Linux. > > I'm guessing that the drive doesn't actually support SCSI UNMAP. I have > a T3 that reports all the right things in the