Individual controller driver has different requirement for wakeup
setting, so move it from core to itself. In order to align with
current etting the default wakeup setting is enabled (except for
chipidea host).
Pass compile test with below commands:
make O=outout/all allmodconfig
Hi
Here are dmesg's with old_scheme_first=1 and where it took about 20s
for usb-storage to start using this device. Is there a way I can
enable debugs from usb-storage to see what it is doing in that 20s
gap. The device in question is at usb1-3 (sdb), manufactured by SMART.
Thank you.
[
Thanks for the quick patch..I will test it.
On Wed, Oct 30, 2013 at 10:02 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Wed, 30 Oct 2013, Alan Stern wrote:
I think you have found a bug in the dwc3 driver.
At this point, because the IGNORE_BULK_OUT bit is set, g_mass_storage
issues a
Update device tree bindings for DWC3 controller and
USB 3.0 phy present on Exynos 5250 SoC, to start using
the phy driver based on generic phy framework.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
arch/arm/boot/dts/exynos5250.dtsi | 17 ++---
1 files changed, 6
Add device tree nodes for DWC3 controller present on
Exynos 5420 SoC, to enable support for USB 3.0.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
arch/arm/boot/dts/exynos5420.dtsi | 38 +++-
1 files changed, 36 insertions(+), 2 deletions(-)
diff
Add device tree nodes for USB 3.0 PHY present alongwith
USB 3.0 controller Exynos 5420 SoC. This phy driver is
based on generic phy framework.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
arch/arm/boot/dts/exynos5420.dtsi | 16
1 files changed, 16 insertions(+), 0
Add a new driver for the USB 3.0 PHY on Exynos5 series of SoCs.
The new driver uses the generic PHY framework and will interact
with DWC3 controller present on Exynos5 series of SoCs.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
.../devicetree/bindings/phy/samsung-phy.txt|
Adding a phy driver for USB 3.0 PHY controller present on Exynos5
series of SoCs alongwith DWC3 controller for USB 3.0 operations.
This driver is inline with Kamil's USB 2.0 phy driver. [1]
Few functions used to translate ref clock rate are common to
Kamil's changes. So we can figure out how to
Thomas Schäfer tschae...@t-online.de writes:
Bjørn Mork bj...@mork.no writes:
That was probably a bit too brief. What I meant was: Try changing the
last argument to ipv6_stub-ndisc_send_na() from false to true and
see if that makes any difference.
It made a difference. It works.
For
On Thu, Oct 24, 2013 at 12:35:35AM -0700, Dan Williams wrote:
Platform firmware identifies ports that share a connector. This
information is relevant for port power control since we do not want a
device to reconnect on its peer port in a connector when pm has decided
to power-off its
Du, ChangbinX changbinx...@intel.com writes:
From: Bjørn Mork [mailto:bj...@mork.no]
Sent: Tuesday, October 29, 2013 4:41 PM
To: Du, ChangbinX
Cc: oli...@neukum.org; linux-usb@vger.kernel.org; net...@vger.kernel.org;
linux-ker...@vger.kernel.org
Subject: Re: [PATCH] net/cdc_ncm: fix null
On Wed, Oct 30, 2013 at 11:07:31AM -0700, Greg KH wrote:
Johan has been conned^Wgracious in accepting the maintainership of the
USB serial drivers, especially as he's been doing all of the real work
for the past few years.
At the same time, remove a bunch of old entries for USB serial
On Wed, Oct 30, 2013 at 11:19:12AM -0400, Alan Stern wrote:
On Wed, 30 Oct 2013, Peter Chen wrote:
Individual controller driver has different requirement for wakeup
setting, so move it from core to itself. In order to align with
current etting the default wakeup setting is enabled (except
* Dirk Gouders | 2013-10-30 15:26:30 [+0100]:
Hi Sebastian, Yann, all,
Hi Dirk,
below is a patch that prevents choice_values to appear in the list if
they depend on 'm' symbols and the choice symbol is set to 'y'. I would
be glad if you could have a look at it.
I applied this patch (and
On Wed, Oct 30, 2013 at 11:14:34PM +0100, Frank Schäfer wrote:
Hmm... try to replace the whole pl2303.c from 3.12 with the one from 3.11.
If it makes no difference, it's not a pl2303 issue.
I did that and the 3.11 pl2303.c works (whereas 3.12 doesn't).
Can you tell me why do we even want to
Hi Russell,
Em Mon, 30 Sep 2013 13:57:47 +0200
Hans Verkuil hverk...@xs4all.nl escreveu:
On 09/19/2013 11:44 PM, Russell King wrote:
Replace the following sequence:
dma_set_mask(dev, mask);
dma_set_coherent_mask(dev, mask);
with a call to the new helper
On Thu, Oct 31, 2013 at 01:09:55PM +0200, Mika Westerberg wrote:
On Wed, Oct 30, 2013 at 11:14:34PM +0100, Frank Schäfer wrote:
Hmm... try to replace the whole pl2303.c from 3.12 with the one from 3.11.
If it makes no difference, it's not a pl2303 issue.
I did that and the 3.11 pl2303.c
Am 31.10.2013 12:09, schrieb Mika Westerberg:
On Wed, Oct 30, 2013 at 11:14:34PM +0100, Frank Schäfer wrote:
Hmm... try to replace the whole pl2303.c from 3.12 with the one from 3.11.
If it makes no difference, it's not a pl2303 issue.
I did that and the 3.11 pl2303.c works (whereas 3.12
Am 31.10.2013 13:03, schrieb Mika Westerberg:
On Thu, Oct 31, 2013 at 01:09:55PM +0200, Mika Westerberg wrote:
On Wed, Oct 30, 2013 at 11:14:34PM +0100, Frank Schäfer wrote:
Hmm... try to replace the whole pl2303.c from 3.12 with the one from 3.11.
If it makes no difference, it's not a pl2303
On 10/31/2013 03:36 AM, Valentine wrote:
On 10/30/2013 06:12 PM, Greg KH wrote:
On Wed, Oct 30, 2013 at 01:56:25PM +0400, Valentine wrote:
On 10/30/2013 03:57 AM, Greg KH wrote:
On Tue, Oct 29, 2013 at 09:19:09PM +0400, Valentine wrote:
On 10/29/2013 09:00 PM, Laurent Pinchart wrote:
Hi
On Thu, Oct 31, 2013 at 01:02:56PM +0100, Frank Schäfer wrote:
2) comment out the following line at the end of
pl2303_baudrate_encode_divisor_HXD():
baud = 1200 * 32 / ((1 buf[1]) * buf[0]);
This seems to fix the problem :)
Once the line is commented out, the serial console works fine
Only receive TD can have a transfer length less than the transfer size,
so rename COMP_SHORT_TX to COMP_SHORT_RX, XHCI_TRUST_TX_LENGTH to
XHCI_TRUST_RX_LENGTH.
handle_tx_event() is called for both receive and transmit completions
so rename to handle_data_event().
In process_bulk_intr_td():
-
On Thu, 31 Oct 2013, David Laight wrote:
Only receive TD can have a transfer length less than the transfer size,
Without commenting on the patch itself, let me point out that this
statement is wrong. An OUT transfer can terminate early for several
reasons. They are all error conditions,
On Thu, 31 Oct 2013, Pratyush Anand wrote:
This is fine.
But I do not see any way to unwedge ep0. dwc3_gadget_ep0_set_halt
ignores *value*
argument and will not handle a gadget driver's clear halt status request.
However, I do no see any gadget driver wedging ep0, so may be it will not
On Thu, Oct 31, 2013 at 09:46:40AM -0200, Mauro Carvalho Chehab wrote:
Hi Russell,
Em Mon, 30 Sep 2013 13:57:47 +0200
Hans Verkuil hverk...@xs4all.nl escreveu:
On 09/19/2013 11:44 PM, Russell King wrote:
Replace the following sequence:
dma_set_mask(dev, mask);
On Wed, Oct 30, 2013 at 10:44:30PM +0100, Johannes Stezenbach wrote:
On Wed, Oct 30, 2013 at 12:54:15PM -0500, Felipe Balbi wrote:
On Wed, Oct 30, 2013 at 03:17:46PM +0100, Johannes Stezenbach wrote:
I'm testing dwc3 with g_zero and noticed that errors
seem to stick even after
Convert TRB_CYCLE to LE when initialising the ring entries.
---
drivers/usb/host/xhci-mem.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/host/xhci-mem.c b/drivers/usb/host/xhci-mem.c
index 83bcd13..79cdcc2 100644
--- a/drivers/usb/host/xhci-mem.c
+++
Hi,
On Thu, Oct 31, 2013 at 04:02:20PM +0100, Johannes Stezenbach wrote:
On Wed, Oct 30, 2013 at 10:44:30PM +0100, Johannes Stezenbach wrote:
On Wed, Oct 30, 2013 at 12:54:15PM -0500, Felipe Balbi wrote:
On Wed, Oct 30, 2013 at 03:17:46PM +0100, Johannes Stezenbach wrote:
I'm testing
Hi,
On Thu, Oct 31, 2013 at 01:35:45PM +0100, Krzysztof Opasiak wrote:
Dear List,
After introduction of ConfigFS composite gadget, there appeared
an gap
in the user space. I mean that without this file system, creation
of
gadget is as simple as:
$ modprobe
Hello,
We are using a linux device as a iPad MFI peripheral. In the current
scenario, the iPad is the USB device, and linux system is the host.
With Apple MFI in this configuration, the only protocol available to
transfer data is HID. We're noticing that when we transfer a lot of
data over HID,
On Wed, 30 Oct 2013, Prasad Koya wrote:
Hi
Here are dmesg's with old_scheme_first=1 and where it took about 20s
for usb-storage to start using this device. Is there a way I can
enable debugs from usb-storage to see what it is doing in that 20s
gap. The device in question is at usb1-3
On Thu, Oct 31, 2013 at 11:24:05AM -0400, Cliff Brake wrote:
Hello,
We are using a linux device as a iPad MFI peripheral. In the current
scenario, the iPad is the USB device, and linux system is the host.
With Apple MFI in this configuration, the only protocol available to
transfer data is
On Thu, Oct 31, 2013 at 11:56 AM, Greg KH gre...@linuxfoundation.org wrote:
On Thu, Oct 31, 2013 at 11:24:05AM -0400, Cliff Brake wrote:
I'd focus on the host controller driver, it would be the one that is
probably the issue (you can test this with a PC running Linux and a
different host
On Thu, Oct 31, 2013 at 12:43 PM, Valentine
valentine.bars...@cogentembedded.com wrote:
Please, let me know if you see better options.
How about disregarding the whole PCI aspect? I mean, yes, those are
PCI busses, but they are internal, with a fixed set of devices
attached, and as far as I can
Code was recently added to the xhci driver to dynamically add extra ring
segments if there is insufficient space for all the fragments of the
URB being sent.
ISTM that it would be better to just queue the URB (on the ring)
and process it when space becomes available.
This wouldn't solve the
On 10/31/2013 08:12 PM, Ulrich Hecht wrote:
On Thu, Oct 31, 2013 at 12:43 PM, Valentine
valentine.bars...@cogentembedded.com wrote:
Please, let me know if you see better options.
How about disregarding the whole PCI aspect? I mean, yes, those are
PCI busses, but they are internal, with a
On Thu, 31 Oct 2013, Valentine wrote:
Do you mean to change usb_hcd_pci_probe() to return -EPROBE_DEFER if the
phy is not ready?
Or should I defer the whole PCI subsystem initialization (pci_common_int)?
Greg,
the reason I ask is that it doesn't seem that simple to me.
Here's some
I tried usbmon before forcing crash:
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 5
B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0002 Rev= 2.06
S: Manufacturer=Linux 2.6.32.28 ehci_hcd
S:
On Thu, Oct 31, 2013 at 12:09:54PM -0400, Cliff Brake wrote:
On Thu, Oct 31, 2013 at 11:56 AM, Greg KH gre...@linuxfoundation.org wrote:
On Thu, Oct 31, 2013 at 11:24:05AM -0400, Cliff Brake wrote:
I'd focus on the host controller driver, it would be the one that is
probably the issue
On Thu, Oct 31, 2013 at 1:54 PM, Greg KH gre...@linuxfoundation.org wrote:
Ick, that's not good. This sounds like a driver issue, if you can find
out where interrupts are being held for so long, hopefully a fix can be
found and resolved. It's good that 3.11 is better, but ideally a real
fix
On Thu, 31 Oct 2013, Prasad Koya wrote:
I tried usbmon before forcing crash:
As this USB is on bus 1, I tried below:
cat /sys/kernel/debug/usb/usbmon/1u
I didn't see anything till I copied a file or did some activity on it.
While cat'ing above, I copied a file to that flash with dd in
On Thu, 31 Oct 2013, Cliff Brake wrote:
On Thu, Oct 31, 2013 at 1:54 PM, Greg KH gre...@linuxfoundation.org wrote:
Ick, that's not good. This sounds like a driver issue, if you can find
out where interrupts are being held for so long, hopefully a fix can be
found and resolved. It's
On Thu, Oct 31, 2013 at 2:25 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Thu, 31 Oct 2013, Cliff Brake wrote:
On Thu, Oct 31, 2013 at 1:54 PM, Greg KH gre...@linuxfoundation.org wrote:
Ick, that's not good. This sounds like a driver issue, if you can find
out where interrupts are
Am 31.10.2013 13:30, schrieb Mika Westerberg:
On Thu, Oct 31, 2013 at 01:02:56PM +0100, Frank Schäfer wrote:
2) comment out the following line at the end of
pl2303_baudrate_encode_divisor_HXD():
baud = 1200 * 32 / ((1 buf[1]) * buf[0]);
This seems to fix the problem :)
Once the line
On 10/30/2013 10:35 AM, Felipe Balbi wrote:
On Wed, Oct 30, 2013 at 10:06:18AM -0700, David Cohen wrote:
DWC3 requires epout to have buffer size aligned to MaxPacketSize value.
This patch adds necessary quirk for it.
Signed-off-by: David Cohen david.a.co...@linux.intel.com
---
On Thu, Oct 31, 2013 at 09:26:06PM +0100, Johan Hovold wrote:
On Thu, Oct 31, 2013 at 7:45 PM, Frank Schäfer wrote:
Am 31.10.2013 13:30, schrieb Mika Westerberg:
On Thu, Oct 31, 2013 at 01:02:56PM +0100, Frank Schäfer wrote:
2) comment out the following line at the end of
On Thu, Oct 31, 2013 at 09:56:25PM +0100, Johan Hovold wrote:
On Thu, Oct 31, 2013 at 09:26:06PM +0100, Johan Hovold wrote:
On Thu, Oct 31, 2013 at 7:45 PM, Frank Schäfer wrote:
Am 31.10.2013 13:30, schrieb Mika Westerberg:
On Thu, Oct 31, 2013 at 01:02:56PM +0100, Frank Schäfer wrote:
On Thu, Oct 31, 2013 at 12:58:51PM -0700, David Cohen wrote:
On 10/30/2013 10:35 AM, Felipe Balbi wrote:
On Wed, Oct 30, 2013 at 10:06:18AM -0700, David Cohen wrote:
DWC3 requires epout to have buffer size aligned to MaxPacketSize value.
This patch adds necessary quirk for it.
On Wed, 30 Oct 2013 00:07:22 +0800 Ming Lei ming@canonical.com wrote:
sg_copy_buffer() can't meet demand for some drrivers(such usb
mass storage), so we have to use the sg_miter_* APIs to access
sg buffer, then need export sg_miter_skip() for these drivers.
The API is needed for
Dirk, All,
On 2013-10-30 15:26 +0100, Dirk Gouders spake thusly:
Dirk Gouders d...@gouders.net writes:
[--SNIP--]
below is a patch that prevents choice_values to appear in the list if
they depend on 'm' symbols and the choice symbol is set to 'y'. I would
be glad if you could have a look at
On Thu, Oct 31, 2013 at 02:03:22PM -0700, Greg KH wrote:
On Thu, Oct 31, 2013 at 09:56:25PM +0100, Johan Hovold wrote:
On Thu, Oct 31, 2013 at 09:26:06PM +0100, Johan Hovold wrote:
On Thu, Oct 31, 2013 at 7:45 PM, Frank Schäfer wrote:
Am 31.10.2013 13:30, schrieb Mika Westerberg:
On
Hi Andrew,
Thank you for the comment.
On Fri, Nov 1, 2013 at 5:47 AM, Andrew Morton a...@linux-foundation.org wrote:
Looks OK to me. Please include this in whatever tree is used to merge
[PATCH 2/2] USB: storage: use sg_miter_* APIs to access scsi buffer.
Greg and Alan, would you mind
52 matches
Mail list logo
