Re: [PATCH 4/4] usb: musb: tusb6010_omap: Convert to DMAengine API

* Peter Ujfalusi [170505 08:20]: > On 2017-05-05 16:37, Peter Ujfalusi wrote: > > On 2017-05-05 00:05, Tony Lindgren wrote: > > > And this sync gpmc issue seems to be timing related. Setting > > > DEBUG in tusb6010_omap.c makes it happen easily while without > > > it it's

Re: [PATCH v3 0/2] usb: Check for DMA capable buffer sanity

On 04/25/2017 05:56 PM, Florian Fainelli wrote: > Changes in v3: > > - added check in usb_gadget_map_request_by_dev (Felipe), new patch > - improved commit message description (Clemens) > - added additiona checks for urb->setup_packet (Alan) > > Changes in v2: > > - moved the check from

Re: [PATCH v3] USB: serial: ftdi_sio: fix setting latency for unprivileged users

On Fri, May 05, 2017 at 05:30:16PM +0200, Anthony Mallet wrote: > Commit 557aaa7ffab6 ("ft232: support the ASYNC_LOW_LATENCY > flag") enables unprivileged users to set the FTDI latency timer, > but there was a logic flaw that skipped sending the corresponding > USB control message to the device. >

[PATCH v3] USB: serial: ftdi_sio: fix setting latency for unprivileged users

Commit 557aaa7ffab6 ("ft232: support the ASYNC_LOW_LATENCY flag") enables unprivileged users to set the FTDI latency timer, but there was a logic flaw that skipped sending the corresponding USB control message to the device. Signed-off-by: Anthony Mallet ---

Re: [PATCH 4/4] usb: musb: tusb6010_omap: Convert to DMAengine API

On 2017-05-05 16:37, Peter Ujfalusi wrote: Tony, On 2017-05-05 00:05, Tony Lindgren wrote: * Tony Lindgren [170504 12:43]: Hi, * Peter Ujfalusi [170503 04:00]: With the port_window support in DMAengine and the sDMA driver we can convert the

Re: Chipidea USB controller hangs in peripheral mode under high memory bus pressure

Am 05.05.2017 um 14:56 schrieb Thomas Entner / EE: Hi, I am Thomas who contacted Laurent regarding this issue. We have some further observations: Am 04.05.2017 um 08:45 schrieb Peter Chen: On Wed, May 03, 2017 at 01:32:28PM +0300, Laurent Pinchart wrote: There was no one reported this problem

Re: [PATCH v2] USB: serial: ftdi_sio: fix setting latency for unprivileged users

On Wed, May 03, 2017 at 09:23:59PM +0200, Anthony Mallet wrote: > Commit 557aaa7ffab6 ("ft232: support the ASYNC_LOW_LATENCY > flag") enables unprivileged users to set the FTDI latency timer, > but there was a logic flaw that skipped sending the corresponding > USB control message to the device. >

Re: [PATCH 4/4] usb: musb: tusb6010_omap: Convert to DMAengine API

Tony, On 2017-05-05 00:05, Tony Lindgren wrote: * Tony Lindgren [170504 12:43]: Hi, * Peter Ujfalusi [170503 04:00]: With the port_window support in DMAengine and the sDMA driver we can convert the driver to DMAengine. Actually looks like this

Re: Chipidea USB controller hangs in peripheral mode under high memory bus pressure

Hi, I am Thomas who contacted Laurent regarding this issue. We have some further observations: Am 04.05.2017 um 08:45 schrieb Peter Chen: On Wed, May 03, 2017 at 01:32:28PM +0300, Laurent Pinchart wrote: There was no one reported this problem before, but from the description, it seems an IC

[PATCH v2] usb: musb: musb_cppi41: Update an error message

If dma_request_slave_channel() failed to return a channel, then the driver will print an error and request to defer probe, regardless of the cause of the failure. Only defer if the DMA is not ready yet and print an error to explain that we are deferring probe. Signed-off-by: Alexandre Bailon

Re: [PATCH v8 1/5] x86: add simple udelay calibration

On 05/05/2017 01:41 AM, Lu Baolu wrote: > Hi, > > On 05/03/2017 06:38 AM, Boris Ostrovsky wrote: >> On 03/21/2017 04:01 AM, Lu Baolu wrote: >>> Add a simple udelay calibration in x86 architecture-specific >>> boot-time initializations. This will get a workable estimate >>> for loops_per_jiffy.

[PATCH] xhci: remove GFP_DMA flag from allocation

There is no reason to restrict allocations to the first 16MB ISA DMA addresses. Signed-off-by: Matthias Lange --- drivers/usb/host/xhci-mem.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/usb/host/xhci-mem.c

Re: GFP_DMA flag in xhci_segment_alloc

Hi, On 05/05/2017 10:39 AM, Mathias Nyman wrote: > Hi > > On 04.05.2017 22:13, Matthias Lange wrote: >> Hi, >> >> I am wondering what the reason for the GFP_DMA flag in >> xhci_segment_alloc() (drivers/usb/host/xhci-mem.c:59) is. >> >> It is causing me problems in a virtualization setup with

Re: [PATCH v1] ACPI: Switch to use generic UUID API

On Fri, May 5, 2017 at 12:57 PM, Christoph Hellwig wrote: > On Fri, May 05, 2017 at 12:50:31PM +0300, Amir Goldstein wrote: >> To complete the picture for folks not cc'ed on my patches, >> xfs use case suggests there is also justification for the additional helpers: >> >>

