gmane.linux.usb.general

Re: USB device not detected on boot

Nuno Gonçalves — 2010-03-11T00:11:17

On power-on(device not discovered):

root< at >OpenWrt:/# cat /sys/kernel/debug/usb/ehci/ar71xx-ehci/registers
bus platform, device ar71xx-ehci
Atheros AR91xx built-in EHCI controller
EHCI 1.00, hcd state 1
structural params 0x00010011
capability params 0x00000006
status 0088 FLR
command 010009 (park)=0 ithresh=1 period=256 RUN
intrenable 37 IAA FATAL PCD ERR INT
uframe 0878
port 1 status c001000 POWER sig=se0
irq normal 0 err 0 reclaim 0 (lost 0)
complete 0 unlink 0

On restart(device discovered):

root< at >OpenWrt:/# cat /sys/kernel/debug/usb/ehci/ar71xx-ehci/registers
bus platform, device ar71xx-ehci
Atheros AR91xx built-in EHCI controller
EHCI 1.00, hcd state 1
structural params 0x00010011
capability params 0x00000006
status 40088 FLR
command 010009 (park)=0 ithresh=1 period=256 RUN
intrenable 37 IAA FATAL PCD ERR INT
uframe 2f18
port 1 status 001805 POWER sig=j PE CONNECT
irq normal 13 err 0 reclaim 5 (lost 0)
complete 13 unlink 0

On insert:

root< at >OpenWrt:/# cat /sys/kernel/debug/usb/ehci/ar71xx-ehci/registers

Re: [RFC/PATCH 1/2] usb: gadget: u_char: introduce chardev abstraction layer

David Brownell — 2010-03-10T23:14:16

Worth clarifying.  If u_char is just to provide a lower overhead byte
stream abstraction (packet/frame boundaries never matter) than TTY,
that's one thing.  Last time I looked at the protocols involved, that
was the I/O model.

But there's no doubt that some protocols get built over packet streams,
a different abstraction.  Reaching back to the early Ethernet days, some
folk may recall that the original XNS protocol stack included a "Sequenced
Packet Protocol" SPP, in contrast to the byte stream model of TCP.

- Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA< at >public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [RFC/PATCH 1/2] usb: gadget: u_char: introduce chardev abstraction layer

Alan Cox — 2010-03-10T22:21:23

It sounds like a bug that someone needs to provide a test case and
explanation for. The underlying buffering logic appears solid up to about
40MB/sec (beyond that the existing buffer settings and round trip time
for flow control would need addressing and possibly some data handling).

I don't see any real value in a char abstraction for most of the cases
where we hit performance and other problems - a packet abstraction ought
to be both a lot faster and provide a more flexible interface for
stuff where usb frame boundaries matter.

Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA< at >public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: usbmon problem

Oliver Neukum — 2010-03-10T23:09:13

Am Mittwoch, 10. März 2010 21:38:43 schrieb Alan Stern:

A fs**** &

Anyway, here it is:
Mar 11 00:06:38 vanamonde kernel: usb-storage: Issuing auto-REQUEST_SENSE                                       
Mar 11 00:06:38 vanamonde kernel: usb_stor_invoke_transport - sglist ffff8801370d5dc8 sense buffer ffff880135c242c0 sense sgl ffff8801370d5dc8 sg_virt ffff880135c242c0 page link ffffea00043c27e2 dmaaddr (null)
Mar 11 00:06:38 vanamonde kernel: usb-storage: Bulk Command S 0x43425355 T 0x9c L 18 F 128 Trg 0 LUN 0 CL 6                                                                                                      
Mar 11 00:06:38 vanamonde kernel: usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes                                                                                                                         
Mar 11 00:06:38 vanamonde kernel: mon_text_get_data: num_sgs == 0: src ffff880037816000

Re: USB_QUIRK_RESET_MORPHS: can't find "avoid_reset"

Oliver Neukum — 2010-03-10T23:02:45

Am Mittwoch, 10. März 2010 11:11:49 schrieb Josua Dietze:

I can replicate the issue. I am investigating.

Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA< at >public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: usbmon problem

Alan Stern — 2010-03-10T20:38:43


---------------------------------------------^

I asked for &ses.sense_sgl, not ses.sense_sgl.  That must have messed
up the printk, since it would pass the entire structure as an argument
instead of just passing its address.

Alan Stern

--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA< at >public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: USB device not detected on boot

Alan Stern — 2010-03-10T20:21:42


Must be.

Here's something else you can do.  Make sure CONFIG_DEBUG_FS is also
enabled in the configuration.  Then mount a debugfs filesystem, say on
/sys/kernel/debug, and post a copy of the
/sys/kernel/debug/usb/ehci/ar71xx/registers file (the pathname may be
slightly different from this, but it will be similar).  Do this after a
failed detection, while the device is still plugged in.

