Re: [PATCH] usb: dwc3: core: Disable USB2.0 phy suspend when dwc3 acts as host role

Hi, Baolin Wang writes: >> Baolin Wang writes: >>> When dwc3 controller acts as host role with attaching slow speed device >>> (like mouse or keypad). Then if we plugged out the slow speed device, >>> it will timeout to run the deconfiguration

Re: [v4.4.40] patch backport error

On Wed, Jan 11, 2017 at 09:17:02PM +0100, Greg Kroah-Hartman wrote: > On Wed, Jan 11, 2017 at 07:13:30PM +0200, Felipe Balbi wrote: > > > > hi, > > > > Bin Liu writes: > > > I am unable to figure out what was happening, but there seems to be a > > > patch backport error in

Re: [PATCH] usb: dwc3-exynos Fix dma_mask WARN_ON from xhci_plat_probe()

Hi, Shuah Khan writes: > During dwc3_exynos_probe(), WARN_ON(!pdev->dev.dma_mask) is triggered from > xhci_plat_probe(). dwc3_host_init() doesn't configure DMA prior to adding > the platform device. > > dwc3_host_init() was changed to not configure DMA with the change

Re: [PATCH 0/4 v3] Fixes and workarounds for dwc2 on HiKey board (rebased to synopsys-usb/next)

On 1/11/2017 4:22 PM, John Stultz wrote: > Just wanted to resend my patches for dwc2 controller on the > HiKey board for consideration for the 4.11 merge window. > > This patchset is the same as v2, only rebased against > John's synopsys-usb/next branch. > > This does still exclude my

[PATCH] usb: dwc3-exynos Fix dma_mask WARN_ON from xhci_plat_probe()

During dwc3_exynos_probe(), WARN_ON(!pdev->dev.dma_mask) is triggered from xhci_plat_probe(). dwc3_host_init() doesn't configure DMA prior to adding the platform device. dwc3_host_init() was changed to not configure DMA with the change to use bus->sysdev for DMA config. sysdev_is_parent is not

[PATCH 1/4 v3] usb: dwc2: Avoid sleeping while holding hsotg->lock

Basically when plugging in various cables in different orders, I'm occasionally seeing the following BUG splat: [ 86.215403] BUG: scheduling while atomic: kworker/u16:2/53/0x0002 [ 86.219164] usb 1-1: USB disconnect, device number 9 [ 86.226845] Preemption disabled at:[ 86.230218] []

[PATCH 0/4 v3] Fixes and workarounds for dwc2 on HiKey board (rebased to synopsys-usb/next)

Just wanted to resend my patches for dwc2 controller on the HiKey board for consideration for the 4.11 merge window. This patchset is the same as v2, only rebased against John's synopsys-usb/next branch. This does still exclude my patchset[1] to add extcon support to dwc2, which John Youn

[PATCH 2/4 v3] usb: dwc2: Workaround case where GOTGCTL state is wrong

When removing a USB-A to USB-otg adapter cable, we get a change status irq, and then in dwc2_conn_id_status_change, we erroniously see the GOTGCTL_CONID_B flag set. This causes us to get stuck in the "while (!dwc2_is_device_mode(hsotg))" loop, spitting out "Waiting for Peripheral Mode, Mode=Host"

[PATCH 4/4 v3] usb: dwc2: Add a quirk to allow speed negotiation for Hisilicon Hi6220

From: Chen Yu The Hi6220's usb controller is limited in that it does not support "Split Transactions", so it does not support communicating with low-speed and full-speed devices behind a high-speed hub. Thus it requires a quirk so that we can manually drop the usb speed

[PATCH 3/4 v3] usb: dwc2: Force port resume on switching to device mode

From: Chen Yu We've seen failures when switching between host and gadget mode, which was diagnosed as being caused due to the bus being auto-suspended when we switched. So this patch forces a port resume when switching to device mode if the bus is suspended. Cc: Wei Xu