Re: [PATCH v1] ACPI: Switch to use generic UUID API

On Fri, May 05, 2017 at 12:50:31PM +0300, Amir Goldstein wrote: > To complete the picture for folks not cc'ed on my patches, > xfs use case suggests there is also justification for the additional helpers: > > uuid_is_null() / uuid_equal() > guid_is_null() / guid_equal() The is_null is useful and

max3421-hcd low performance

Hi. I'm using max3421-hcd on max3421evkit-1+ connected to SPI of Wandboard (i.MX6Quad) and running kernel 4.11-rc6 (from trunk of linux-stable). The SPI is running at 25MHz (the maximum for max3421e chip). The performance I'm observing is very low. Transfer speed to/from a USB flash stick is

Re: [PATCH v1] ACPI: Switch to use generic UUID API

On Fri, May 5, 2017 at 12:24 PM, Andy Shevchenko wrote: > On Fri, 2017-05-05 at 10:06 +0300, Amir Goldstein wrote: [...] >> I think with this semantic change, our proposals can reach common >> grounds >> and satisfy a wider group of users (i.e. filesystem

Re: [PATCH v1] ACPI: Switch to use generic UUID API

On Fri, 2017-05-05 at 10:06 +0300, Amir Goldstein wrote: > On Fri, May 5, 2017 at 9:20 AM, Dan Williams > wrote: > > On Thu, May 4, 2017 at 2:21 AM, Andy Shevchenko > > wrote: > > > for (i = 0; i < NFIT_UUID_MAX; i++) > > >

Re: GFP_DMA flag in xhci_segment_alloc

Hi On 04.05.2017 22:13, Matthias Lange wrote: Hi, I am wondering what the reason for the GFP_DMA flag in xhci_segment_alloc() (drivers/usb/host/xhci-mem.c:59) is. It is causing me problems in a virtualization setup with enabled IOMMU (x86_64). The result is that USB is not working in the VM.

Re: [PATCH] usb: misc: legousbtower: Fix memory leak

Hi, On Thu, May 04, 2017 at 10:51:52PM +0300, Maksim Salau wrote: > get_version_reply is not freed if function returns with success. > Memory leak was introduced by commit 942a48730faf149ccbf3e12ac718aee120bb3529 Pointing the commit like that is probable fine, but you should also use "Fixes"

Re: [PATCH v1] ACPI: Switch to use generic UUID API

On Fri, May 05, 2017 at 10:06:06AM +0300, Amir Goldstein wrote: > I much rather that you sort out uuid helpers in a way that will > satisfy the filesystem > needs (just provide the helpers don't need to convert filesystems code). Yeah. > IMO, you should acknowledge that the common use case for

Re: [PATCH 0/4] usb: musb: tusb6010_omap: Convert to DMAengine

On 2017-05-04 17:31, Tony Lindgren wrote: * Peter Ujfalusi [170503 04:00]: Hi, With port_window support implemented in DMAengine and the sDMA DMAengine driver, the tusb6010_omap driver can be converted away from the custom legacy omap-dma API to generic DMAengine.

Re: [PATCH v1] ACPI: Switch to use generic UUID API

On Fri, May 5, 2017 at 9:20 AM, Dan Williams wrote: > On Thu, May 4, 2017 at 2:21 AM, Andy Shevchenko > wrote: >> acpi_evaluate_dsm() and friends take a pointer to a raw buffer of 16 >> bytes. Instead we convert them to use uuid_le

Re: [PATCH v1] ACPI: Switch to use generic UUID API

On Thu, May 4, 2017 at 2:21 AM, Andy Shevchenko wrote: > acpi_evaluate_dsm() and friends take a pointer to a raw buffer of 16 > bytes. Instead we convert them to use uuid_le type. At the same time we > convert current users. > > acpi_str_to_uuid() becomes

[PATCH v3 1/3] usb: phy: Introduce one extcon device into usb phy

Usually usb phy need register one extcon device to get the connection notifications. It will remove some duplicate code if the extcon device is registered using common code instead of each phy driver having its own related extcon APIs. So we add one pointer of extcon device into usb phy structure,

[PATCH v3 3/3] usb: phy: phy-msm-usb: Remove redundant extcon register/unregister

Since usb phy core has added common code to register or unregister extcon device, then phy-msm-usb driver does not need its own code to register/unregister extcon device, then remove them. Signed-off-by: Baolin Wang --- drivers/usb/phy/phy-msm-usb.c | 85

[PATCH v3 2/3] usb: phy: phy-qcom-8x16-usb: Remove redundant extcon register/unregister

Since usb phy core has added common code to register or unregister extcon device, then phy-qcom-8x16-usb driver does not need its own code to register/unregister extcon device, then remove them. Signed-off-by: Baolin Wang --- drivers/usb/phy/phy-qcom-8x16-usb.c | 20

[PATCH v3 0/3] Introduce one extcon device into usb phy

This patchset introduces one pointer of extcon device into usb phy structure, and some other helper functions to register extcon instead of each phy driver having its own related extcon APIs. Changes since v2: - Support separate extcon device. - Convert the phy-msm-usb driver. Changes since

Re: [Intel-gfx] [PATCH v1] ACPI: Switch to use generic UUID API

-Shevchenko/ACPI-Switch-to-use-generic-UUID-API/20170505-134225 config: i386-tinyconfig (attached as .config) compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901 reproduce: # save the attached .config to linux build tree make ARCH=i386 All errors (new ones prefixed by >>): I