Alan Stern

--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA< at >public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: USB device not detected on boot

Nuno Gonçalves — 2010-03-10T18:21:45

root< at >OpenWrt:/# lsmod | grep usb
usbserial              23856  0
root< at >OpenWrt:/# lsmod | grep ar71xx
root< at >OpenWrt:/#

Maybe it's builtin and not a module...?

Regards,
Nuno

2010/3/10 Alan Stern <stern-nwvwT67g6+6dFdvTe/nMLpVzexx5G7lz< at >public.gmane.org>:

Re: [PATCH 2/4] USB: MUSB: Enable MUSB for OMAP4 in Kconfig

Olof Johansson — 2010-03-10T18:27:02

Yeah, they can go in. It was more a comment in case someone's looking for
janitorial things to do.


-Olof
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA< at >public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: USB device not detected on boot

Nuno Gonçalves — 2010-03-10T18:18:14

I haven't provided all the information. Sorry.

USB device not recognized on computer power-on(dmesg log is exactaly
the same if the device is not connected. No recognition in any way).
USB device RECOGNIZED on computer restart.
USB device RECOGNIZED on insert after computer is booted.

I include below the dmesg part that changes from a computer power-on
to a computer restart. (this is for the "successful" boot).

Going to test now to unload and load the driver.

Regards,
Nuno

[   13.140000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[   13.140000] ehci_hcd: block sizes: qh 60 qtd 96 itd 160 sitd 96
[   13.140000] ar71xx-ehci ar71xx-ehci: Atheros AR91xx built-in EHCI controller
[   13.150000] drivers/usb/core/inode.c: creating file 'devices'
[   13.150000] drivers/usb/core/inode.c: creating file '001'
[   13.150000] ar71xx-ehci ar71xx-ehci: new USB bus registered,
assigned bus number 1
[   13.160000] ar71xx-ehci ar71xx-ehci: reset command 080002 (park)=0
ithresh=8 period=1024 Reset HALT
[

Re: USB device not detected on boot

Alan Stern — 2010-03-10T18:16:54




Yes, this definitely looks like a problem with the ar71xx-ehci driver.

What happens if you unplug the device and rmmod the driver, then plug 
the device in again, and then modprobe the driver?

Alan Stern

--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA< at >public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: USB device not detected on boot

Nuno Gonçalves — 2010-03-10T17:36:52

Full log below.
Boot finish at 66.540000, device not detected.
Then I remove and insert it. Detected.

Would appreciate any tip.

Regards,
Nuno


[    0.000000] Linux version 2.6.32.9 (nuno< at >ground2) (gcc version
4.3.3 (GCC) ) #3 Wed Mar 10 17:27:21 WET 2010
[    0.000000] prom: fw_arg0=00000009, fw_arg1=a1f67fb0,
fw_arg2=a1f68470, fw_arg3=00000008
[    0.000000] MyLoader: sysp=aaaa5554, boardp=aaaa5554, parts=aaaa5554
[    0.000000] bootconsole [early0] enabled
[    0.000000] CPU revision is: 00019374 (MIPS 24Kc)
[    0.000000] Atheros AR9130 rev 2, CPU:400.000 MHz, AHB:200.000 MHz,
DDR:400.000 MHz
[    0.000000] Determined physical RAM map:
[    0.000000]  memory: 02000000 < at > 00000000 (usable)
[    0.000000] Initrd not found or empty - disabling initrd
[    0.000000] Zone PFN ranges:
[    0.000000]   Normal   0x00000000 -> 0x00002000
[    0.000000] Movable zone start PFN for each node
[    0.000000] early_node_map[1] active PFN ranges
[    0.000000]     0: 0x00000000 -> 0x00002000
[    0.000000] On node 0 to

Re: usbmon problem

Oliver Neukum — 2010-03-10T16:36:16

Am Montag, 8. März 2010 19:50:23 schrieb Alan Stern:

Retry_Sense:
US_DEBUGP("Issuing auto-REQUEST_SENSE\n");

scsi_eh_prep_cmnd(srb, &ses, NULL, 0, sense_size);
printk(KERN_ERR"%s - sglist %p sense buffer %p sense sgl %p sg_virt %p page link %p dmaaddr %p\n", __func__,
scsi_sglist(srb), srb->sense_buffer, ses.sense_sgl, ((void *)sg_virt(&ses.sense_sgl)),
(void *)ses.sense_sgl.page_link, (void *)ses.sense_sgl.dma_address);

As far as I can tell, it is correct? Disassembly needed?

Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA< at >public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[PATCH] USB Serial Driver: ZIO Motherboard

Vijay Kumar — 2010-03-10T15:47:56

Add ZIO Motherboard USB serial interface driver.

Signed-off-by: Vijay Kumar B. <vijaykumar-1MQmoylvZ5VBDgjK7y7TUQ< at >public.gmane.org>

Index: linux-2.6/drivers/usb/serial/Kconfig
===================================================================
--- linux-2.6.orig/drivers/usb/serial/Kconfig2010-03-10 21:06:26.000000000 +0530
+++ linux-2.6/drivers/usb/serial/Kconfig2010-03-10 21:06:34.000000000 +0530
< at >< at > -619,6 +619,14 < at >< at >
           To compile this driver as a module, choose M here: the
           module will be called vivopay-serial.
 
+config USB_SERIAL_ZIO
+tristate "ZIO Motherboard USB serial interface driver"
+help
+  Say Y here if you want to use ZIO Motherboard.
+
+  To compile this driver as a module, choose M here: the
+  module will be called zio.
+
 config USB_SERIAL_DEBUG
 tristate "USB Debugging Device"
 help
Index: linux-2.6/drivers/usb/serial/Makefile
===================================================================
--- linux-2.6.orig/drivers/usb/serial/Makefile2010-03-10 21:06:22.00

Re: USB device not detected on boot

Alan Stern — 2010-03-10T15:07:31


As Greg said, this is likely to be a platform issue.  However you _can_
collect some additional information.  Build a kernel with
CONFIG_USB_DEBUG and CONFIG_PRINTK_TIME enabled, and then post the
dmesg log showing what happens during a boot in which the modem wasn't
detected.

Alan Stern

--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA< at >public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: USB device not detected on boot

Greg KH — 2010-03-10T14:43:04

proc does not contain usb devices at all anymore, so that's not an issue
:)


Sounds like a host controller issue.  We've seen this in the past and it
ended up not being a USB core problem, but a platform one.  I suggest
contacting the openwrt developers with the issue, not much we can do
about it here.

good luck,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA< at >public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [RFC/PATCH 1/2] usb: gadget: u_char: introduce chardevabstraction layer

Greg KH — 2010-03-10T13:43:00

For mtp, I understand, that's fine.

But for "raw" data, please stick with the tty layer, as you will end up
reimplementing most of it anyway in the end :)

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA< at >public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [RFC/PATCH 1/2] usb: gadget: u_char: introduce chardevabstraction layer

