Hello Manjunathappa
On 11.10.2012 07:42, Manjunathappa, Prakash wrote:
Hi,
On Mon, Oct 08, 2012 at 18:47:07, Constantine Shulyupin wrote:
From: Constantine Shulyupinco...@makelinux.com
Remove USB configuration in arch/arm/mach-davinci/usb.c accordingly
CONFIG_USB_MUSB_OTG
Henrik Rydberg wrote:
What is the programming cable and software that uses it?
The programmer is impact, using libusbx-1.0.14-1.
Do you know for a fact that your version calls libusb-1.0? Did you
establish this with e.g. strace? ISE 11.1 impact uses only libusb.so,
ie. libusb-0.1.
Depending
Xiaofan Chen wrote:
On Thu, Oct 11, 2012 at 2:50 PM, Peter Stuge pe...@stuge.se wrote:
But it isn't certain that is is involved at all. If your impact
version uses libusb.so like in ISE 11.1 then it will not be. One way
to test is by trying to generate a libusb debug log. See
On Wed, Oct 10, 2012 at 03:07:30PM -0400, Alan Stern wrote:
In preparation for splitting the ehci-hcd driver into a core library
and separate platform-specific driver modules, this patch (as1616)
moves the console logging macros from ehci-dbg.c to ehci.h, where they
will be available to the
On Wed, Oct 10, 2012 at 03:07:39PM -0400, Alan Stern wrote:
In preparation for splitting the ehci-hcd driver into a core library
and separate platform-specific driver modules, this patch (as1617)
changes the way ehci_read_frame_index() is handled.
Since the same core library will have to
On Wed, Oct 10, 2012 at 03:07:46PM -0400, Alan Stern wrote:
In preparation for splitting the ehci-hcd driver into a core library
and separate platform-specific driver modules, this patch (as1618)
moves ehci_update_device() from a couple of platform-specific source
files into ehci-lpm.c. This
On Wed, Oct 10, 2012 at 10:58:16AM -0700, Sarah Sharp wrote:
On Wed, Oct 10, 2012 at 07:35:48PM +0530, Vikas C Sajjan wrote:
From: Vikas Sajjan vikas.saj...@linaro.org
Adding the suspend and resume functionality for the XHCI driver
Signed-off-by: Abhilash Kesavan a.kesa...@samsung.com
On Thursday 11 October 2012 11:18:22 Ming Lei wrote:
On Wed, Oct 10, 2012 at 1:51 PM, Oliver Neukum oneu...@suse.de wrote:
No, the problem is autoresume.
Suppose we have a device with two interface. Interface A be usbnet;
interface B
something you page on. Now consider that you can
Hi,
On Wed, Oct 10, 2012 at 07:35:49PM +0530, Vikas C Sajjan wrote:
From: Vikas Sajjan vikas.saj...@linaro.org
Adding the suspend and resume functionality to exynos dwc3 driver
Signed-off-by: Abhilash Kesavan a.kesa...@samsung.com
Signed-off-by: Vikas C Sajjan vikas.saj...@linaro.org
CC:
On Wed, Oct 10, 2012 at 07:35:46PM +0530, Vikas C Sajjan wrote:
From: Vikas Sajjan vikas.saj...@linaro.org
This patchset adds suspend/resume functionality to dwc3-core layer
and xhci-platform driver. It also adds S2R support to dwc3-exynos
glue layer.
how has this been tested ? For how long
Hi,
On Wed, Oct 10, 2012 at 07:35:47PM +0530, Vikas C Sajjan wrote:
From: Vikas Sajjan vikas.saj...@linaro.org
Adding the suspend and resume funtionality to DWC3 core.
Signed-off-by: Abhilash Kesavan a.kesa...@samsung.com
Signed-off-by: Vikas C Sajjan vikas.saj...@linaro.org
CC: Doug
On Thu, Oct 11, 2012 at 12:11 PM, Oliver Neukum oneu...@suse.de wrote:
On Thursday 11 October 2012 11:18:22 Ming Lei wrote:
Currently scsi disk can only be runtime suspended when the device is not
opened, so are you sure that the paging out above can cause IO on a suspend
usb mass storage
Hi,
On 10/10/2012 10:31 PM, Henrik Rydberg wrote:
Hi Hans, Alan, Greg,
commit 3d97ff63f8997761f12c8fbe8082996c6eeaba1a
Author: Hans de Goede hdego...@redhat.com
Date: Wed Jul 4 09:18:03 2012 +0200
usbdevfs: Use scatter-gather lists for large bulk transfers
breaks an usb programming
Hi all,
I recently found a strange issue on a embedded platform and don't know
how to fix it. Please give me some suggestions.
The platform is ar9331. The issue is if we attach a usb audio device to
the host on ar9331 directly or via a usb 1.1 hub the usb audio works fine,
but if we attach it
On 10/11/2012 12:05 PM, Heiko Schocher wrote:
Hello Manjunathappa
On 11.10.2012 07:42, Manjunathappa, Prakash wrote:
Hi,
On Mon, Oct 08, 2012 at 18:47:07, Constantine Shulyupin wrote:
From: Constantine Shulyupinco...@makelinux.com
Remove USB configuration in arch/arm/mach-davinci/usb.c
Bjørn Mork bj...@mork.no writes:
Oliver Neukum oneu...@suse.de writes:
On Wednesday 10 October 2012 18:34:52 Bjørn Mork wrote:
Signed-off-by: Bjørn Mork bj...@mork.no
---
What do you think about something like this? Does it have to
be more complicated? Somewhat tested, and seems to do the
Hi,
On Thu, Oct 11, 2012 at 02:22:42PM +0530, Vikas Sajjan wrote:
Hi Felipe,
Thanks for the comments, will get back with modifications.
cool, but please avoid top posting ;-)
--
balbi
signature.asc
Description: Digital signature
On Thursday 11 October 2012 16:14:02 Ming Lei wrote:
On Thu, Oct 11, 2012 at 12:11 PM, Oliver Neukum oneu...@suse.de wrote:
On Thursday 11 October 2012 11:18:22 Ming Lei wrote:
Currently scsi disk can only be runtime suspended when the device is not
opened, so are you sure that the paging
On Thu, 2012-10-11 at 04:57 +0900, Greg KH wrote:
The patch looks great, thanks so much for doing this. I'll queue it up
after 3.7-rc1 is released by Linus (which should be in a few days).
No problem. It's pretty cool to be able to contribute.
--
To unsubscribe from this list: send the line
Elric Fu wrote:
It is a usb 1.1 device and works at full speed.
It is a frequent misunderstanding that a device must be 1.1 only
because it does not support high speed. This is not the case.
But the interesting thing is the bcdUSB field of device descriptor
is 0x0200.
It is perfectly legal
On Thursday 11 October 2012 11:05:05 Bjørn Mork wrote:
Bjørn Mork bj...@mork.no writes:
This is harmless because the driver ignores the sequence numbers anyway.
But if the disconnect on reset is typical for NCM devices, then I guess
it does not help much adding pre and post_reset in cdc_ncm.
On Thursday 11 October 2012 11:05:05 Bjørn Mork wrote:
So I guess that demonstrates the issue with pre and post_reset on
devices keeping internal state pretty well: The effect is entirely
device dependent. The device reset behaviour is not known, and we risk
that the device changes some of its
I've tested gadget mode on DM365 without HW changes.
On Thu, Oct 11, 2012 at 10:50 AM, Sekhar Nori nsek...@ti.com wrote:
On 10/11/2012 12:05 PM, Heiko Schocher wrote:
Hello Manjunathappa
On 11.10.2012 07:42, Manjunathappa, Prakash wrote:
Hi,
On Mon, Oct 08, 2012 at 18:47:07, Constantine
Oliver Neukum oneu...@suse.de writes:
On Thursday 11 October 2012 11:05:05 Bjørn Mork wrote:
So I guess that demonstrates the issue with pre and post_reset on
devices keeping internal state pretty well: The effect is entirely
device dependent. The device reset behaviour is not known, and we
On 21/09/12 22:44, Alan Stern wrote:
What is the Razer DeathAdder?
A mouse. (With some extra buttons)
I can't tell much from these logs. A usbmon trace might help more,
although I don't know whether it would be better to trace the bus for
the headset or the bus for the camera. See the
On Thu, Oct 11, 2012 at 5:05 PM, Oliver Neukum oneu...@suse.de wrote:
That depends on whether an API change would be necessary.
Changing the code only when necessary is no problem. But the
API I want to do right from the beginning if that is possible.
For the auto-resume situation, the current
Hi
I have some stange errors on a arm pcm043 with internal usb phy. The log is
attached at the end of the mail. It would be nice if someone could give me a
pointer whats going wrong?. It would also be nice to know where the status
flags which are output by the usb debug messages are
Bjørn Mork bj...@mork.no writes:
[48880.048494] BUG: unable to handle kernel NULL pointer dereference at
0068
[48880.048573] IP: [a06ba879] cdc_ncm_tx_bundle+0x168/0x43b
[cdc_ncm]
This one is because you removed the if (skb == NULL) from the for
loop, but left the skb =
Hi,
This patch set introduces 3 helpers for handling usb read, write
and write_async command, and replaces the low level's implemention
with the generic ones.
This patchset is a cleanup and about 300 lines code can be saved.
Also, the patchset fixes problem of DMA on buffer embedded inside
one
This patch introduces the below 3 usb command helpers:
usbnet_read_cmd / usbnet_write_cmd / usbnet_write_cmd_async
so that each low level driver doesn't need to implement them
by itself, and the dma buffer allocation for usb transfer and
runtime PM things can be handled just in one
Signed-off-by: Ming Lei ming@canonical.com
---
drivers/net/usb/asix_common.c | 117 +
1 file changed, 13 insertions(+), 104 deletions(-)
diff --git a/drivers/net/usb/asix_common.c b/drivers/net/usb/asix_common.c
index 774d9ce..50d1673 100644
---
Signed-off-by: Ming Lei ming@canonical.com
---
drivers/net/usb/cdc_ncm.c | 73 ++---
1 file changed, 23 insertions(+), 50 deletions(-)
diff --git a/drivers/net/usb/cdc_ncm.c b/drivers/net/usb/cdc_ncm.c
index 4cd582a..429a2ad 100644
---
Signed-off-by: Ming Lei ming@canonical.com
---
drivers/net/usb/int51x1.c | 52 +++--
1 file changed, 3 insertions(+), 49 deletions(-)
diff --git a/drivers/net/usb/int51x1.c b/drivers/net/usb/int51x1.c
index 8de6417..ace9e74 100644
---
Signed-off-by: Ming Lei ming@canonical.com
---
drivers/net/usb/mcs7830.c | 85 -
1 file changed, 6 insertions(+), 79 deletions(-)
diff --git a/drivers/net/usb/mcs7830.c b/drivers/net/usb/mcs7830.c
index 03c2d8d..db46a68 100644
---
Signed-off-by: Ming Lei ming@canonical.com
---
drivers/net/usb/net1080.c | 110 +
1 file changed, 30 insertions(+), 80 deletions(-)
diff --git a/drivers/net/usb/net1080.c b/drivers/net/usb/net1080.c
index c062a3e..93e0716 100644
---
Signed-off-by: Ming Lei ming@canonical.com
---
drivers/net/usb/smsc75xx.c | 39 ++-
1 file changed, 14 insertions(+), 25 deletions(-)
diff --git a/drivers/net/usb/smsc75xx.c b/drivers/net/usb/smsc75xx.c
index b77ae76..1baa53a 100644
---
Signed-off-by: Ming Lei ming@canonical.com
---
drivers/net/usb/smsc95xx.c | 115 +++-
1 file changed, 27 insertions(+), 88 deletions(-)
diff --git a/drivers/net/usb/smsc95xx.c b/drivers/net/usb/smsc95xx.c
index 7479a57..1730f75 100644
---
On Thu, 11 Oct 2012, Oliver Neukum wrote:
On Thursday 11 October 2012 11:18:22 Ming Lei wrote:
On Wed, Oct 10, 2012 at 1:51 PM, Oliver Neukum oneu...@suse.de wrote:
No, the problem is autoresume.
Suppose we have a device with two interface. Interface A be usbnet;
interface B
On Fri, 12 Oct 2012, L N Wirz wrote:
Dear Alan,
I found your address on the lkml when I looked for someone who recently
worked on the usb subsystem.
Messages like this should always be CC'ed to the linux-usb mailing
list.
I've encountered a reproducible kernel oops, when I remove a
On Thu, 11 Oct 2012, Elric Fu wrote:
Hi all,
I recently found a strange issue on a embedded platform and don't know
how to fix it. Please give me some suggestions.
The platform is ar9331. The issue is if we attach a usb audio device to
the host on ar9331 directly or via a usb 1.1 hub the
Hi,
while doing some monkey tests on a product we found races in usb audio code when
the device in unplugged from usb (on linus master tree).
This can be reproduced with usb_audio_show_race.diff and CONFIG_DEBUG_SLAB.
With this patch, start a stream :
# arecord -D hw:0 -r 44100 -c 2 -f S16_LE
On Thu, 11 Oct 2012, Gian-Carlo Pascutto wrote:
I noticed that sometimes when booting the USB subsystem already behaves
erratically. For example this morning I'm greeted by:
[ 234.455604] ohci_hcd :00:04.0: urb 8801296fac80 path 4 ep1in
9312 cc 9 -- status -121
[ 234.466567]
On Thu, 11 Oct 2012, Tim Sander wrote:
Hi
I have some stange errors on a arm pcm043 with internal usb phy. The log is
attached at the end of the mail. It would be nice if someone could give me a
pointer whats going wrong?. It would also be nice to know where the status
flags which are
On Thu, 11 Oct 2012, Matthieu CASTET wrote:
Hi,
while doing some monkey tests on a product we found races in usb audio code
when
the device in unplugged from usb (on linus master tree).
This can be reproduced with usb_audio_show_race.diff and CONFIG_DEBUG_SLAB.
With this patch, start a
On 11/10/12 17:19, Alan Stern wrote:
Maybe my hardware/chipset is just crap?
I don't know, maybe. Maybe that's just a bad cable connection (this
includes the possibility of bad connections inside the PC case).
Ouch. I can check a few things, like the USB card reader. It should be
possible
From: Alan Cox a...@linux.intel.com
We nowdays copy the buffer and free fw-data, so make the debug printk use
the right thing.
Signed-off-by: Alan Cox a...@linux.intel.com
---
drivers/net/usb/kaweth.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
From: Constantine Shulyupin co...@makelinux.com
Sets USB PHY clock source to 24 MHz clock.
Tested with OTG configuration, usb gadget g_zero on DM365 EVM connected to PC.
To active the patch need to call davinci_setup_usb from dm365_evm_init
References:
Definition of USB_PHY_CTRL and
[Added Daniel and Clemens in the loop]
At Thu, 11 Oct 2012 17:17:59 +0200,
Matthieu CASTET wrote:
Hi,
while doing some monkey tests on a product we found races in usb audio code
when
the device in unplugged from usb (on linus master tree).
This can be reproduced with
From: Constantine Shulyupin co...@makelinux.com
Call USB initialization davinci_setup_usb from board initialization
dm365_evm_init.
Tested with OTG configuration, usb gadget g_zero on DM365 EVM connected to PC.
Note: register USB_PHY_CTRL must have flag USBPHY_CLKFREQ_24MHZ
References:
On Thu, 11 Oct 2012, Gian-Carlo Pascutto wrote:
On 11/10/12 17:19, Alan Stern wrote:
Maybe my hardware/chipset is just crap?
I don't know, maybe. Maybe that's just a bad cable connection (this
includes the possibility of bad connections inside the PC case).
Ouch. I can check a
On Mon, Oct 01, 2012 at 03:53:03PM -0400, Alan Stern wrote:
On Mon, 1 Oct 2012, Sarah Sharp wrote:
I don't remember the details. Doesn't usb_unlocked_disable_lpm() force
the device back into U0? You call that routine before suspending the
port.
It sends the control transfer to
On Tue, Oct 09, 2012 at 03:36:59PM -0400, Alan Stern wrote:
On Tue, 9 Oct 2012, Sarah Sharp wrote:
Hmm, so I've tested the VIA hubs under a different Intel chipset (Lynx
Point), and they exhibit the same issues as when a bus analyzer is
connected on Panther Point. Only the issues show up
On Thu, 11 Oct 2012, Sarah Sharp wrote:
Thinking about this further, USB 2.1 devices need to be brought out of
their low power link state (L1) before they are suspended. Some xHCI
host controllers have hardware-driven USB 2.1 LPM, so the device could
have been put in L1 before hibernation.
From: Alan Cox a...@lxorguk.ukuu.org.uk
Date: Thu, 11 Oct 2012 17:22:03 +0100
From: Alan Cox a...@linux.intel.com
We nowdays copy the buffer and free fw-data, so make the debug printk use
the right thing.
Signed-off-by: Alan Cox a...@linux.intel.com
Applied and queued up for -stable.
--
On Thu, 11 Oct 2012, Peter Chen wrote:
You could test all the port status registers. If any of them have the
PORT_PE bit set and the PORT_SUSPEND bit clear then the delay is
needed; otherwise it can be skipped.
I think the condition should like below, as we need to consider remote
Before a driver is probed, we want to disable USB 3.0 Link Power
Management (LPM), in case the driver needs hub-initiated LPM disabled.
After the probe finishes, we want to attempt to re-enable LPM, order to
balance the LPM ref count.
When a probe fails (such as when libusual doesn't want to bind
Some USB 3.0 devices signal that they don't implement Link PM by having
all zeroes in the U1/U2 exit latencies in their SuperSpeed BOS
descriptor. Don found that a Western Digital device he has experiences
transfer errors when LPM is enabled. The lsusb shows the U1/U2 exit
latencies are set to
SEL and PEL are in microseconds, not milliseconds. Also, fix a split
string that will trigger checkpatch warnings.
Signed-off-by: Sarah Sharp sarah.a.sh...@linux.intel.com
---
drivers/usb/core/hub.c |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git
The following changes since commit ecefbd94b834fa32559d854646d777c56749ef1c:
Merge tag 'kvm-3.7-1' of git://git.kernel.org/pub/scm/virt/kvm/kvm
(2012-10-04 09:30:33 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/sarah/xhci.git
The Set SEL control transfer tells a device the exit latencies
associated with a device-initated U1 or U2 exit. Since a parent hub may
initiate a transition to U1 soon after a downstream port's U1 timeout is
set, we need to make sure the device receives the Set SEL transfer
before the parent hub
Hi Hans,
Oh what fun (not). The best way to figure out what really is going
on is to get some usb level traces. Note my first hunch is that what
you're seeing is a device firmware bug, as this patch together with
a new libusb (which you seem to also have) will make bulk transfers
run
Henrik Rydberg wrote:
Hi Hans,
Oh what fun (not). The best way to figure out what really is going
on is to get some usb level traces. Note my first hunch is that what
you're seeing is a device firmware bug, as this patch together with
a new libusb (which you seem to also have) will make
On Thu, Oct 11, 2012 at 08:50:33AM +0200, Peter Stuge wrote:
Henrik Rydberg wrote:
What is the programming cable and software that uses it?
The programmer is impact, using libusbx-1.0.14-1.
Do you know for a fact that your version calls libusb-1.0? Did you
establish this with e.g.
On Thu, Oct 11, 2012 at 11:37:07PM +0200, Henrik Rydberg wrote:
Hi Hans,
Oh what fun (not). The best way to figure out what really is going
on is to get some usb level traces. Note my first hunch is that what
you're seeing is a device firmware bug, as this patch together with
a new
On Thu, Oct 11, 2012 at 02:28:06PM -0700, Sarah Sharp wrote:
The following changes since commit ecefbd94b834fa32559d854646d777c56749ef1c:
Merge tag 'kvm-3.7-1' of git://git.kernel.org/pub/scm/virt/kvm/kvm
(2012-10-04 09:30:33 -0700)
are available in the git repository at:
On Thu, 11 Oct 2012, Ming Lei wrote:
Keeping allowed gfp_flag inside task_struct should be one solution, and
let that teach mm to allocate memory, see the draft idea below:
Hmm, I actually like that idea.
I guess you are going to propose this to a wider audience, right? So I am
now putting
On Wed, Oct 10, 2012 at 11:08:11AM -0400, Alan Stern wrote:
On Wed, 10 Oct 2012, Oliver Neukum wrote:
Hi,
Ming Lei made me look. I found a scenario I don't like.
Suppose we have a device with two interfaces #1 and #0
Let #1 be storage and #0 be vendor specific and the skeleton driver
On Fri, Oct 12, 2012 at 5:55 AM, Jiri Kosina jiri.kos...@suse.com wrote:
On Thu, 11 Oct 2012, Ming Lei wrote:
Keeping allowed gfp_flag inside task_struct should be one solution, and
let that teach mm to allocate memory, see the draft idea below:
Hmm, I actually like that idea.
I guess you
On Thu, Oct 11, 2012 at 12:00 AM, Ming Lei tom.leim...@gmail.com wrote:
Keeping allowed gfp_flag inside task_struct should be one solution, and
let that teach mm to allocate memory, see the draft idea below:
diff --git a/drivers/usb/storage/transport.c b/drivers/usb/storage/transport.c
index
2012/10/11 Alan Stern st...@rowland.harvard.edu:
On Thu, 11 Oct 2012, Elric Fu wrote:
Hi all,
I recently found a strange issue on a embedded platform and don't know
how to fix it. Please give me some suggestions.
The platform is ar9331. The issue is if we attach a usb audio device to
the
2012/10/11 Peter Stuge pe...@stuge.se:
Elric Fu wrote:
It is a usb 1.1 device and works at full speed.
It is a frequent misunderstanding that a device must be 1.1 only
because it does not support high speed. This is not the case.
But the interesting thing is the bcdUSB field of device
On Thu, Oct 11, 2012 at 10:36 PM, Alan Stern st...@rowland.harvard.edu wrote:
It's worse than you may realize. When a SCSI disk is suspended, all of
its ancestor devices may be suspended too. Pages can't be read in from
the drive until all those ancestors are resumed. This means that all
1st pos of __usbhs_for_each_pipe() was wrong.
Each pipe were pipe0, pipe2, pipe3 ...
This patch modifies it.
Signed-off-by: Kuninori Morimoto kuninori.morimoto...@renesas.com
---
drivers/usb/renesas_usbhs/pipe.h |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Thu, Oct 11, 2012 at 03:20:51PM -0400, Alan Stern wrote:
On Thu, 11 Oct 2012, Peter Chen wrote:
There is a port on the root hub with suspend status clear
and enabled status set (which implies there must be a device
attached to the port, because disconnected ports can't be
Signed-off-by: Kuninori Morimoto kuninori.morimoto...@renesas.com
---
drivers/usb/renesas_usbhs/common.c |5 +
drivers/usb/renesas_usbhs/common.h |1 +
drivers/usb/renesas_usbhs/mod_gadget.c | 11 +++
3 files changed, 17 insertions(+)
diff --git
When interrupt happened, renesas_usbhs driver gets irq status
by usbhs_status_get_each_irq(), and cleared all status by using 0.
But, this method is incorrect,
since extra interrupt might occur between them.
This patch cleared corresponding bits only
Signed-off-by: Kuninori Morimoto
76 matches
Mail list logo