Re: [PATCH 0/5 v2] Fixes and workarounds for dwc2 on HiKey board

On 1/11/2017 3:10 PM, John Stultz wrote: > On Wed, Jan 11, 2017 at 2:58 PM, John Youn wrote: >> On 1/11/2017 2:39 PM, John Stultz wrote: >>> On Wed, Jan 11, 2017 at 2:08 PM, John Youn wrote: On 1/3/2017 11:52 AM, John Stultz wrote: > Hope

Re: [PATCH 0/5 v2] Fixes and workarounds for dwc2 on HiKey board

On Wed, Jan 11, 2017 at 2:58 PM, John Youn wrote: > On 1/11/2017 2:39 PM, John Stultz wrote: >> On Wed, Jan 11, 2017 at 2:08 PM, John Youn wrote: >>> On 1/3/2017 11:52 AM, John Stultz wrote: Hope everyone had a happy new years! I

Re: [PATCH 0/5 v2] Fixes and workarounds for dwc2 on HiKey board

On 1/11/2017 2:39 PM, John Stultz wrote: > On Wed, Jan 11, 2017 at 2:08 PM, John Youn wrote: >> On 1/3/2017 11:52 AM, John Stultz wrote: >>> Hope everyone had a happy new years! >>> >>> I just wanted to send out my current queue of patches for dwc2 >>> controller on the

Re: [PATCH 0/5 v2] Fixes and workarounds for dwc2 on HiKey board

On Wed, Jan 11, 2017 at 2:08 PM, John Youn wrote: > On 1/3/2017 11:52 AM, John Stultz wrote: >> Hope everyone had a happy new years! >> >> I just wanted to send out my current queue of patches for dwc2 >> controller on the HiKey board for consideration for the 4.11 >>

Re: [PATCH 0/5 v2] Fixes and workarounds for dwc2 on HiKey board

On 1/3/2017 11:52 AM, John Stultz wrote: > Hope everyone had a happy new years! > > I just wanted to send out my current queue of patches for dwc2 > controller on the HiKey board for consideration for the 4.11 > merge window. > > This does exclude my patchset[1] to add extcon support to dwc2, >

[PATCH v2 0/2] usb: gadget: s3c2410: add device tree support

This series adds support for configuring Samsung's s3c2410 and compatible USB device controller via device tree. Tested on FriendlyARM mini2440, based on s3c2440 SoC. Changes since v1: - change the USB bus clock name to "uclk" to better reflect the name used in the datasheet - improve

[PATCH v2 1/2] dt-bindings: usb: add DT binding for s3c2410 USB device controller

Adds the device tree bindings description for Samsung S3C2410 and compatible USB device controller. Signed-off-by: Sergio Prado --- .../devicetree/bindings/usb/s3c2410-usb.txt| 28 ++ 1 file changed, 28 insertions(+) diff --git

[PATCH v2 2/2] usb: gadget: s3c2410: allow probing from device tree

Allows configuring Samsung's s3c2410 and compatible USB device controller using a devicetree. Signed-off-by: Sergio Prado --- drivers/usb/gadget/udc/s3c2410_udc.c | 144 +-- drivers/usb/gadget/udc/s3c2410_udc.h | 4 + 2 files

Re: [PATCH v5 0/6] inherit dma configuration from parent dev

