[RFC PATCH 6/7] dt-bindings: usb: typec-mux: Add property for default mux mode

2018-05-01 Thread Mats Karrman
For some devices it is necessary to specify a different initial mux mode to use after connection. E.g. some devices may not have USB SS support but just USB HS and an alternate mode and thus prefer TYPEC_MUX_NONE as default mode. Signed-off-by: Mats Karrman ---

[RFC PATCH 1/7] usb: typec: Generalize mux mode names

2018-05-01 Thread Mats Karrman
The current naming used for tcpc_mux_mode constants makes too much assumptioms about the usage of the signals. This patch replaces the names with generic names more closely tied to the Type-C specifications and also adds some new ones. At the same time TCPC_MUX_* defines are removed as they do not

[RFC PATCH 5/7] usb: typec: mux: pi3usb30532: Add support for supported mode properties

2018-05-01 Thread Mats Karrman
Signed-off-by: Mats Karrman --- drivers/usb/typec/mux/pi3usb30532.c | 29 +++-- 1 file changed, 23 insertions(+), 6 deletions(-) diff --git a/drivers/usb/typec/mux/pi3usb30532.c b/drivers/usb/typec/mux/pi3usb30532.c index d995883..3e564e6 100644

[RFC PATCH 7/7] usb: typec: mux: Allow default mux mode to be specified

2018-05-01 Thread Mats Karrman
This patch allows the default mux mode to be specified using a firmware property. Signed-off-by: Mats Karrman --- drivers/usb/typec/mux/pi3usb30532.c | 18 ++ drivers/usb/typec/tcpm.c| 2 +- include/linux/usb/typec.h | 1 + 3

[RFC PATCH 0/7] Fixe some issues with Type-C muxes

2018-05-01 Thread Mats Karrman
This series is based on usb-next commit 252427037a36 ("typec: tcpm: Fix incorrect 'and' operator"). In my work trying to adapt my project to the latest kernel I have ran into a number of issues. Consider the following series an initial poll on the acceptance of the solutions I have found. In

[RFC PATCH 3/7] usb: typec: Add API to find mux mode from its string representation

2018-05-01 Thread Mats Karrman
Signed-off-by: Mats Karrman --- drivers/usb/typec/class.c | 22 ++ include/linux/usb/typec.h | 1 + 2 files changed, 23 insertions(+) diff --git a/drivers/usb/typec/class.c b/drivers/usb/typec/class.c index 53df10d..c5432f4 100644 ---

[RFC PATCH 4/7] dt-bindings: usb: Add general documentation for USB Type-C muxes

2018-05-01 Thread Mats Karrman
This patch adds documentation of properties allowing the supported set of mux modes to be restricted in situations where a bad mode selection may have negative effects. Signed-off-by: Mats Karrman --- Documentation/devicetree/bindings/usb/typec-mux.txt | 18

[RFC PATCH 2/7] usb: typec: Move mux mode type definition to limit dependency

2018-05-01 Thread Mats Karrman
To avoid unnecessary dependencies on tcpm.h and to pave the way for comming patches, move the tcpc_mux_mode enum from tcpm.h to typec.h and change its name to typec_mux_mode (the enum constants already follow this naming). Signed-off-by: Mats Karrman ---

Re: [RFC 04/10] clk: samsung: Remove support for Exynos5440

2018-05-01 Thread Stephen Boyd
Quoting Krzysztof Kozlowski (2018-04-24 13:32:33) > The Exynos5440 is not actively developed, there are no development > boards available and probably there are no real products with it. > Remove wide-tree support for Exynos5440. > > Signed-off-by: Krzysztof Kozlowski > ---

Re: [PATCH v2 2/2] usb: dwc2: fix isoc split in transfer with no data

2018-05-01 Thread Doug Anderson
Hi, On Tue, May 1, 2018 at 8:04 PM, William Wu wrote: > If isoc split in transfer with no data (the length of DATA0 > packet is zero), we can't simply return immediately. Because > the DATA0 can be the first transaction or the second transaction > for the isoc split in

Re: [PATCH] musb: fix remote wakeup racing with suspend

2018-05-01 Thread Daniel Glöckner
Hi, On Tue, May 01, 2018 at 08:48:11AM -0500, Bin Liu wrote: > On Fri, Apr 27, 2018 at 03:00:05PM +0200, Daniel Glöckner wrote: > > It has been observed that writing 0xF2 to the power register while it > > reads as 0xF4 results in the register having the value 0xF0, i.e. clearing > > RESUME and

