Hi,
[auto build test WARNING on net-next/master]
url:
https://github.com/0day-ci/linux/commits/Kristian-Evensen/cdc_ether-Improve-ZTE-MF823-831-910-handling/20160723-093100
config: x86_64-randconfig-i0-201629 (attached as .config)
compiler: gcc-4.9 (Debian 4.9.3-14) 4.9.3
reproduce:
#
On Fri, Jul 22, 2016 at 2:16 PM, Alan Stern wrote:
>> I'd suggest a comment referencing the spec then :)
>
> Don't be silly. Nobody could possibly understand the code without
> reading the spec first. There's no need to mention the spec in a
> comment; it's an obvious prerequisite.
I've managed
On Fri, 22 Jul 2016, Bruce Korb wrote:
> HI,
>
> On Fri, Jul 22, 2016 at 12:57 PM, Alan Stern
> wrote:
> > They come from the xHCI hardware.
>
> I'd suggest a comment referencing the spec then :)
Don't be silly. Nobody could possibly understand the code without
reading the spec first. Ther
HI,
On Fri, Jul 22, 2016 at 12:57 PM, Alan Stern wrote:
> They come from the xHCI hardware.
I'd suggest a comment referencing the spec then :)
> /* Completion Code - only applicable for some types of TRBs */
> #define COMP_CODE_MASK (0xff << 24)
> #define GET_COMP_CODE(p) (((p) & COMP_CODE_MASK
On Fri, 22 Jul 2016, Bruce Korb wrote:
> A few questions:
>
> 1. Where do the values for TRB completion codes come from?
> COMP_BW_ERR and COMP_2ND_BW_ERR seem to be defined
> and then only used in a switch statement.
They come from the xHCI hardware.
> 2. xhci_queue_configure_endpoint
A few questions:
1. Where do the values for TRB completion codes come from?
COMP_BW_ERR and COMP_2ND_BW_ERR seem to be defined
and then only used in a switch statement.
2. xhci_queue_configure_endpoint() seems to be the function for
sending down a command that somehow loads the "BW_E
On Fri, 22 Jul 2016, Oliver Neukum wrote:
> It is always possible to go back to the usb_device if you know
> the interface. It is unnecessary to store the device and thus should
> not be done.
That is not a hard-and-fast law -- the kernel isn't based on Codd's
rules for relational databases. Thi
This patch adds support for the GPIO found on the CP2105. Unlike the GPIO
provided by some of the other devices supported by the cp210x driver, the
GPIO on the CP2015 is muxed on pins otherwise used for serial control
lines. The GPIO have been configured in 2 separate banks as the choice to
configu
This patch series includes a resend of v5 of a patch to provide GPIO support
for cp210x.
Martyn Welch (1):
USB: serial: cp210x: Adding GPIO support for CP2105
drivers/usb/serial/cp210x.c | 351 +++-
1 file changed, 348 insertions(+), 3 deletions(-)
--
The whole Kconfig entries of the USB subsystem are surrounded with
"if USB_SUPPORT" ... "endif", so CONFIG_USB_SUPPORT=y is surely met
when these two Kconfig options are visible.
Signed-off-by: Masahiro Yamada
---
drivers/usb/core/Kconfig | 1 -
drivers/usb/dwc3/Kconfig | 2 +-
2 files changed,
It is always possible to go back to the usb_device if you know
the interface. It is unnecessary to store the device and thus should
not be done.
Signed-off-by: Oliver Neukum
---
drivers/usb/storage/uas.c | 20 +---
1 file changed, 9 insertions(+), 11 deletions(-)
diff --git a/dr
Add usb2-phy nodes and specify phys phandle for ehci.
Signed-off-by: Frank Wang
---
Changes in v9:
- Move the usb gpio config to rk3399-evb.dts
- Fix ehci phy-names property.
arch/arm64/boot/dts/rockchip/rk3399.dtsi | 42 +-
1 file changed, 41 insertions(+), 1 d
Add vcc5v0_host regulator for usb2-phy and enable host-port support.
Signed-off-by: Frank Wang
---
arch/arm64/boot/dts/rockchip/rk3399-evb.dts | 44 +++
1 file changed, 44 insertions(+)
diff --git a/arch/arm64/boot/dts/rockchip/rk3399-evb.dts
b/arch/arm64/boot/dts/roc
The newer SoCs (rk3366, rk3399) take a different usb-phy IP block
than rk3288 and before, and most of phy-related registers are also
different from the past, so a new phy driver is required necessarily.
Signed-off-by: Frank Wang
Suggested-by: Heiko Stuebner
Suggested-by: Guenter Roeck
Suggested
Signed-off-by: Frank Wang
Acked-by: Rob Herring
Reviewed-by: Heiko Stuebner
---
Changes in v9: None
Changes in v8: None
Changes in v7: None
Changes in v6:
- Changed '_' to '-' for otg-id and otg-bvalid property.
Changes in v5:
- Added 'reg' property to identify the different phy-blocks.
The newer SoCs (rk3366, rk3399) of Rock-chip take a different usb-phy
IP block than rk3288 and before, and most of phy-related registers are
also different from the past, so a new phy driver is required necessarily.
These series patch add phy-rockchip-inno-usb2.c and the corresponding
dt-bindings.
16 matches
Mail list logo