On Fri, 3 Aug 2012, Yann Cantin wrote:
+#include linux/hid.h
As this driver is not a HID bus driver, why do you need this include?
Cinder, removed
+#define DRIVER_VERSIONv0.7
I don't think we need to be tracking driver versions for newly submitted
drivers, git is much
Hi all,
I'm using mainline upstream 3.6.0-rc1 compiled based on Fedora-16.
When I unplug my mobile usb card, I hit this:
[ 247.017258] BUG: unable to handle kernel NULL pointer dereference at
(null)
[ 247.017378] IP: [a03bf27f] stop_read_write_urbs+0x3f/0x90
[usb_wwan]
[
Host controller's suspend should be executed later than root hub's,
or the hang may occur when root hub try to visit some registers
but host controller's suspend close the related clocks.
Mark controller's suspend as async can make sure it is executed
later than root hub's as host controller is
Liu Bo liub.li...@gmail.com writes:
I'm using mainline upstream 3.6.0-rc1 compiled based on Fedora-16.
When I unplug my mobile usb card, I hit this:
[ 247.017258] BUG: unable to handle kernel NULL pointer dereference at
(null)
[ 247.017378] IP: [a03bf27f]
Hi,
I need some help debugging a USB transfer problem on my raspberry pi.
I know this is not a mainstream kernel issue but I would be glad if someone
here can
help me understand and debug the problem.
The problem is that the DVB Transport stream recorded from a usb DVB stick
(cinergy htc
On 08/13/2012 06:01 PM, Bjørn Mork wrote:
Liu Bo liub.li...@gmail.com writes:
I'm using mainline upstream 3.6.0-rc1 compiled based on Fedora-16.
When I unplug my mobile usb card, I hit this:
[ 247.017258] BUG: unable to handle kernel NULL pointer dereference at
(null)
[
Bjørn Mork bj...@mork.no writes:
The home cooked whitelisting code can be removed now that
the USB core supports interface number matching.
The second patch adds a few new devices.
The third patch improves device list readability by using
existing macros where possible.
I hope this can
This driver provides support for several Kvaser CAN/USB devices.
Such kind of devices supports up to three CAN network interfaces.
It has been tested with a Kvaser USB Leaf Light (one network interface)
connected to a pch_can interface.
The firmware version of the Kvaser device was 2.5.205.
List
On Sat, Aug 11, 2012 at 12:13:58AM +0400, Paul Fertser wrote:
Hi Felipe,
On Fri, Aug 10, 2012 at 10:39:52PM +0300, Felipe Balbi wrote:
On Fri, Aug 10, 2012 at 10:35:20PM +0400, Paul Fertser wrote:
I'm using an RT3052F device (DIR-620 SOHO wifi router) with current
OpenWrt trunk and its
Hi,
in finish_port_resume() usb_get_status() is always done and the result
evaluated even in the case of reset_resume. Is this efficient? If a device
has been reset, remote wakeup must be disabled.
Regards
Oliver
--
To unsubscribe from this list: send the line
We're trying to get USB host mode working on a Freescale i.MX233. I'm using
a chumby hacker board, but there are several people trying on an OlinuXino
board as well. We're running into a problem where every time the root hub
is detected, it's disconnected. This results in kernel messages such
Hi,
On Mon, Aug 13, 2012 at 12:34:53PM +1000, NeilBrown wrote:
On Thu, 9 Aug 2012 14:15:51 +0300 Felipe Balbi ba...@ti.com wrote:
hehe, that's nasty. Please send a patch converting to a try count and a
udelay_range(), or something.
how's this?
Thanks,
NeilBrown
From:
On Mon, Aug 13, 2012 at 12:01:52PM +0200, Ruben Jenster wrote:
Hi,
I need some help debugging a USB transfer problem on my raspberry pi.
I know this is not a mainstream kernel issue but I would be glad if someone
here can
help me understand and debug the problem.
The problem is that the
Hi all:
I am trying to implement patch of setting DeviceRemovable
according ACPI information.
The DeviceRemovable is set in hcd driver *_hub_descriptor(e.g
ehci_hub_descriptor()). But these
functions just have struct usb_hcd or hcd specific struct(e.g struct xhci_hcd)
and struct
On Mon, 13 Aug 2012, Oliver Neukum wrote:
Hi,
in finish_port_resume() usb_get_status() is always done and the result
evaluated even in the case of reset_resume. Is this efficient? If a device
has been reset, remote wakeup must be disabled.
Checking the remote wakeup setting is not the only
On Mon, 13 Aug 2012, Lan, Tianyu wrote:
Hi all:
I am trying to implement patch of setting DeviceRemovable
according ACPI information.
The DeviceRemovable is set in hcd driver *_hub_descriptor(e.g
ehci_hub_descriptor()). But these
functions just have struct usb_hcd or hcd
Hi,
I discovered the problem. I am using Openwrt and I was missing the
module usb-serial-option.
Using it everything works fine. The device modules and parameters are
loaded and ttyUSB*
are created.
Thanks for all the help,
Guilherme
On Fri, Jul 20, 2012 at 3:47 AM, Bjørn Mork bj...@mork.no
The intent was to test whether the flag was set.
Signed-off-by: Dan Carpenter dan.carpen...@oracle.com
diff --git a/drivers/usb/host/xhci.c b/drivers/usb/host/xhci.c
index c59d5b5..617b0a7 100644
--- a/drivers/usb/host/xhci.c
+++ b/drivers/usb/host/xhci.c
@@ -659,7 +659,7 @@ void
On 8/13/12, Sean Cross x...@xoblo.gs wrote:
We're trying to get USB host mode working on a Freescale i.MX233. I'm
using
a chumby hacker board, but there are several people trying on an OlinuXino
board as well. We're running into a problem where every time the root hub
is detected, it's
Hi,
On Mon, Aug 13, 2012 at 03:04:56PM -0300, Fabio Estevam wrote:
On 8/13/12, Sean Cross x...@xoblo.gs wrote:
We're trying to get USB host mode working on a Freescale i.MX233. I'm
using
a chumby hacker board, but there are several people trying on an OlinuXino
board as well. We're
On 8/13/12, Felipe Balbi ba...@ti.com wrote:
Will there be another version for this or is this final ? Won't this
cause any regressions to other boards ?
The proposed patch is not meant to be a final one.
We still need to figure out the proper way to handle HOSTDISCONDETECT
for all i.mx SoCs,
On Mon, 13 Aug 2012 17:32:34 +0300 Felipe Balbi ba...@ti.com wrote:
Hi,
On Mon, Aug 13, 2012 at 12:34:53PM +1000, NeilBrown wrote:
On Thu, 9 Aug 2012 14:15:51 +0300 Felipe Balbi ba...@ti.com wrote:
hehe, that's nasty. Please send a patch converting to a try count and a
On 8/13/12, Felipe Balbi ba...@ti.com wrote:
Will there be another version for this or is this final ? Won't this
cause any regressions to other boards ?
The proposed patch is not meant to be a final one.
We still need to figure out the proper way to handle HOSTDISCONDETECT
for all
Dear Chen Peter-B29397,
On 8/13/12, Felipe Balbi ba...@ti.com wrote:
Will there be another version for this or is this final ? Won't this
cause any regressions to other boards ?
The proposed patch is not meant to be a final one.
We still need to figure out the proper way to
Peter,
On 8/13/12, Chen Peter-B29397 b29...@freescale.com wrote:
According to IC guys, the logic of handling HOSTDISCONDETECT is the same
between i.mx28 and i.mx23.
As pointed out by Sean, on mx23 reference manual we have the following
text describing HOSTDISCONDETECT:
Due to a on chip issue
Add IC guy
Best regards,
Peter Chen
-Original Message-
From: Fabio Estevam [mailto:feste...@gmail.com]
Sent: Tuesday, August 14, 2012 10:01 AM
To: Chen Peter-B29397
Cc: ba...@ti.com; Sean Cross; linux-usb@vger.kernel.org; Estevam Fabio-
R49496; Zhao Richard-B20223; Shawn Guo;
According to IC guys, the logic of handling HOSTDISCONDETECT is the
same
between i.mx28 and i.mx23.
As pointed out by Sean, on mx23 reference manual we have the following
text describing HOSTDISCONDETECT:
Due to a on chip issue (Errata #2791), software must
pay attention to when
On Tue, Aug 14, 2012 at 10:40:21AM +0800, Chen Peter-B29397 wrote:
According to IC guys, the logic of handling HOSTDISCONDETECT is the
same
between i.mx28 and i.mx23.
As pointed out by Sean, on mx23 reference manual we have the following
text describing HOSTDISCONDETECT:
It is the same with i.mx28.
If they're same, imx23 should be ok. The mxs_phy driver pass test
on mx28.
I think Richard's patch should not
violate point 2. Richard, can you confirm it?
You mean I should not set the bit in mxs_phy_on_connect?
or mxs_phy_on_connect is called in wrong
29 matches
Mail list logo