[PATCH v2 1/2] usb: dwc2: alloc dma aligned buffer for isoc split in

2018-05-01 Thread William Wu
The commit 3bc04e28a030 ("usb: dwc2: host: Get aligned DMA in a more supported way") rips out a lot of code to simply the allocation of aligned DMA. However, it also introduces a new issue when use isoc split in transfer. In my test case, I connect the dwc2 controller with an usb hs Hub

[PATCH v2 0/2] usb: dwc2: fix isoc split in transfer issue

2018-05-01 Thread William Wu
This patch fix dma unaligned problem and data lost problem for isoc split in transfer. Test on rk3288 platform, use an usb hs Hub (GL852G-12) and an usb fs audio device (Plantronics headset) to capture and playback. William Wu (2): usb: dwc2: alloc dma aligned buffer for isoc split in usb:

[PATCH v2 2/2] usb: dwc2: fix isoc split in transfer with no data

2018-05-01 Thread William Wu
If isoc split in transfer with no data (the length of DATA0 packet is zero), we can't simply return immediately. Because the DATA0 can be the first transaction or the second transaction for the isoc split in transaction. If the DATA0 packet with no data is in the first transaction, we can return

Re: [PATCH v2 1/2] usb: dwc2: alloc dma aligned buffer for isoc split in

2018-05-01 Thread Doug Anderson
Hi, On Tue, May 1, 2018 at 8:04 PM, William Wu wrote: > The commit 3bc04e28a030 ("usb: dwc2: host: Get aligned DMA in > a more supported way") rips out a lot of code to simply the > allocation of aligned DMA. However, it also introduces a new > issue when use isoc

Re: [PATCH v2 1/2] usb: misc: xapea00x: add driver for Xaptum ENF Access Card

2018-05-01 Thread David R. Bild
On Mon, Apr 30, 2018 at 11:05 AM, Greg Kroah-Hartman wrote: > > On Mon, Apr 30, 2018 at 07:54:17AM -0500, David R. Bild wrote: > > This commit adds a driver for the Xaptum ENF Access Card, a TPM2.0 > > hardware module for authenticating IoT devices and gateways. > > >

Re: [RFC 02/10] ata: ahci-platform: Remove support for Exynos5440

2018-05-01 Thread Rob Herring
On Tue, Apr 24, 2018 at 10:32:31PM +0200, Krzysztof Kozlowski wrote: > The Exynos5440 is not actively developed, there are no development > boards available and probably there are no real products with it. > Remove wide-tree support for Exynos5440. > > Signed-off-by: Krzysztof Kozlowski

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

2018-05-01 Thread Masahiro Yamada
Hi Felipe, 2018-04-19 20:03 GMT+09:00 Masahiro Yamada : > It is not a good idea to directly modify the resource of a platform > device. Modify its local copy, and pass it to devm_ioremap_resource() > so that we do not need to restore it in the failure path and the

Re: [RFC 03/10] cpufreq: exynos: Remove support for Exynos5440

2018-05-01 Thread Rob Herring
On Tue, Apr 24, 2018 at 10:32:32PM +0200, Krzysztof Kozlowski wrote: > The Exynos5440 is not actively developed, there are no development > boards available and probably there are no real products with it. > Remove wide-tree support for Exynos5440. > > Signed-off-by: Krzysztof Kozlowski

Re: [PATCH] thermal: samsung: Remove support for Exynos5440

2018-05-01 Thread Rob Herring
On Thu, Apr 26, 2018 at 01:21:12PM +0200, Bartlomiej Zolnierkiewicz wrote: > From: Krzysztof Kozlowski > Subject: [PATCH] thermal: samsung: Remove support for Exynos5440 > > The Exynos5440 is not actively developed, there are no development > boards available and probably there

RE: [PATCH v4 01/13] dt-bindings: connector: add properties for typec

2018-05-01 Thread Jun Li
Hi > -Original Message- > From: Heikki Krogerus [mailto:heikki.kroge...@linux.intel.com] > Sent: 2018年4月30日 19:24 > To: Jun Li > Cc: robh...@kernel.org; gre...@linuxfoundation.org; li...@roeck-us.net; > a.ha...@samsung.com; shufan_...@richtek.com; Peter Chen >

RE: [PATCH v4 02/13] dt-bindings: usb: add documentation for typec port controller(TCPCI)

