Problem is that, when I try to move files from usb3 hard drive dock to laptop,
all usb ports drops (all external ports are usb3).
How to reproduce bug:
1. When connecting hard drive dock everything is well, here is log:
Jul 28 10:21:49 localhost kernel: [ 520.002851] usb 4-1: new SuperSpeed
On 2012年07月30日 15:24, Oliver Neukum wrote:
On Monday 30 July 2012 11:34:11 Lan Tianyu wrote:
--- a/drivers/usb/core/sysfs.c
+++ b/drivers/usb/core/sysfs.c
@@ -209,10 +209,13 @@ set_avoid_reset_quirk(struct device *dev, struct
device_attribute *attr,
if (sscanf(buf, %d,val) != 1 || val
Huang Ying ying.hu...@intel.com writes:
Do you have time to test the following patch to fix the lspci issue?
Subject: [BUGFIX] PCI/PM: Keep parent bridge active when read/write config reg
Sure. But keep this going and I will file a request for modular build
of the PCI subsystem :-)
The
Lan Tianyu tianyu@intel.com writes:
- if (sscanf(buf, %d, config) != 1 || config 0 || config 1)
+ if (sscanf(buf, %d, val) != 1 || val 0 || val 1)
return -EINVAL;
Not directly related to this patch, but a question I started wondering
about recently: Is there
The mailbox register for usb otg in omap is present in control module.
On detection of any events VBUS or ID, this register should be written
to send the notification to musb core.
Till we have a separate control module driver to write to control module,
omap2430 will handle the register writes
Add twl4030-usb data node in twl4030 device tree file.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/boot/dts/twl4030.dtsi | 21 +
1 file changed, 21 insertions(+)
diff --git a/arch/arm/boot/dts/twl4030.dtsi b/arch/arm/boot/dts/twl4030.dtsi
index
All the PHY configuration other than VBUS, ID GND and OTG SRP are removed
from twl6030. The phy configurations are taken care by the dedicated
usb2 phy driver. So twl6030 is made as comparator driver for VBUS and
ID detection.
Writing to control module which is now handled in omap2430.c should be
Add device tree support for twl6030 usb driver.
Update the Documentation with device tree binding information.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
.../devicetree/bindings/usb/twl-usb.txt| 21 +++
drivers/usb/otg/twl6030-usb.c | 39
On Thu, Jul 26, 2012 at 06:59:48PM +0800, Richard Zhao wrote:
On Thu, Jul 19, 2012 at 10:05:54AM +0800, Richard Zhao wrote:
On Mon, Jul 16, 2012 at 05:40:57PM -0700, Greg KH wrote:
On Thu, Jul 12, 2012 at 03:01:40PM +0800, Richard Zhao wrote:
The patch set is tested on imx6q_sabrelite
On Thu, Jul 26, 2012 at 06:35:14PM +0800, Richard Zhao wrote:
i.MX usb controllers shares non-core registers, which may include
SoC specific controls. We take it as a usbmisc device and usbmisc
driver set operations needed by ci13xxx_imx driver.
For example, Sabrelite board has bad
On Mon, Jul 30, 2012 at 11:32:44AM +0200, Sascha Hauer wrote:
On Thu, Jul 26, 2012 at 06:35:14PM +0800, Richard Zhao wrote:
i.MX usb controllers shares non-core registers, which may include
SoC specific controls. We take it as a usbmisc device and usbmisc
driver set operations needed by
On Monday 30 July 2012 15:58:25 Lan Tianyu wrote:
On 2012年07月30日 15:24, Oliver Neukum wrote:
this is on second thought quite problematic. If user space has
disabled the persist feature it must stay disabled, even if
the quirk setting is removed.
Yeah. You are right. So how about remain
On Monday 30 July 2012 03:16 PM, ABRAHAM, KISHON VIJAY wrote:
Hi,
On Mon, Jul 30, 2012 at 3:07 PM, Shubhrajyoti shubhrajy...@ti.com wrote:
On Monday 30 July 2012 02:39 PM, Kishon Vijay Abraham I wrote:
+ writel(~PHY_PD, phy-control_dev);
+ /* XXX: add
Hi Anton,
On Mon, July 30, 2012 5:25 am, Anton Tikhomirov wrote:
Hi Ido,
You activate sm only if gadget and host are ready. At the same time,
in dwc3_otg_interrupt() you schedule work if interrupt happens. In
situation
when host is not set yet, but cable is plugged, we will have
Hello.
On 07/24/2012 11:17 PM, Mark Ferrell wrote:
* mos7840_startup() blindly calls kfree() on memory that may have never been
allocated.
Callling kfree() on NULL pointers is valid.
Signed-off-by: Mark Ferrell mferr...@uplogix.com
WBR, Sergei
--
To unsubscribe from this list: send
On Mon, 30 Jul 2012 10:33:27 +0200, Bjørn Mork bj...@mork.no wrote:
Lan Tianyu tianyu@intel.com writes:
Not directly related to this patch, but a question I started wondering
about recently: Is there some generic guideline wrt parsing boolean
flags in sysfs? If not, shouldn't there be?
I
From: Justin P. Mattock justinmatt...@gmail.com
Signed-off-by: Justin P. Mattock justinmatt...@gmail.com
---
The below patch fixes typos found while reading through staging: usbip
drivers/staging/usbip/stub_rx.c |2 +-
drivers/staging/usbip/vhci_hcd.c |4 ++--
2 files changed, 3
Hi,
The code structure (device selector + functions indirection) also seems
overkill
to me for now, but permit to anticipate device's variations. If it appears
that they
all works in the same way, it'll be easy (and more comfortable to me) to
step down,
the opposite seems more
On Mon, 30 Jul 2012, Oliver Neukum wrote:
On Monday 30 July 2012 11:34:10 Lan Tianyu wrote:
The hub is always supposed to support reset and its persist is enabled.
By default, not necessarily always. User space may disable it.
No -- necessarily always. Userspace cannot disable it. The
On Mon, 30 Jul 2012, Bjørn Mork wrote:
Lan Tianyu tianyu@intel.com writes:
- if (sscanf(buf, %d, config) != 1 || config 0 || config 1)
+ if (sscanf(buf, %d, val) != 1 || val 0 || val 1)
return -EINVAL;
Not directly related to this patch, but a question I
On Mon, 30 Jul 2012, Oliver Neukum wrote:
On Monday 30 July 2012 15:58:25 Lan Tianyu wrote:
On 2012年07月30日 15:24, Oliver Neukum wrote:
this is on second thought quite problematic. If user space has
disabled the persist feature it must stay disabled, even if
the quirk setting is
From: Julia Lawall julia.law...@lip6.fr
The various devm_ functions allocate memory that is released when a driver
detaches. This patch uses these functions for data that is allocated in
the probe function of a platform device and is only freed in the remove
function.
Signed-off-by: Julia
From: Julia Lawall julia.law...@lip6.fr
The various devm_ functions allocate memory that is released when a driver
detaches. This patch uses these functions for data that is allocated in
the probe function of a platform device and is only freed in the remove
function.
Signed-off-by: Julia
From: Julia Lawall julia.law...@lip6.fr
The various devm_ functions allocate memory that is released when a driver
detaches. This patch uses these functions for data that is allocated in
the probe function of a platform device and is only freed in the remove
function.
Signed-off-by: Julia
From: Julia Lawall julia.law...@lip6.fr
The various devm_ functions allocate memory that is released when a driver
detaches. This patch uses these functions for data that is allocated in
the probe function of a platform device and is only freed in the remove
function.
Signed-off-by: Julia
From: Julia Lawall julia.law...@lip6.fr
The various devm_ functions allocate memory that is released when a driver
detaches. This patch uses these functions for data that is allocated in
the probe function of a platform device and is only freed in the remove
function.
Signed-off-by: Julia
From: Julia Lawall julia.law...@lip6.fr
The various devm_ functions allocate memory that is released when a driver
detaches. This patch uses these functions for data that is allocated in
the probe function of a platform device and is only freed in the remove
function.
Signed-off-by: Julia
From: Julia Lawall julia.law...@lip6.fr
The various devm_ functions allocate memory that is released when a driver
detaches. This patch uses these functions for data that is allocated in
the probe function of a platform device and is only freed in the remove
function.
Signed-off-by: Julia
The default 10 microsecond delay for the controller to come out of
halt in dbgp_ehci_startup is too short, so increase it to 1 millisecond.
This is based on emperical testing on various USB debug ports on
modern machines such as a Lenovo X220i and an Ivybridge development
platform that needed to
On Mon, 30 Jul 2012, Oliver Neukum wrote:
On Monday 30 July 2012 10:39:50 Alan Stern wrote:
this leads to behavior that is not easy to predict or understand.
It would be cleaner to leave the flag alone and check for the quirk
in addition for the flag when the check is done.
I
On Monday 30 July 2012 11:16:12 Alan Stern wrote:
As you say, coupling the two attributes is confusing and circumvents
the permissions. If the device needs a reset-resume, we'll go ahead
and try to do it. If the reset fails because the firmware gets erased,
at least there will be an error
On Mon, Jul 30, 2012 at 05:17:58PM +0800, Richard Zhao wrote:
On Thu, Jul 26, 2012 at 06:59:48PM +0800, Richard Zhao wrote:
On Thu, Jul 19, 2012 at 10:05:54AM +0800, Richard Zhao wrote:
On Mon, Jul 16, 2012 at 05:40:57PM -0700, Greg KH wrote:
On Thu, Jul 12, 2012 at 03:01:40PM +0800,
This commit fixes the way gadget's pullup method (wrapped at
usb_gadget_connect/disconnect) is called in the udc-core.
The composite driver allows correct driver registration, even when it calls
the usb_gadget_disconnect method (composite driver configuration is defered
for user space - please
On Mon, Jul 30, 2012 at 10:33:27AM +0200, Bjørn Mork wrote:
Lan Tianyu tianyu@intel.com writes:
- if (sscanf(buf, %d, config) != 1 || config 0 || config 1)
+ if (sscanf(buf, %d, val) != 1 || val 0 || val 1)
return -EINVAL;
Not directly related to this patch, but
Hello.
On 07/30/2012 06:23 PM, Justin P. Mattock wrote:
From: Justin P. Mattock justinmatt...@gmail.com
Signed-off-by: Justin P. Mattock justinmatt...@gmail.com
---
The below patch fixes typos found while reading through staging: usbip
Unfortunately, it introduces some new instead.
On 30.07.2012 19:05, Greg KH wrote:
On Mon, Jul 30, 2012 at 09:29:12AM +0200, Daniel Mack wrote:
Add DT bindings to the ohci-pxa27x driver and some documentation.
Successfully tested on a PXA3xx board.
Signed-off-by: Daniel Mack zon...@gmail.com
---
Changes from v1:
- renamed mrvl to
Hello.
On 11/24/2011 09:59 PM, Sergei Shtylyov wrote:
we are compiling the driver always with full OTG
capabilities, so that board_mode trick becomes
useless.
Signed-off-by: Felipe Balbiba...@ti.com
---
I would like to get Acks from blackfin, da8xx and davinci guys, please.
After
On Mon, Jul 30, 2012 at 09:28:36AM +0200, Oliver Neukum wrote:
On Monday 30 July 2012 11:34:10 Lan Tianyu wrote:
The hub is always supposed to support reset and its persist is enabled.
By default, not necessarily always. User space may disable it.
So hub doesn't need attribute
Sarah Sharp sarah.a.sh...@linux.intel.com writes:
On Mon, Jul 30, 2012 at 09:28:36AM +0200, Oliver Neukum wrote:
On Monday 30 July 2012 11:34:10 Lan Tianyu wrote:
The hub is always supposed to support reset and its persist is enabled.
By default, not necessarily always. User space may
On Monday 30 July 2012 22:35:37 Bjørn Mork wrote:
Sarah Sharp sarah.a.sh...@linux.intel.com writes:
On Mon, Jul 30, 2012 at 09:28:36AM +0200, Oliver Neukum wrote:
- We need to issue a reset resume for all suspended devices that have
been powered off.
- We can't power off ports
On Mon, 30 Jul 2012, Alexey Filin wrote:
Yes, something like it might work, I think. But you probably wouldn't
want to use URBs for this; they have too much overhead. You'd need a
more direct interface to the host controller driver.
really, too much, about 7 us on my pc (Core2 Duo CPU
On Mon, Jul 30, 2012 at 03:22:52PM -0500, Alexis Cortes wrote:
Hi Greg,
I'm sorry for my late response on this. First of all thanks for your reply
and your feedback :)
We have been discussing with one of our major customers the possibility of
identifying the platforms with the failing
On Tue, Jul 31, 2012 at 1:08 AM, Alan Stern st...@rowland.harvard.edu wrote:
On Mon, 30 Jul 2012, Alexey Filin wrote:
Yes, something like it might work, I think. But you probably wouldn't
want to use URBs for this; they have too much overhead. You'd need a
more direct interface to the
On Mon, Jun 25, 2012 at 11:37 PM, Shawn Guo shawn@linaro.org wrote:
On Mon, Jun 25, 2012 at 01:18:22PM -0300, Fabio Estevam wrote:
Any suggestions as to how to make the driver work on mx23?
I won't be able to test it on my imx23-evk board, because the board
design is somehow odd on vbus
Hi Denis,
Can you send me the output of `sudo dmidecode`? I'd like to see if I
can make a more general patch apply to the Intense-PC.
Sarah Sharp
--
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
On Mon, 2012-07-30 at 18:57 +0200, Bjørn Mork wrote:
huang ying huang.ying.cari...@gmail.com writes:
On Mon, Jul 30, 2012 at 4:08 PM, Bjørn Mork bj...@mork.no wrote:
Huang Ying ying.hu...@intel.com writes:
Do you have time to test the following patch to fix the lspci issue?
Subject:
This patchset tries to handle all the review comments received
on the following UVC gadget related patches:
[PATCH 4/5] usb: gadget/uvc: Port UVC webcam gadget to use videobuf2 framework
[PATCH 5/5] usb: gadget/uvc: Add support for 'USB_GADGET_DELAYED_STATUS'
response for a set_intf(alt-set 1)
This patch reworks the videobuffer management logic present in the UVC
webcam gadget and ports it to use the more apt videobuf2 framework for
video buffer management.
To support routing video data captured from a real V4L2 video capture
device with a zero copy operation on videobuffers (as they
This patch adds the support in UVC webcam gadget design for providing
USB_GADGET_DELAYED_STATUS in response to a set_interface(alt setting 1)
command issue by the Host.
The current UVC webcam gadget design generates a STREAMON event
corresponding to a set_interface(alt setting 1) command from the
usbmisc 0 would then mean port 0 of the usbmisc device.
I didn't add the restriction that a usbmisc driver must have a usbmisc
device. I'm not sure whether all SoC and future SoC can be look as
a device.
Peter, do you have any idea?
I have not followed this usbmisc design, I just
On Mon, 2012-07-30 at 10:19 -0400, Alan Stern wrote:
On Mon, 30 Jul 2012, Huang Ying wrote:
Yup, that worked in the quick test I just did.
lspci reading the device config will still not wake the bridge, but I
assume that is intentional? But loading the device driver now wakes
On Monday 30 July 2012 15:34:06 Sarah Sharp wrote:
Hi Denis,
Can you send me the output of `sudo dmidecode`? I'd like to see if I
can make a more general patch apply to the Intense-PC.
As this is for shutdown, why not all systems?
Regards
Oliver
--
To unsubscribe
this patch enable to use pm_runtime_xxx() on ohci-platform
if .config has CONFIG_PM_RUNTIME, otherwise, these are ignored
Signed-off-by: Kuninori Morimoto kuninori.morimoto...@renesas.com
---
drivers/usb/host/ohci-platform.c |6 ++
1 files changed, 6 insertions(+), 0 deletions(-)
diff
On Thu, Jul 26, 2012 at 11:36:44PM -0700, Matthew Hall wrote:
On Thu, Jul 26, 2012 at 11:27:47PM -0700, Sarah Sharp wrote:
Man, I hope my code hasn't eaten your disk. Is there any chance you
could replace the drive in the enclosure and create a new file system to
test?
This part is
On 2012年07月30日 23:16, Alan Stern wrote:
On Mon, 30 Jul 2012, Oliver Neukum wrote:
On Monday 30 July 2012 10:39:50 Alan Stern wrote:
this leads to behavior that is not easy to predict or understand.
It would be cleaner to leave the flag alone and check for the quirk
in addition for the flag
55 matches
Mail list logo
