es
bInterval 0
bMaxBurst 15
If helpful I could also provide an USB3 analyzer log.
Regards,
David
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo i
it make
sense for there to be some mechanism that can add firmware to the kernel
image after the fact so that it can create a 'cache' of the firmware
needed for the particular system as part of that systems kernel image?
David Lang
--
To unsubscribe from this list: send the line "un
modules to autoload, why can't
scripts be written to figure out what drives to build into a system?
David Lang
-
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Sun, 6 Jan 2008, Stefan Richter wrote:
David Lang wrote:
On Sun, 6 Jan 2008, Stefan Richter wrote:
Module autoloading is quite different.
but if boot scripts can figure out what modules to autoload, why can't
scripts be written to figure out what drives to build into a system?
Be
- Add Support For AT&T 881U.
- I Have been testing patch for sometime with out any issues.
Signed-off-by: David Roth <[EMAIL PROTECTED]>
---
--- sierra.c 2008-01-28 05:52:14.0 -0600
+++ ../Working/sierra/sierra.c 2008-01-26 20:34:48.0 -0600
@@ -117,6 +117,7 @@
{
ee
some of my work.
best regards.
David Cox
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
From: Oliver Neukum
Date: Mon, 2 May 2016 13:06:12 +0200
> Allow for SS+ USB
>
> Signed-off-by: Oliver Neukum
Applied.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/m
From: Oliver Neukum
Date: Mon, 2 May 2016 13:06:14 +0200
> Allow for SS+ USB
>
> Signed-off-by: Oliver Neukum
Applied.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/m
From: Oliver Neukum
Date: Mon, 2 May 2016 13:06:13 +0200
> Allow for SS+ USB
>
> Signed-off-by: Oliver Neukum
Applied.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/m
ixed, but there are some changes needed to inc_enq()
> as well together with this fix.
> Otherwise the last TRB of a event ring won't be used
Is it worth using separate functions for the event rings?
I remember looking at it a long time ago and almost all the call sites
know what sort
On 04/14/2016 01:35 PM, David Lechner wrote:
The "da8xx USB clocks" patch series was growing a bit too big, so on the advice
of Sekhar Nori, I am splitting it into two parts. This part contains everything
in drivers/ and the other part will contain everything in arch/arm/mach-davi
On 05/04/2016 01:10 PM, Bin Liu wrote:
Hi,
On Thu, Apr 14, 2016 at 01:35:14PM -0500, David Lechner wrote:
The initial use for this is for PHYs that have a mode related to USB OTG.
There are several SoCs (e.g. TI OMAP and DA8xx) that have a mode setting
in the USB PHY to override OTG VBUS and
On 05/04/2016 01:39 PM, Bin Liu wrote:
Have you already tested this? I never tried changing mode via sysfs, but
by quickly reviewing the code, I am wondering how it works. the core
only calls ops->set_mode() but nothing else. To really switch the mode,
the driver has to talk to the root hub, and
From: Dan Carpenter
Date: Wed, 4 May 2016 09:21:02 +0300
> If the fn() calls fail then "buf" is uninitialized. Just return early
> in that situation.
>
> Signed-off-by: Dan Carpenter
Applied.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to m
From: Dan Carpenter
Date: Wed, 4 May 2016 09:22:01 +0300
> If the call to fn() fails then "buf" is uninitialized. Just return the
> error code in that case.
>
> Signed-off-by: Dan Carpenter
Applied.
Please, in the future, use a consistent subsystem prefixing scheme. In these
two patches you
On 05/04/2016 01:39 PM, Bin Liu wrote:
On Wed, May 04, 2016 at 01:20:36PM -0500, David Lechner wrote:
This is something I actually plan on using because the device I am
using (LEGO MINDSTORMS EV3) is not wired for OTG, so the callback is
needed to override the ID and VBUS signals when switching
This is a new phy driver for the SoC USB controllers on the TI DA8xx
family of microcontrollers. The USB 1.1 PHY is just a simple on/off.
The USB 2.0 PHY also allows overriding the VBUS and ID pins.
Signed-off-by: David Lechner
---
drivers/phy/Kconfig | 10 ++
drivers/phy/Makefile
Use the new phy-da8xx-usb driver to take the place of the mach code that
pokes CFGCHIP2 in the da8xx musb glue driver. This unbreaks the driver.
Signed-off-by: David Lechner
---
drivers/usb/musb/Kconfig | 2 +-
drivers/usb/musb/da8xx.c | 135 ++-
2
Simplify things a bit by using devm functions where possible.
Signed-off-by: David Lechner
---
drivers/usb/musb/da8xx.c | 19 +--
1 file changed, 5 insertions(+), 14 deletions(-)
diff --git a/drivers/usb/musb/da8xx.c b/drivers/usb/musb/da8xx.c
index b03d3b8..0c1997c 100644
they didn't really belong there anyway.
Signed-off-by: David Lechner
Acked-by: Lee Jones
---
include/linux/mfd/da8xx-cfgchip.h | 153 ++
include/linux/platform_data/usb-davinci.h | 22 -
2 files changed, 153 insertions(+), 22 deletions(-)
create
Including mach/* is frowned upon in device drivers, so get rid of it.
This replaces usb20_clk and code that pokes CFGCHIP2 with a proper phy
driver.
Signed-off-by: David Lechner
Acked-by: Alan Stern
---
drivers/usb/host/Kconfig | 1 +
drivers/usb/host/ohci-da8xx.c | 102
.
Suggested-by: Kishon Vijay Abraham I
Signed-off-by: David Lechner
---
drivers/phy/phy-core.c | 15 +++
include/linux/phy/phy.h | 17 +
2 files changed, 32 insertions(+)
diff --git a/drivers/phy/phy-core.c b/drivers/phy/phy-core.c
index e7e574d..fe0344c 100644
--- a
Device tree binding for new phy-da8xx-usb driver.
Signed-off-by: David Lechner
Acked-by: Rob Herring
---
.../devicetree/bindings/phy/phy-da8xx-usb.txt | 40 ++
1 file changed, 40 insertions(+)
create mode 100644 Documentation/devicetree/bindings/phy/phy-da8xx-usb.txt
v5 changes:
Functionally, nothing has really changed. Just some cleanups based on feedback.
* Renamed "usbphy" to "usb_phy" or "usb-phy" as appropriate
* License header matches MODULE_LICENSE in new phy driver
David Lechner (7):
mfd: da8xx-cfgchip: New header fi
v5 changes: renamed "usbphy" to "usb_phy" or "usb-phy" as appropriate
David Lechner (5):
ARM: davinci: da8xx: add usb phy clocks
ARM: davinci: da8xx: Add CFGCHIP syscon platform declaration.
ARM: davinci: da8xx: Add USB PHY platform declaration
ARM: DTS:
The CFGCHIP registers are used by a number of devices, so using a syscon
device to share them. The first consumer of this will by the phy-da8xx-usb
driver.
Signed-off-by: David Lechner
---
arch/arm/mach-davinci/board-da830-evm.c | 4
arch/arm/mach-davinci/board-da850-evm.c | 4
Add a node for the new usb phy driver.
Signed-off-by: David Lechner
---
arch/arm/boot/dts/da850.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/da850.dtsi b/arch/arm/boot/dts/da850.dtsi
index 9546ace..b2ebbe5 100644
--- a/arch/arm/boot/dts/da850.dtsi
+++ b/arch
Add a syscon node for the SoC CFGCHIPn registers. This is needed for
the new usb phy driver.
Signed-off-by: David Lechner
---
arch/arm/boot/dts/da850.dtsi | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/da850.dtsi b/arch/arm/boot/dts/da850.dtsi
index cf1aad8..9546ace
replaced with the new clock registration functions.
Signed-off-by: David Lechner
---
arch/arm/mach-davinci/board-da830-evm.c | 22 ++-
arch/arm/mach-davinci/board-omapl138-hawk.c | 16 +-
arch/arm/mach-davinci/include/mach/da8xx.h | 3 +
arch/arm/mach-davinci/usb-da8xx.c | 219
There is now a proper phy driver for the DA8xx SoC USB PHY. This adds the
platform device declarations needed to use it.
Signed-off-by: David Lechner
---
arch/arm/mach-davinci/board-da830-evm.c | 28 +---
arch/arm/mach-davinci/board-omapl138-hawk.c | 5 +
arch
On 05/10/2016 06:26 AM, Sergei Shtylyov wrote:
On 5/10/2016 2:46 AM, David Lechner wrote:
The CFGCHIP registers are used by a number of devices, so using a syscon
device to share them. The first consumer of this will by the
phy-da8xx-usb
driver.
Signed-off-by: David Lechner
[...]
diff
From: John Stultz
Date: Mon, 16 May 2016 20:36:15 -0700
> In testing with HiKey, we found that since
> commit 3f30b158eba5 ("asix: On RX avoid creating bad Ethernet
> frames"),
> we're seeing lots of noise during network transfers:
...
> And network throughput ends up being pretty bursty and slo
From: Heinrich Schuchardt
Date: Wed, 18 May 2016 02:13:30 +0200
> (!count || count < 4) is always true.
> So let's remove the coding which is dead at least since 2005.
>
> Signed-off-by: Heinrich Schuchardt
Applied.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the
From: Arnd Bergmann
Date: Fri, 20 May 2016 10:22:30 +0200
> The latest dead-code removal was slightly incomplete and
> left a few things behind that we now get compiler warnings
> for:
>
> drivers/net/usb/pegasus.c: In function 'read_bulk_callback':
> drivers/net/usb/pegasus.c:475:1: error: labe
From: Petko Manolov
Date: Fri, 20 May 2016 10:33:47 +0300
> On 16-05-19 11:35:42, David Miller wrote:
>> From: Heinrich Schuchardt
>> Date: Wed, 18 May 2016 02:13:30 +0200
>>
>> > (!count || count < 4) is always true.
>> > So let's remo
From: Robert Dobrowolski
Date: Thu, 19 May 2016 11:56:09 +0200
> From: Rafal Redzimski
>
> Current implementation updates the mtu size and notify cdc_ncm
> device using USB_CDC_SET_MAX_DATAGRAM_SIZE request about datagram
> size change instead of changing rx_urb_size.
>
> Whenever mtu is being
From: Muhammad Falak R Wani
Date: Thu, 19 May 2016 19:26:50 +0530
> Use kmemdup when some other buffer is immediately copied into allocated
> region. It replaces call to allocation followed by memcpy, by a single
> call to kmemdup.
>
> Signed-off-by: Muhammad Falak R Wani
Applied.
--
To unsubs
ugging logs?)
I remember a problem with the XCHI controller on an amd (x86) motherboard I
have.
What you are seeing might be the same.
Basically it only processed one entry from the command ring each time the
doorbell was rung.
I don't remember seeing a patch go past that would fix it, and I didn't
actually write one.
It might be worth trying re-ringing the command ring doorbell in the
command completion code.
David
On 05/09/2016 06:46 PM, David Lechner wrote:
v5 changes: renamed "usbphy" to "usb_phy" or "usb-phy" as appropriate
David Lechner (5):
ARM: davinci: da8xx: add usb phy clocks
ARM: davinci: da8xx: Add CFGCHIP syscon platform declaration.
ARM: davinc
bounds (&foo - 1) can fault.
The most recent hardware that does that is probably a vax.
Although I believe amd64 will fault if you load a suitable invalid
value (not a valid pointer) into the fs/gs offset registers.
David
From: Heinrich Schuchardt
Date: Wed, 18 May 2016 20:40:51 +0200
> If !count is true, count < 4 is also true.
>
> Signed-off-by: Heinrich Schuchardt
Applied.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majord
From: Hayes Wang
Date: Wed, 8 Jun 2016 14:52:33 +0800
> Replace netdev_alloc_skb_ip_align() with napi_alloc_skb() which can save
> several CPU cycles by avoiding having to disable and re-enable IRQs.
>
> Signed-off-by: Hayes Wang
Applied.
--
To unsubscribe from this list: send the line "unsubs
From: Mario Limonciello
Date: Tue, 7 Jun 2016 13:22:37 -0500
> The RTL8153-AD supports a persistent system specific MAC address.
> This means a device plugged into two different systems with host side
> support will show different (but persistent) MAC addresses.
>
> This information for the sys
From: Andrew Lunn
Date: Sat, 11 Jun 2016 17:39:21 +0200
> What is still open is do we want to accept it at all? Do we accept the
> concept of putting the same MAC address on multiple interfaces at
> hotplug time? Do we trust BIOS vendors to not keep changing DSDT
> property name, since it is not
se POLLHUP for device disconnect type errors
and leave POLLERR for serious things (like bad fd numbers).
David
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
From: Pali Rohár
Date: Tue, 14 Jun 2016 18:47:36 +0200
> You have never seen two ethernet cards with same MAC addresses? Right I
> have not seen two USB, but there is non zero chance that could happen.
It would be an error scenerio, and something to be avoided.
It is a valid and correct assum
From: Hayes Wang
Date: Mon, 13 Jun 2016 17:49:35 +0800
> These patches are for adjusting the code about PHY and setting speed.
Series applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info
From: Hayes Wang
Date: Thu, 16 Jun 2016 10:55:16 +0800
> These patches fix some known issues.
Series applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/major
From: Hayes Wang
Date: Thu, 16 Jun 2016 14:08:29 +0800
> In set_speed(), BMCR_RESET would be set when the flag of PHY_RESET
> is set. Use BMCR_RESET to replace testing the flag of PHY_RESET.
>
> Signed-off-by: Hayes Wang
Applied, thanks.
--
To unsubscribe from this list: send the line "unsubsc
On 06/22/2016 12:57 AM, Kishon Vijay Abraham I wrote:
Hi,
On Tuesday 10 May 2016 05:09 AM, David Lechner wrote:
The initial use for this is for PHYs that have a mode related to USB OTG.
There are several SoCs (e.g. TI OMAP and DA8xx) that have a mode setting
in the USB PHY to override OTG VBUS
From 2261f0ea15690623dcefd71b8aaaea6089b16468 Mon Sep 17 00:00:00 2001
From: David Lechner
Date: Wed, 16 Mar 2016 14:16:08 -0500
Subject: [PATCH] phy: da8xx-usb: new driver for DA8xx SoC USB PHY
This is a new phy driver for the SoC USB controllers on the TI DA8xx
family of microcontrollers. The
From b0ae5eeba849b49f82980218a374c6d3f06487b8 Mon Sep 17 00:00:00 2001
From: David Lechner
Date: Thu, 24 Mar 2016 01:38:54 -0500
Subject: [PATCH] ARM: davinci: da8xx: Add CFGCHIP syscon platform
declaration.
The CFGCHIP registers are used by a number of devices, so using a syscon
device to
From 53c9b38e0a7860e51ce7bdfe6d4f1d83cf2394a5 Mon Sep 17 00:00:00 2001
From: David Lechner
Date: Wed, 16 Mar 2016 14:25:23 -0500
Subject: [PATCH] ARM: davinci: da8xx: Add USB PHY platform declaration
There is now a proper phy driver for the DA8xx SoC USB PHY. This adds the
platform device
On 05/25/2016 06:15 AM, Sekhar Nori wrote:
On Tuesday 10 May 2016 10:14 PM, David Lechner wrote:
On 05/10/2016 06:26 AM, Sergei Shtylyov wrote:
On 5/10/2016 2:46 AM, David Lechner wrote:
The CFGCHIP registers are used by a number of devices, so using a syscon
device to share them. The first
This is a new phy driver for the SoC USB controllers on the TI DA8xx
family of microcontrollers. The USB 1.1 PHY is just a simple on/off.
The USB 2.0 PHY also allows overriding the VBUS and ID pins.
Signed-off-by: David Lechner
Reviewed-by: Sekhar Nori
---
Just one small change here. Changed
Re: USB needing fixed, I'm not sure how to do this and I won't have time
for at least the next 2 or 3 months to do anything about it. The problem
is that the MUSB can't detect the ID pin. As a workaround, it is
detecting the VBUS state and using that to determine the ID pin state.
So, when you at
#x27;t mention the zilog scc) that
report 'abort/break' asynchronously from the data stream.
Correctly receiving and
is almost impossible.
David
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel
From: Hayes Wang
Date: Thu, 30 Jun 2016 15:33:35 +0800
> LINK_OFF_WAKE_EN should be cleared after autoresume, otherwise after
> system suspend, the system would wake up when linking off occurs.
>
> Signed-off-by: Hayes Wang
Applied, thanks.
--
To unsubscribe from this list: send the line "unsu
From: Jean-Christophe PLAGNIOL-VILLARD
Date: Thu, 22 Nov 2012 08:35:17 +0100
> Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD
Applied to net-next.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info
From: Joe Perches
Date: Sat, 24 Nov 2012 03:27:49 -0800
> Avoid any possible message logging interleaving by adding
> missing newlines.
>
> Align arguments.
>
> Signed-off-by: Joe Perches
Applied.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message
From: Bjørn Mork
Date: Sun, 25 Nov 2012 17:03:59 +0100
> The Huawei E173 is a QMI/wwan device which normally appear
> as 12d1:1436 in Linux. The descriptors displayed in that
> mode will be picked up by cdc_ether. But the modem has
> another mode with a different device ID and a slightly
> diffe
there? Any help would be very appreciated.
Many thanks,
David
P.S. Below is the output when I connect the unit to the CentOS machine
and the contents of the
http://www.kernel.org/doc/Documentation/usb/usb-serial.txt file.
Dec 12 14:42:40 solo kernel: usb 1-2: new full speed USB device number
2 us
driver is no longer exist. Thanks!
Acked-by: David Chang
> Signed-off-by: Ilija Hadzic
> ---
> drivers/staging/usbip/userspace/Makefile.am | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/usbip/userspace/Makefile.am
> b/drivers/st
return -1;
> + if (!(s.st_mode & S_IFDIR))
> + return -1;
> + } else
> + return -1;
> + }
>
> snprintf(path, PATH_MAX, VHCI_STATE_PATH"/port%d", rhport);
>
The
From: Bjørn Mork
Date: Wed, 19 Dec 2012 15:15:51 +0100
> The driver description files gives these names to the vendor specific
> functions on this modem:
>
> diag: VID_19D2&PID_0284&MI_00
> nmea: VID_19D2&PID_0284&MI_01
> at: VID_19D2&PID_0284&MI_02
> mdm: VID_19D2&PID_0284&MI_03
> net:
From: Bjørn Mork
Date: Fri, 28 Dec 2012 17:30:55 +0100
> also known as Alcatel One Touch L100V LTE
>
> The driver description files gives these names to the vendor specific
> functions on this modem:
>
> Application1: VID_1BBB&PID_011E&MI_00
> Application2: VID_1BBB&PID_011E&MI_01
> Modem:
> version 3.0+ supports usbip? Or do i have to switch back to older
> kernel versions?
Yes, the usbip is working fine with 3.0+ kernel.
The userspace tools is located at $kernel-SOURCE/driver/staging/usbip/userspace.
Reference: http://kernel.org/doc/readme/drivers-staging-usbip-userspace-
From: Ming Lei
Date: Fri, 11 Jan 2013 10:45:38 +0800
> Cc netdev and usb lists.
That doesn't work for patches, sorry. It will have to be submitted
freshly and cleanly to the appropriate lists, not as a quoted reply.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the
From: Wei Shuai
Date: Sat, 12 Jan 2013 19:34:39 +0800
> Infineon(now Intel) HSPA Modem platform NCM cannot support ARP. so I
> introduce a flag CDC_NCM_DRIVER_DATA_NOARP which is defined in
> driver_info:data. so later on, if more such buggy devices are found,
> they could use same flag to handle
From: Dan Williams
Date: Mon, 14 Jan 2013 11:19:13 -0600
> On Sat, 2013-01-12 at 15:35 -0800, David Miller wrote:
>> From: Wei Shuai
>> Date: Sat, 12 Jan 2013 19:34:39 +0800
>>
>> > Infineon(now Intel) HSPA Modem platform NCM cannot support A
From: Tushar Behera
Date: Tue, 15 Jan 2013 11:09:01 +0530
> commit 24b1042c4eb2 ("usbnet: dm9601: apply introduced usb command
> APIs") removes the distiction between DM_WRITE_REG and DM_WRITE_REGS
> command. The distiction is reintroduced to the driver so that the
> functionality of the driver r
From: Bjørn Mork
Date: Tue, 15 Jan 2013 10:19:50 +0100
> The driver description files gives these names to the vendor specific
> functions on this modem:
>
> Diagnostics VID_2357&PID_0201&MI_00
> NMEAVID_2357&PID_0201&MI_01
> Modem VID_2357&PID_0201&MI_03
> Networkcard VID_2357
From: Bjørn Mork
Date: Tue, 15 Jan 2013 09:34:07 +0100
> The main problem is that these devices don't support ethernet. They
> support IP (v4 and _maybe_ v6) with an ethernet header. Many of them
> will do ARP (and IPv6 ND) as well to complete the picture, but some of
> them don't and that's wh
From: Lucas Stach
Date: Wed, 16 Jan 2013 15:24:06 +0100
> The device comes up with a MAC address of all zeros. We need to read the
> initial device MAC from EEPROM so it can be set properly later.
>
> Signed-off-by: Lucas Stach
Applied.
--
To unsubscribe from this list: send the line "unsubscr
From: Lucas Stach
Date: Wed, 16 Jan 2013 15:24:07 +0100
> ASIX AX88772B started to pack data even more tightly. Packets and the ASIX
> packet
> header may now cross URB boundaries. To handle this we have to introduce
> some state between individual calls to asix_rx_fixup().
>
> Signed-off-by: L
From: Freddy Xin
Date: Thu, 17 Jan 2013 17:32:54 +0800
> +struct ax88179_rx_pkt_header {
> +
> + u8 l4_csum_err:1,
Get rid of such extraneous empty lines. They do not add clarity,
rather they just take up space.
> + ret = fn(dev, cmd, USB_DIR_IN | USB_TYPE_VENDOR |
> +
Why did you submit this _4_ times?
I'm deleteing everything, I'm not even going to try and guess why
you submitted this so many times and what might be different between
each copy.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.k
From: Bjørn Mork
Date: Fri, 18 Jan 2013 15:26:34 +0100
> The driver description files gives these names to the vendor specific
> functions on this modem:
>
> Diag VID_19D2&PID_0265&MI_00
> NMEA VID_19D2&PID_0265&MI_01
> AT cmd VID_19D2&PID_0265&MI_02
> Modem VID_19D2&PID_0265&MI_03
> N
When any patch is discarded, the whole series is tossed.
Therefore you must resubmit the entire series, not just one
part of it.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel
From: Wei Shuai
Date: Mon, 21 Jan 2013 10:20:22 +0800
> The main problem is that these devices don't support ethernet.
He's saying your comment is referring to the wrong thing,
rather than saying anything against what your change is
doing.
Read his feedback carefully:
>>> +/* Same as wwan_info
From: Ming Lei
Date: Sat, 19 Jan 2013 19:32:01 +0800
> This patch calls device_set_wakeup_enable() inside set_wol
> callback, so that turning on WOL from user mode utility
> can make the 'wakeup' of pegasus device to be enabled, then
> remote wakeup may be enabled before putting into sleep.
>
>
From: Bjørn Mork
Date: Mon, 21 Jan 2013 16:50:37 +0100
> The 2 first patches in this series are required to make the Sierra
> Wireless MC7710 card work in MBIM mode. They may also be
> required for other Qualcomm firmware based MBIM devices.
>
> Patch #1 was previously posted as a standalone pa
From: Wei Shuai
Date: Tue, 22 Jan 2013 00:00:31 +0800
> We do have some USB net devices, which cannot do ARP.
> so we can introduce a new flag FLAG_NOARP, then client drivers
> can easily handle this kind of devices
>
> Signed-off-by: Wei Shuai
Applied.
--
To unsubscribe from this list: send
From: Wei Shuai
Date: Tue, 22 Jan 2013 00:00:32 +0800
> Infineon(now Intel) HSPA Modem platform NCM cannot support ARP.
> we can define a new common structure wwan_noarp_info.
> Then more similiar NO ARP devices can be handled easily
>
> Signed-off-by: Wei Shuai
Applied.
--
To unsubscribe from
From: Freddy Xin
Date: Wed, 23 Jan 2013 10:32:17 +0800
> Fixed coding style errors.
There are still many style issues remaining, you have a lot more
work to do, for example:
> + return fn(dev, cmd, USB_DIR_OUT | USB_TYPE_VENDOR | USB_RECIP_DEVICE,
> +value, index, data, size);
>
From: Bjørn Mork
Date: Wed, 23 Jan 2013 11:57:02 +0100
> Reverting 328d7b8 and instead adding an exception for the
> Sierra Wireless MC7710.
>
> commit 328d7b8 (net: cdc_mbim: send ZLP after max sized NTBs)
> added a workaround for an issue observed on one specific device.
> Concerns were raised
From: David Moore
When the xHCI driver is not available, actively switch the ports to EHCI
mode since some BIOSes leave them in xHCI mode where they would
otherwise appear dead.
Signed-off-by: David Moore
---
drivers/usb/host/pci-quirks.c | 1 +
1 file changed, 1 insertion(+)
diff --git a
if (PTR_ERR(da8xx_ohci->usb11_phy) != -EPROBE_DEFER)
dev_err(&pdev->dev, "Failed to get phy.\n");
- return PTR_ERR(usb11_phy);
+ error = PTR_ERR(da8xx_ohci->usb11_phy);
+ goto err;
}
same here
...
Tested-by: D
On 11/14/2016 08:41 AM, ahas...@baylibre.com wrote:
Using a regulator to handle VBUS will eliminate the need for
platform data and callbacks, and make the driver more generic
allowing different types of regulators to handle VBUS.
The regulator equivalents to the platform callbacks are:
set_p
On 11/19/2016 09:31 PM, David Lechner wrote:
On 11/14/2016 08:41 AM, ahas...@baylibre.com wrote:
+ocic_mask |= 1;
I thought that a previous patch got rid of all globals. Why is ocic_mask
still a global variable?
I suppose if I read the commit message, I will know the answer
On 11/07/2016 02:39 PM, Axel Haslam wrote:
This adds the ohci device node for the da850 soc.
It also enables it for the omapl138 hawk board.
Signed-off-by: Axel Haslam
---
arch/arm/boot/dts/da850-lcdk.dts | 8
arch/arm/boot/dts/da850.dtsi | 8
2 files changed, 16 insertio
On 11/21/2016 04:22 AM, Axel Haslam wrote:
Hi David,
Thanks for the review,
You're welcome.
@@ -160,15 +212,41 @@ static void ohci_da8xx_ocic_handler(struct
da8xx_ohci_root_hub *hub,
hub->set_power(port, 0);
}
+static int ohci_da8xx_regulator_event(struct notifi
On 11/21/2016 10:30 AM, Axel Haslam wrote:
Using a regulator to handle VBUS will eliminate the need for
platform data and callbacks, and make the driver more generic
allowing different types of regulators to handle VBUS.
The regulator equivalents to the platform callbacks are:
set_power ->
pointer. This will be moved
on a later patch.
Signed-off-by: Axel Haslam
---
Looks good to me (other than the spelling error above).
Tested-by: David Lechner
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kerne
On 11/22/2016 02:46 PM, Axel Haslam wrote:
On Tue, Nov 22, 2016 at 9:37 PM, David Lechner wrote:
On 11/21/2016 10:30 AM, Axel Haslam wrote:
Using a regulator to handle VBUS will eliminate the need for
platform data and callbacks, and make the driver more generic
allowing different types of
From: Hayes Wang
Date: Thu, 24 Nov 2016 13:26:55 +
> I don't think the garbage results from our driver or device.
This is my impression with what has been presented so far as well.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@v
From: Mark Lord
Date: Thu, 24 Nov 2016 07:31:17 -0500
> Any way we look at it though, the chip/driver are simply unreliable,
> and relying upon hardware checksums (which fail due to the driver
> looking at garbage rather than the checksum bits) leads to data
> corruption.
If the cpu/DMA implemen
From: Mark Lord
Date: Thu, 24 Nov 2016 11:43:53 -0500
> So even if this were a platform memory coherency issue, one should
> still never see ASCII data at the beginning of an rx buffer.
I'm not so convinced, since this is the kind of random corruption one
would expect to see when dealing with vi
From: Mark Lord
Date: Thu, 24 Nov 2016 12:00:15 -0500
> It seems I am being overly helpful here.
Either you want to cry or you want to keep helping us track down
this problem. It is your choice, and your choice alone.
Please do not pretend otherwise, everyone else in this thread is
operating w
From: Mark Lord
Date: Fri, 25 Nov 2016 07:49:35 -0500
> On 16-11-25 04:53 AM, Greg KH wrote:
>> On Thu, Nov 24, 2016 at 10:49:33PM -0500, Mark Lord wrote:
>>> There is no possibility for them to be used for anything other than
>>> USB receive buffers, for this driver only. Nothing in the driver
1 - 100 of 2170 matches
Mail list logo