2018-05-01 Thread Jun Li
Hi, > -Original Message- > From: Mats Karrman [mailto:mats.dev.l...@gmail.com] > Sent: 2018年4月30日 15:41 > To: Jun Li > Cc: robh...@kernel.org; gre...@linuxfoundation.org; > heikki.kroge...@linux.intel.com; li...@roeck-us.net; a.ha...@samsung.com; > shufan_...@richtek.com;

Re: [PATCH 2/4] usb: typec: tcpm: Release the role mux when exiting

2018-05-01 Thread Hans de Goede
Hi, On 30-04-18 14:41, Heikki Krogerus wrote: The ref count for the USB role switch device must be released after we are done using the switch. Fixes: c6962c29729c ("usb: typec: tcpm: Set USB role switch to device mode when configured as such") Signed-off-by: Heikki Krogerus

Re: [PATCH] usb: musb: Support gadget mode when the port is set to dual role

2018-05-01 Thread Bin Liu
On Mon, Apr 30, 2018 at 11:08:42PM +0200, Paul Kocialkowski wrote: > Hi, > > Le samedi 21 avril 2018 à 09:34 -0500, Bin Liu a écrit : > > Okay, this came down to an argument that whether we should require > > loading a gadget driver on a dual-role port to work in host mode, > > which is currently

Re: [PATCH 1/4] platform: x86: intel_cht_int33fe: Fix dependencies

2018-05-01 Thread Hans de Goede
Hi, On 30-04-18 14:41, Heikki Krogerus wrote: The driver will not probe unless bq24190 is loaded, so making it a dependency. Hmm, the dependency is pure run-time, with this Kconfig change if a user now decides to builtin the intel_cht_int33fe driver, the bq24190 driver must also be builtin,

Re: [PATCH 4/4] usb: roles: intel_xhci: Always allow user control

2018-05-01 Thread Hans de Goede
Hi, On 30-04-18 14:41, Heikki Krogerus wrote: Trying to determine the USB port type with this mux is very difficult. To simplify the situation, always allowing user control, even if the port is USB Type-C port. Signed-off-by: Heikki Krogerus > ---

Re: [PATCH] musb: fix remote wakeup racing with suspend

2018-05-01 Thread Bin Liu
Hi, On Fri, Apr 27, 2018 at 03:00:05PM +0200, Daniel Glöckner wrote: > It has been observed that writing 0xF2 to the power register while it > reads as 0xF4 results in the register having the value 0xF0, i.e. clearing > RESUME and setting SUSPENDM in one go does not work. It might also violate >

Re: [PATCH] usb: musb: Support gadget mode when the port is set to dual role

2018-05-01 Thread Paul Kocialkowski
Hi, Le mardi 01 mai 2018 à 07:25 -0500, Bin Liu a écrit : > On Mon, Apr 30, 2018 at 11:08:42PM +0200, Paul Kocialkowski wrote: > > Hi, > > > > Le samedi 21 avril 2018 à 09:34 -0500, Bin Liu a écrit : > > > Okay, this came down to an argument that whether we should require > > > loading a gadget

Re: [RFC 01/10] ARM: dts: exynos: Remove Exynos5440

2018-05-01 Thread Rob Herring
On Tue, Apr 24, 2018 at 10:32:30PM +0200, Krzysztof Kozlowski wrote: > The Exynos5440 (quad-core A15 with GMAC, PCIe, SATA) was targeting > server platforms but it did not make it to the market really. There are > no development boards with it and probably there are no real products > neither.

Re: [PATCH 1/2] dt-bindings: add MediaTek XS-PHY binding

2018-05-01 Thread Rob Herring
On Wed, Apr 25, 2018 at 03:45:28PM +0800, Chunfeng Yun wrote: > Add a DT binding documentation of XS-PHY for MediaTek SoCs > with USB3.1 GEN2 controller > > Signed-off-by: Chunfeng Yun > --- > .../devicetree/bindings/phy/phy-mtk-xsphy.txt | 127 >

Re: [PATCH] usb: musb: Support gadget mode when the port is set to dual role

2018-05-01 Thread Bin Liu
On Tue, May 01, 2018 at 03:26:57PM +0200, Paul Kocialkowski wrote: > Hi, > > Le mardi 01 mai 2018 à 07:25 -0500, Bin Liu a écrit : > > On Mon, Apr 30, 2018 at 11:08:42PM +0200, Paul Kocialkowski wrote: > > > Hi, > > > > > > Le samedi 21 avril 2018 à 09:34 -0500, Bin Liu a écrit : > > > > Okay,