The following changes since commit 33d930e59a98fa10a0db9f56c7fa2f21a4aef9b9:
Linux 4.14-rc5 (2017-10-15 21:01:12 -0400)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/
tags/usb-4.14-rc6
for you to fetch changes up to 1ac7db6db1eeff9
On 10/20/2017 3:57 PM, Minas Harutyunyan wrote:
> On 10/20/2017 12:20 AM, John Stultz wrote:
>> On Wed, Oct 18, 2017 at 11:46 PM, Minas Harutyunyan
>> wrote:
>>> Could you please apply this patch. Please not apply your patch series
>>> "[PATCH 0/3] dwc2 fixes for edge cases on hikey" to check only
On Fri, Oct 20, 2017 at 04:51:24PM +0100, Jon Hunter wrote:
> Hi Philipp,
>
> On 19/10/17 16:17, Philipp Zabel wrote:
> > Hi Jon, Thierry,
> >
> > On Wed, 2017-07-19 at 17:59 +0200, Philipp Zabel wrote:
> >> From: Vivek Gautam
> >>
> >> Make use of of_reset_control_array_get_exclusive() to manag
Hi,
In our latest ARM64-based CPU, we use the DesignWare USB which is
xHCI-compatible. For some reasons, we disable USB3.0 support so remove the
unnecessary USB3.0 capability structure information as specified in the
xHCI specification 1.1, section 7.2:
"At least one of these capability structures
On 23.10.2017 12:37, Thang Q. Nguyen wrote:
Hi,
In our latest ARM64-based CPU, we use the DesignWare USB which is
xHCI-compatible. For some reasons, we disable USB3.0 support so remove the
unnecessary USB3.0 capability structure information as specified in the
xHCI specification 1.1, section 7.2:
This product is named 'TP-LINK USB 3.0 Gigabit Ethernet Network
Adapter (Model No.is UE300)'. It uses chip RTL8153 and works with
driver drivers/net/usb/r8152.c
Signed-off-by: Ran Wang
---
drivers/net/usb/cdc_ether.c | 8
drivers/net/usb/r8152.c | 2 ++
2 files changed, 10 insertion
Hi Kishon,
Please review this so that I can re-submit patch-set based on this approach.
On 10/9/2017 1:33 PM, Manu Gautam wrote:
> Hi Kishon
>
> On 10/5/2017 2:38 PM, Manu Gautam wrote:
>> Kishon,
>> What would you suggest here?
>> Should we add new calls e.g. phy_get/set_current_speed like::
>>
Am Montag, den 23.10.2017, 18:10 +0800 schrieb Ran Wang:
> This product is named 'TP-LINK USB 3.0 Gigabit Ethernet Network
> Adapter (Model No.is UE300)'. It uses chip RTL8153 and works with
> driver drivers/net/usb/r8152.c
>
Hi,
just for the record, have you confirm that it fails with cdc-ether
On 10/19/2017 5:35 PM, Dinh Nguyen wrote:
>
>
> On 10/19/2017 06:55 AM, Grigor Tovmasyan wrote:
>> On 10/18/2017 6:07 PM, Marek Vasut wrote:
>>> On 10/18/2017 04:05 PM, Dinh Nguyen wrote:
Hi,
I'm trying to bringup the DWC2 USB IP version 330A on a new Stratix10
SoC and have en
The Huawei ME906 (12d1:15c1) comes with a standard ECM interface that
requires management via AT commands sent over one of the control TTYs
(e.g. connected with AT^NDISDUP).
Signed-off-by: Aleksander Morgado
---
drivers/net/usb/cdc_ether.c | 6 ++
1 file changed, 6 insertions(+)
diff --git
On Mon, Oct 23, 2017 at 2:19 AM, Minas Harutyunyan
wrote:
> Could you please verify on your setup follow patches:
> 1. Vardan's patch.
> 2. Patch for TOUTCAL&USBTRDTIM programming (new version see below).
> 4. Your patch 2/3 to avoid "Mode Mismatch" interrupts.
> 5. Your patch 3/3 to set udc state
We've found that while in host mode, using Android, if one runs
the command:
stop adbd
The existing usb devices being utilized in host mode are disconnected.
This is most visible with usb networking devices.
This seems to be due to adbd closing the file:
/dev/usb-ffs/adb/ep0
Which calls ffs_e
So here is v2 of a few dwc2 fixes that I've been using with HiKey.
I'm not totally sure these are all ideal, but they avoid edge case
issues that we have been running into with switching between
gadget mode and host mode.
I'd guess the first two are potentially -stable material, and
the last might
In the earlier commit dad3f793f20f ("usb: dwc2: Make sure we
disconnect the gadget state"), I was trying to fix up the
fact that we somehow weren't disconnecting the gadget state,
so that when the OTG port was plugged in the second time we
would get warnings about the state tracking being wrong.
(
It has been noticed that the dwc2 udc state reporting doesn't
seem to work (at least on HiKey boards). Where after the initial
setup, the sysfs /sys/class/udc/f72c.usb/state file would
report "configured" no matter the state of the OTG port.
This patch adds a call so that we report to the UDC
On Mon, Oct 23, 2017 at 1:41 PM, John Stultz wrote:
> On Mon, Oct 23, 2017 at 2:19 AM, Minas Harutyunyan
> wrote:
>> Could you please verify on your setup follow patches:
>> 1. Vardan's patch.
>> 2. Patch for TOUTCAL&USBTRDTIM programming (new version see below).
>> 4. Your patch 2/3 to avoid "Mo
Hi Arnd,
thank you for taking 10 minutes to discuss this in person with me!
On Fri, Oct 20, 2017 at 12:10 AM, Arnd Bergmann wrote:
> On Thu, Oct 19, 2017 at 11:25 PM, Martin Blumenstingl
> wrote:
>>> Does dwc2 also use separate nodes for the roothub? From your
>>> description it sounds like it
Hi,
On Sun, Oct 22, 2017 at 5:16 AM, Chunfeng Yun wrote:
> Hi,
>
> On Thu, 2017-10-19 at 23:32 +0200, Martin Blumenstingl wrote:
>> Hi Chunfeng Yun,
>>
>> many thanks for your efforts (testing and explaining the Mediatek SoC
>> implementatino) on the earlier versions of this series!
>>
>> On Tue,
On 10/22/2017 10:38 PM, Serge Semin wrote:
USB251xb as well as USB2517 datasheet states, that all these
hubs differ by number of ports declared as the last digit in the
model name. So USB2512 got two ports, USB2513 - three, and so on.
Such setting must be reflected in the device specific data
str
Hi,
please see comments below for some nit-picks.
On 10/22/2017 10:38 PM, Serge Semin wrote:
There are USB2517 and USB2517i hubs, which have almost the same
registers space as already supported USB251xBi series. The difference
it in DIDs and in a few functions. This patch adds the USB2517/i data
Hi,
again some nit-picks below...
On 10/22/2017 10:38 PM, Serge Semin wrote:
This parameters may be varied in accordance with hardware specifics.
So lets add the corresponding settings to the usb251xb driver dts
specification.
Signed-off-by: Serge Semin
---
drivers/usb/misc/usb251xb.c | 24 +
The following was used to switch the Novatel USB730L from user mode
(product ID 0x9030) into enterprise mode (product ID 0x9032):
* Tested with Linux kernel 3.14.15 on a 32bit ARM machine (kernel is
compiled without IPV6) and with static HID driver
* Kernel patches 1: ignore HID interface of Novate
This extends the existing example from the USB xHCI binding
documentation so it includes the roothub and an actual device.
The goal of this is to show that the roothub is specified alongside the
actual devices on the USB bus (which is important because a device on
the USB bus - for example a hub -
This integrates the PHY roothub wrapper into the core hcd
infrastructure. Multiple PHYs which are part of the roothub devicetree
node (which is a sub-node of the sysdev's node) are now managed
(= powered on/off when needed), by the new usb_phy_roothub code.
One example where this is required is th
A USB root-hub may have several PHYs which need to be configured before
the root-hub starts working.
This adds the documentation for such a USB root-hub as well as a hint
regarding the child-nodes on XHCI controllers which can include the
roothub.
Signed-off-by: Martin Blumenstingl
Acked-by: Rob
This series is the outcome of a discussion with Felipe Balbi,
see [0] and [1] as well as Mathias Nyman, see [7] and [8].
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 a
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
Adds bindings documentation for the max3421 driver.
Signed-off-by: Jules Maselbas
Acked-by: Rob Herring
---
.../devicetree/bindings/usb/maxim,max3421.txt | 25 ++
1 file changed, 25 insertions(+)
create mode 100644 Documentation/devicetree/bindings/usb/maxim,max3421.tx
Hi,
This patchset adds devicetree support to the max3421 driver.
Theses modification are based on a previous (unapplied) patch
series by Alexander Amelkin [1].
Changes in v3:
* Documentation modification, interrupt-parent is optional.
Changes in v2:
* The platform_data is no longer freed in ma
Adds support for devicetree to the max3421 driver.
Signed-off-by: Jules Maselbas
---
drivers/usb/host/max3421-hcd.c | 75 +-
1 file changed, 74 insertions(+), 1 deletion(-)
diff --git a/drivers/usb/host/max3421-hcd.c b/drivers/usb/host/max3421-hcd.c
index
On 10/23/2017 09:03 AM, Minas Harutyunyan wrote:
> On 10/19/2017 5:35 PM, Dinh Nguyen wrote:
>>
>>
>> On 10/19/2017 06:55 AM, Grigor Tovmasyan wrote:
>>> On 10/18/2017 6:07 PM, Marek Vasut wrote:
On 10/18/2017 04:05 PM, Dinh Nguyen wrote:
> Hi,
>
> I'm trying to bringup the DWC2
On Mon, 2017-10-23 at 23:57 +0200, Martin Blumenstingl wrote:
> 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 shutd
On Mon, 2017-10-23 at 23:57 +0200, Martin Blumenstingl wrote:
> This integrates the PHY roothub wrapper into the core hcd
> infrastructure. Multiple PHYs which are part of the roothub devicetree
> node (which is a sub-node of the sysdev's node) are now managed
> (= powered on/off when needed), by t
Hi Oliver
> -Original Message-
> From: Oliver Neukum [mailto:oneu...@suse.com]
> Sent: Monday, October 23, 2017 6:56 PM
> To: Ran Wang
> Cc: David S . Miller ; hayeswang
> ; linux-ker...@vger.kernel.org; linux-
> u...@vger.kernel.org; net...@vger.kernel.org
> Subject: Re: [PATCH] drivers/n
When system is running, if usb2 phy is forced to bypass utmi signals,
all PLL will be turned off, and it can't detect device connection
anymore, so replace force mode with auto mode which can bypass utmi
signals automatically if no device attached for normal flow.
But keep the force mode to fix RX
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Addresses-Coverity-ID: 1222118
Signed-off-by: Gustavo A. R. Silva
---
drivers/usb/phy/phy-msm-usb.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/phy/phy-msm-usb.c b/dri
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Signed-off-by: Gustavo A. R. Silva
---
drivers/usb/image/mdc800.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/image/mdc800.c b/drivers/usb/image/mdc800.c
index e92540a
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Addresses-Coverity-ID: 1162594
Signed-off-by: Gustavo A. R. Silva
---
drivers/usb/core/urb.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/core/urb.c b/drivers/usb/core/
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Addresses-Coverity-ID: 703128
Signed-off-by: Gustavo A. R. Silva
---
drivers/usb/gadget/function/f_tcm.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/gadget/function/f_
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Addresses-Coverity-ID: 1397608
Signed-off-by: Gustavo A. R. Silva
---
drivers/usb/musb/musb_core.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/musb/musb_core.c b/drive
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Addresses-Coverity-ID: 1350962
Signed-off-by: Gustavo A. R. Silva
---
drivers/usb/gadget/function/u_serial.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/gadget/functio
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Addresses-Coverity-ID: 145713
Signed-off-by: Gustavo A. R. Silva
---
drivers/usb/gadget/udc/goku_udc.c | 14 +-
1 file changed, 9 insertions(+), 5 deletions(-)
diff --git a/d
Hi Oliver,
On Wed, Oct 18, 2017 at 5:31 PM, Oliver Neukum wrote:
> Am Mittwoch, den 18.10.2017, 15:15 +0800 schrieb Daniel Drake:
>> Notes:
>> v2:
>> - Handle quirk later in suspend, to avoid interfering with other parts
>> of the suspend routine.
>> - Don't do the disconnect on
Add dts for usb module of Hikey960.
Signed-off-by: Yu Chen
Signed-off-by: Ning Fan
Signed-off-by: Di Yang
Signed-off-by: Rui Li
---
arch/arm64/boot/dts/hisilicon/hi3660.dtsi | 39 +++
1 file changed, 39 insertions(+)
diff --git a/arch/arm64/boot/dts/hisilicon/hi3
The usb controller of Kirin960 is DesignWare Cores SuperSpeed USB 3.0
Controller.
The patch modifies dwc3 for support Kirin960 and adds codes for a USB Hub on
board Hikey960.
Signed-off-by: Yu Chen
Signed-off-by: Ning Fan
Signed-off-by: Di Yang
Signed-off-by: Rui Li
---
arch/arm64/configs/
The HiKey960 development platform is based around the HiSilicon Kirin960.
The patch sets add support for usb of HiKey960.
Fan Ning (3):
Add document for usb of Hikey960
Modify dwc3 code for support usb of Hikey960
Modify device tree for support Hikey960
.../devicetree/bindings/usb/hisilico
DT bindings for usb of Hikey960.
Signed-off-by: Yu Chen
Signed-off-by: Ning Fan
Signed-off-by: Di Yang
Signed-off-by: Rui Li
---
.../devicetree/bindings/usb/hisilicon-usb.txt | 38 ++
1 file changed, 38 insertions(+)
create mode 100644 Documentation/devicetree/bindi
47 matches
Mail list logo