Greg KH — 2010-03-10T13:42:02

The tty layer is always in flux :)

Anyway, I would be interested in seeing this all fixed up first, I'm
pretty sure that the high data rates can happen in this driver that
would make the char driver not be needed at all (and if you really need
high speeds, then you can use a proper line dicipline as you pointed
out, which will be needed anyway.)

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA< at >public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

USB device not detected on boot

Nuno Gonçalves — 2010-03-10T13:44:22

The UMTS modem Huawei E169 sometimes is not detected as a USB device
on boot. No entry on /proc/...
When pluged after the system is booted, it is always detected.

It looks like some kind of incompability with this unit firmware(I've
tested 5 hardware pieces).

Is there any kind of diagnose suit I can run to try to diagnose the issue?

I could only find the problem on Openwrt(2.6).

Regards,

[PATCH v3] usb: musb: abstract out ULPI_BUSCONTROL register reads/writes

Mike Frysinger — 2010-03-10T12:35:38

The USB PHY on current Blackfin processors is a UTMI+ level 2 PHY.
However, it has no ULPI support - so there are no registers at all.
That means accesses to ULPI_BUSCONTROL have to be abstracted away
like other MUSB registers.

This fixes building for Blackfin parts again.

Signed-off-by: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A< at >public.gmane.org>
Acked-by: Anand Gadiyar <gadiyar-l0cyMroinI0< at >public.gmane.org>
---
v3
- fix copy & paste size error pointed out by Sergei

 drivers/usb/musb/musb_core.c |    5 ++---
 drivers/usb/musb/musb_regs.h |   19 +++++++++++++++++++
 2 files changed, 21 insertions(+), 3 deletions(-)

diff --git a/drivers/usb/musb/musb_core.c b/drivers/usb/musb/musb_core.c
index b4bbf8f..e54e468 100644
--- a/drivers/usb/musb/musb_core.c
+++ b/drivers/usb/musb/musb_core.c
< at >< at > -2007,7 +2007,6 < at >< at > bad_config:
 /* host side needs more setup */
 if (is_host_enabled(musb)) {
 struct usb_hcd*hcd = musb_to_hcd(musb);
-u8 busctl;
 
 otg_set_host(musb->xceiv, &hcd->self);
 
< at >< at > -2018,9 +201

Re: [Uclinux-dist-devel] [PATCH v2] usb: musb: abstract out ULPI_BUSCONTROL register reads/writes

Mike Frysinger — 2010-03-10T12:30:37

hrm, i noticed this when i was writing the patch, but i guess i messed
it up anyways.  good eye ;).
-mike
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA< at >public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html