[adding Arnd Bergmann who wrote the patches and I noticed was not cc'ed] Hello, On Tue, Jan 10, 2017 at 9:11 AM, Roger Quadros wrote: > On 05/01/17 19:16, Greg KH wrote: >> On Thu, Jan 05, 2017 at 05:21:09PM +0200, Roger Quadros wrote: >>> Hi, >>> >>> On 17/11/16 13:43, Sriram

Re: [PATCH 4/4] ARM: dts: sun8i: add OTG function to Lichee Pi Zero

On Wed, Jan 11, 2017 at 02:08:11PM -0600, Bin Liu wrote: > On Thu, Jan 12, 2017 at 03:55:33AM +0800, Icenowy Zheng wrote: > > > > > > 11.01.2017, 04:24, "Bin Liu" : > > > On Tue, Jan 03, 2017 at 11:25:34PM +0800, Icenowy Zheng wrote: > > >>  Lichee Pi Zero features a USB OTG port.

Re: [PATCH net] r8152: fix the sw rx checksum is unavailable

From: Hayes Wang Date: Wed, 11 Jan 2017 16:25:34 +0800 > Fix the hw rx checksum is always enabled, and the user couldn't switch > it to sw rx checksum. > > Note that the RTL_VER_01 only support sw rx checksum only. Besides, > the hw rx checksum for RTL_VER_02 is disabled

Re: [PATCH 4/4] ARM: dts: sun8i: add OTG function to Lichee Pi Zero

On Thu, Jan 12, 2017 at 04:13:34AM +0800, Icenowy Zheng wrote: > > > 12.01.2017, 04:08, "Bin Liu" : > > On Thu, Jan 12, 2017 at 03:55:33AM +0800, Icenowy Zheng wrote: > >>  11.01.2017, 04:24, "Bin Liu" : > >>  > On Tue, Jan 03, 2017 at 11:25:34PM +0800, Icenowy Zheng

Re: [PATCH 4/4] ARM: dts: sun8i: add OTG function to Lichee Pi Zero

On Thu, Jan 12, 2017 at 03:55:33AM +0800, Icenowy Zheng wrote: > > > 11.01.2017, 04:24, "Bin Liu" : > > On Tue, Jan 03, 2017 at 11:25:34PM +0800, Icenowy Zheng wrote: > >>  Lichee Pi Zero features a USB OTG port. > >> > >>  Add support for it. > >> > >>  Note: in order to use the

Re: [v4.4.40] patch backport error

On Wed, Jan 11, 2017 at 07:13:30PM +0200, Felipe Balbi wrote: > > hi, > > Bin Liu writes: > > I am unable to figure out what was happening, but there seems to be a > > patch backport error in v4.4.40. > > > > Commit c53af76d5de1 (usb: gadget: composite: always set ep->mult to a >

Re: [PATCH -next] usb: musb: dsps: make dsps_musb_clear_ep_rxintr() static

On Wed, Jan 11, 2017 at 04:44:02PM +, Wei Yongjun wrote: > From: Wei Yongjun > > Fixes the following sparse warning: > > drivers/usb/musb/musb_dsps.c:270:6: warning: > symbol 'dsps_musb_clear_ep_rxintr' was not declared. Should it be static? > > Signed-off-by: Wei

Re: [PATCH v5 1/2] USB: add switch to turn off padding of resume time delays

On Wed, 11 Jan 2017, Felipe Balbi wrote: > Hi, > > Todd Brandt writes: > > On Mon, 2017-01-09 at 09:44 +0100, Oliver Neukum wrote: > >> On Fri, 2017-01-06 at 16:45 -0800, Todd Brandt wrote: > >> > Add a kernel parameter that replaces the USB_RESUME_TIMEOUT > >> >

Re: [PATCH v5 1/2] USB: add switch to turn off padding of resume time delays

Hi, Todd Brandt writes: > On Mon, 2017-01-09 at 09:44 +0100, Oliver Neukum wrote: >> On Fri, 2017-01-06 at 16:45 -0800, Todd Brandt wrote: >> > Add a kernel parameter that replaces the USB_RESUME_TIMEOUT >> > and other hardcoded delay numbers with the USB spec

Re: [PATCH v5 1/2] USB: add switch to turn off padding of resume time delays

On Sat, 2017-01-07 at 11:58 -0500, Alan Stern wrote: > On Fri, 6 Jan 2017, Todd Brandt wrote: > > > Add a kernel parameter that replaces the USB_RESUME_TIMEOUT > > and other hardcoded delay numbers with the USB spec minimums. > > > > The USB subsystem currently uses some padded values for USB

Re: [PATCH v5 1/2] USB: add switch to turn off padding of resume time delays

On Mon, 2017-01-09 at 09:44 +0100, Oliver Neukum wrote: > On Fri, 2017-01-06 at 16:45 -0800, Todd Brandt wrote: > > Add a kernel parameter that replaces the USB_RESUME_TIMEOUT > > and other hardcoded delay numbers with the USB spec minimums. > > Hi, > > the problem with that is that distros

Re: [PATCH v2 2/4] usb: dwc2: Add binding for AHB burst

On Tuesday, January 10, 2017 3:23:24 PM CET John Youn wrote: > On 1/10/2017 3:03 PM, Christian Lamparter wrote: > > On Tuesday, January 10, 2017 1:46:56 PM CET John Youn wrote: > >> On 12/19/2016 6:49 AM, Christian Lamparter wrote: > >>> (Lot's of old stuff, that doesn't matter anymore) > > > >

Re: [v4.4.40] patch backport error

Hi, Bin Liu writes: > On Wed, Jan 11, 2017 at 07:13:30PM +0200, Felipe Balbi wrote: >> >> hi, >> >> Bin Liu writes: >> > I am unable to figure out what was happening, but there seems to be a >> > patch backport error in v4.4.40. >> > >> > Commit c53af76d5de1 (usb:

Re: [v4.4.40] patch backport error

On Wed, Jan 11, 2017 at 11:13:05AM -0600, Bin Liu wrote: > Hi, > > I am unable to figure out what was happening, but there seems to be a > patch backport error in v4.4.40. > > Commit c53af76d5de1 (usb: gadget: composite: always set ep->mult to a > sensible value) is backported from upstream >

Re: [v4.4.40] patch backport error

On Wed, Jan 11, 2017 at 07:13:30PM +0200, Felipe Balbi wrote: > > hi, > > Bin Liu writes: > > I am unable to figure out what was happening, but there seems to be a > > patch backport error in v4.4.40. > > > > Commit c53af76d5de1 (usb: gadget: composite: always set ep->mult to a >

Re: [v4.4.40] patch backport error

hi, Bin Liu writes: > I am unable to figure out what was happening, but there seems to be a > patch backport error in v4.4.40. > > Commit c53af76d5de1 (usb: gadget: composite: always set ep->mult to a > sensible value) is backported from upstream >

[v4.4.40] patch backport error

Hi, I am unable to figure out what was happening, but there seems to be a patch backport error in v4.4.40. Commit c53af76d5de1 (usb: gadget: composite: always set ep->mult to a sensible value) is backported from upstream eaa496ffaaf19591fe471a36cef366146eeb9153, however c53af76d5de1 has +

Re: [PATCH] usb: musb: Add support for optional VBUS irq to dsps glue layer

* Bin Liu [170111 05:42]: > On Tue, Jan 10, 2017 at 01:53:53PM -0600, Bin Liu wrote: > > On Thu, Jan 05, 2017 at 11:12:59AM -0800, Tony Lindgren wrote: > > > We can now configure the PMIC interrupt to provide us VBUS > > > events. In that case we don't need to constantly poll the >

Re: [PATCH] usb: dwc3 dwc3_exynos_probe() change goto labels to meaningful names

Hello Shuah, On 01/11/2017 01:45 PM, Shuah Khan wrote: > Change goto labels to meaningful names from a series of errNs. > > Signed-off-by: Shuah Khan > --- > drivers/usb/dwc3/dwc3-exynos.c | 22 +++--- > 1 file changed, 11 insertions(+), 11 deletions(-)

[PATCH] usb: dwc3 dwc3_exynos_probe() change goto labels to meaningful names

Change goto labels to meaningful names from a series of errNs. Signed-off-by: Shuah Khan --- drivers/usb/dwc3/dwc3-exynos.c | 22 +++--- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/drivers/usb/dwc3/dwc3-exynos.c

[PATCH -next] usb: musb: dsps: make dsps_musb_clear_ep_rxintr() static

From: Wei Yongjun Fixes the following sparse warning: drivers/usb/musb/musb_dsps.c:270:6: warning: symbol 'dsps_musb_clear_ep_rxintr' was not declared. Should it be static? Signed-off-by: Wei Yongjun --- drivers/usb/musb/musb_dsps.c | 2 +- 1

Re: dwc3: add support for hardware with multiple ports on USB2 hub enabled

On Mon, Jan 9, 2017 at 2:05 PM, Felipe Balbi wrote: > > Hi, > > Martin Blumenstingl writes: >> On Mon, Jan 9, 2017 at 1:39 PM, Felipe Balbi >> wrote: >>> >>> Hi, >>> >>> Martin Blumenstingl

[RFC PATCH 0/2] initialize (multiple) PHYs in xhci-plat

This series is the outcome of a discussion with Felipe Balbi, see [0] and [1]. The quick-summary of this is: - dwc3 already takes one USB2 and one USB3 PHY and initializes these correct - some other HCI platform drivers (like ehci-platform.c, xhci-mtk.c and ohci-platform.c) do not have a

[RFC PATCH 2/2] usb: host: xhci: plat: integrate the platform-roothub

This enables the platform-roothub for the xhci-plat driver. This allows specifying a PHY for each port via devicetree. All PHYs will then be enabled/disabled by the platform-roothub driver. One example where this is required is the Amlogic GXL and GXM SoCs: They are using a dwc3 USB controller

[RFC PATCH 1/2] usb: host: add a generic platform USB roothub driver

Many SoC platforms have separate devices for the USB PHY which are registered through the generic PHY framework. These PHYs have to be enabled to make the USB controller actually work. They also have to be disabled again on shutdown/suspend. Currently (at least) the following HCI platform drivers

Re: Advanced Format SAT devices show incorrect physical block size

On Tue, 10 Jan 2017, James Bottomley wrote: > On Tue, 2017-01-10 at 16:00 -0500, Alan Stern wrote: > > In theory, I suppose we could change the kernel so that it would > > default to READ CAPACITY(16) for devices that report a SCSI level >= > > 3, or something along those lines. In general we

Re: [PATCH v5 4/6] usb: xhci: use bus->sysdev for DMA configuration

On Wed, 11 Jan 2017, Mathias Nyman wrote: > On 17.11.2016 13:43, Sriram Dash wrote: > > From: Arnd Bergmann > > > > For xhci-hcd platform device, all the DMA parameters are not > > configured properly, notably dma ops for dwc3 devices. So, set > > the dma for xhci from sysdev.

[PATCH 0/1] xhci fix for usb-linus

Hi Greg One more fix that would be great to have in 4.10 It fixes a deadlock seen by Richard van der Hoff when unplugging the last USB-C device from a PCI hotluggable xhci controller Mathias Nyman (1): xhci: fix deadlock at host remove by running watchdog correctly

[PATCH 1/1] xhci: fix deadlock at host remove by running watchdog correctly

If a URB is killed while the host is removed we can end up in a situation where the hub thread takes the roothub device lock, and waits for the URB to be given back by xhci-hcd, blocking the host remove code. xhci-hcd tries to stop the endpoint and give back the urb, but can't as the host is

Re: Advanced Format SAT devices show incorrect physical block size

On Wed, 11 Jan 2017, Pali Rohár wrote: > On Tuesday 10 January 2017 15:29:23 Alan Stern wrote: > > > Tom Yan wrote that smartctl/hdparm "works" because they use the SCSI ATA > > > PASSTHROUGH command. It is not an option for kernel? > > > > No, because many devices do not implement SCSI ATA

[PATCH] Documentation: dt: dwc3: add reference to the usb-xhci properties

dwc3 internally creates a usb-xhci device which means that all properties documented in usb-xhci.txt are supported as well. Signed-off-by: Martin Blumenstingl --- Documentation/devicetree/bindings/usb/dwc3.txt | 4 1 file changed, 4 insertions(+) diff

Re: Advanced Format SAT devices show incorrect physical block size

On Tue, 10 Jan 2017, Dainius Masiliūnas wrote: > On Tue, Jan 10, 2017 at 9:00 PM, Alan Stern wrote: > > It is used for preventing the kernel from issuing a READ CAPACITY(16) > > command to the device. Normally the kernel would do this if the reply > > to READ

Re: crash in usb_hc_died+0x16 when unplugging usb-c dock

On 11.01.2017 13:27, Richard van der Hoff wrote: On 14/09/16 15:07, Mathias Nyman wrote: I've been staring at the code for a while and I think xhci might need a bigger rework in this area. For example the XHCI_STATE_DYING flag was originally a flag meaning that a watchdog function for a timed

Re: [PATCH v5 4/6] usb: xhci: use bus->sysdev for DMA configuration

On 17.11.2016 13:43, Sriram Dash wrote: From: Arnd Bergmann For xhci-hcd platform device, all the DMA parameters are not configured properly, notably dma ops for dwc3 devices. So, set the dma for xhci from sysdev. sysdev is pointing to device that is known to the system firmware

Re: [PATCH] usb: musb: Add support for optional VBUS irq to dsps glue layer

On Tue, Jan 10, 2017 at 01:53:53PM -0600, Bin Liu wrote: > On Thu, Jan 05, 2017 at 11:12:59AM -0800, Tony Lindgren wrote: > > We can now configure the PMIC interrupt to provide us VBUS > > events. In that case we don't need to constantly poll the > > status and can make it optional. This is only

Re: Advanced Format SAT devices show incorrect physical block size

On Tuesday 10 January 2017 15:29:23 Alan Stern wrote: > > Tom Yan wrote that smartctl/hdparm "works" because they use the SCSI ATA > > PASSTHROUGH command. It is not an option for kernel? > > No, because many devices do not implement SCSI ATA PASSTHROUGH. > (Consider devices whose underlying

Re: Advanced Format SAT devices show incorrect physical block size

On Tuesday 10 January 2017 14:12:25 James Bottomley wrote: > On Tue, 2017-01-10 at 16:00 -0500, Alan Stern wrote: > > In theory, I suppose we could change the kernel so that it would > > default to READ CAPACITY(16) for devices that report a SCSI level >= > > 3, or something along those lines.

Re: Fwd: Raw hid gadget

Apologies for the multiple send, I had an inbound mail problem. On Tue, Jan 10, 2017 at 8:53 AM, Greg KH wrote: > On Mon, Jan 09, 2017 at 10:24:42PM +0200, Rogan Dawes wrote: >> Sigh! This got bounced because of HTML parts. >> >> Another question that arises, though: >> >> What

[PATCH] usb: gadget: udc: atmel: remove memory leak

Commit bbe097f092b0 ("usb: gadget: udc: atmel: fix endpoint name") introduced a memory leak when unbinding the driver. The endpoint names would not be freed. Solve that by including the name as a string in struct usba_ep so it is freed when the endpoint is. Signed-off-by: Alexandre Belloni

Re: crash in usb_hc_died+0x16 when unplugging usb-c dock

On 14/09/16 15:07, Mathias Nyman wrote: I've been staring at the code for a while and I think xhci might need a bigger rework in this area. For example the XHCI_STATE_DYING flag was originally a flag meaning that a watchdog function for a timed out stop endpoint command is running and all URBs

Re: [PATCH v2 09/14] USB: serial: ch341: fix control-message error handling

On Fri, Jan 06, 2017 at 07:15:18PM +0100, Johan Hovold wrote: > A short control transfer would currently fail to be detected, something > which could lead to stale buffer data being used as valid input. > > Check for short transfers, and make sure to log any transfer errors. > > Fixes:

Re: [PATCHv14 2/3] usb: USB Type-C connector class

Hi Guenter, On Tue, Jan 10, 2017 at 09:35:42AM -0800, Guenter Roeck wrote: > > I guess we might as well then split the VDO into header, cert stat and > > product parts. What do you think? > > > > If it's OK, then should we change that file to "identity" and dump the > > whole response from

Re: [PATCH v3] USB: Add uPD78F0730 USB to Serial Adaptor Driver

On Wed, Jan 11, 2017 at 10:49:22AM +0300, Maksim Salau wrote: > Hi Johan, > > Thanks for feedback. > > > > * Dropped inversion of DTR and RTS signals > > > > Did you figure out whether this was needed or not, for example by > > comparing to the hardware flow control levels? > > The current

Re: [PATCH 1/3] ARM: dts: da850: Add the cppi41 dma node

On Tuesday 10 January 2017 07:15 PM, Alexandre Bailon wrote: > On 01/09/2017 07:26 PM, Sergei Shtylyov wrote: >>> +0x201000 0x1000 >>> +0x202000 0x1000 >>> +0x204000 0x4000>; >>> +reg-names = "glue", "controller", >>> +

Fwd: Raw hid gadget

For some odd reason, my emails are not getting through to the list. Even after removing the HTML parts. Hopefully this makes it. Rogan -- Forwarded message -- From: Rogan Dawes Date: Mon, Jan 9, 2017 at 10:24 PM Subject: Fwd: Raw hid gadget To:

Re: [PATCH 08/11] dmaengine: cppi41: Implement the glue for da8xx

On Tuesday 10 January 2017 09:19 PM, Tony Lindgren wrote: > * Alexandre Bailon [170110 07:23]: >> On 01/10/2017 11:05 AM, Sekhar Nori wrote: >>> On DA8xx, CPPI 4.1 DMAengine is not an independent system resource, but >>> embedded within the USB 2.0 controller. So, I think

Re: [PATCH 08/11] dmaengine: cppi41: Implement the glue for da8xx

On 01/10/2017 06:53 PM, Sergei Shtylyov wrote: > On 01/09/2017 07:06 PM, Alexandre Bailon wrote: > >> The da8xx has a cppi41 dma controller. > >It's called CPPI 4.1. :-) > >> This is add the glue layer required to make it work on da8xx, >> as well some changes in driver (e.g to manage

Re: [PATCH 08/11] dmaengine: cppi41: Implement the glue for da8xx

On 01/10/2017 04:22 PM, Alexandre Bailon wrote: > On 01/10/2017 11:05 AM, Sekhar Nori wrote: >> On Tuesday 10 January 2017 03:08 PM, Alexandre Bailon wrote: >>> On 01/09/2017 07:08 PM, Grygorii Strashko wrote: On 01/09/2017 10:06 AM, Alexandre Bailon wrote: > The da8xx has a

Re: [PATCHv14 2/3] usb: USB Type-C connector class

On Wed, 2017-01-11 at 09:57 +0200, Heikki Krogerus wrote: > On Tue, Jan 10, 2017 at 11:08:51AM +0100, Oliver Neukum wrote: > > > And since we are talking about the ABI, can we also change the listing > > > of the accessory mode back to just "audio" and "debug" like I > > > originally had it? I

[PATCH net] r8152: fix the sw rx checksum is unavailable

Fix the hw rx checksum is always enabled, and the user couldn't switch it to sw rx checksum. Note that the RTL_VER_01 only support sw rx checksum only. Besides, the hw rx checksum for RTL_VER_02 is disabled after commit b9a321b48af4 ("r8152: Fix broken RX checksums."). Re-enable it.