hi all:
when I trace linux ehci driver source code.
I have some questions
1. in itd_slot_ok, why we have to
uframe %= period;
and use this uframe to calculate the bandwidth?
suppose start passed to itd_slot_ok is 537, period, usb->interval, is 8.
that mean we want to know whether bandwi
hi Alan:
2013/9/7 Alan Stern :
> On Sat, 7 Sep 2013, vichy wrote:
>
>> hi all:
>> when I trace linux ehci driver source code.
>> I have some questions
>> 1. in itd_slot_ok, why we have to
>> uframe %= period;
>> and use this uframe to calculate
2013/9/8 vichy :
> hi all:
> I try to do webcam audio capture on my arm platform.
> when I execute audio capture I got below message
> "retire_capture_urb: 108 callbacks suppressed"
>
> my questions:
> 1. where I can get the message "retire_capture_urb: 108 c
hi Clemens:
2013/9/9 Clemens Ladisch :
> vichy wrote:
>> I try to do webcam audio capture on my arm platform.
>> when I execute audio capture I got below message
>> "retire_capture_urb: 108 callbacks suppressed"
>
> This means that the retire_capture_urb() fun
hi Clemens:
2013/9/9 vichy :
> hi Clemens:
>
> 2013/9/9 Clemens Ladisch :
>> vichy wrote:
>>> I try to do webcam audio capture on my arm platform.
>>> when I execute audio capture I got below message
>>> "retire_capture_urb: 108 callbacks suppresse
hi Clemens:
2013/9/10 Clemens Ladisch :
> vichy wrote:
>> 2013/9/9 Clemens Ladisch :
>>> vichy wrote:
>>>> I try to do webcam audio capture on my arm platform.
>>>> when I execute audio capture I got below message
>>>> "retire_capture
hi Alan:
> > BTW, I have another question about iso_stream_schedule.
> > When if (likely (!list_empty (&stream->td_list))) happen,
> > why don't we just take last scheduled microframe, stream->next_uframe
> > as start point directly?
>
> We do exactly that if URB_ISO_ASAP isn't set. But first th
hi alan:
>> > > BTW, I have another question about iso_stream_schedule.
>> > > When if (likely (!list_empty (&stream->td_list))) happen,
>> > > why don't we just take last scheduled microframe, stream->next_uframe
>> > > as start point directly?
>> >
>> > We do exactly that if URB_ISO_ASAP isn't
hi all:
I have some questions:
1. if I need to capture all the data host capture from bus, usb mon
binary can reach this goal?
2. if #1 is Yes. from usb mon text I need
a. compile kernel with usbmon support
b. access /dev/usbmonx
c. feed the binary file to wireshark.
in b), shall we
hi alan:
2013/11/14 Alan Ott :
> On 11/14/2013 09:33 AM, vichy wrote:
>>
>> 1. if I need to capture all the data host capture from bus, usb mon
>> binary can reach this goal?
>> 2. if #1 is Yes. from usb mon text I need
>> a. compile kernel with usbmo
hi alan ott:
2013/11/14 Alan Ott :
> On 11/14/2013 09:52 AM, vichy wrote:
>>
>> hi alan:
>>
>> 2013/11/14 Alan Ott :
>>>
>>> On 11/14/2013 09:33 AM, vichy wrote:
>>>>
>>>> 1. if I need to capture all the data host capture fr
hi Alan
2013/11/14 Alan Stern :
> On Thu, 14 Nov 2013, vichy wrote:
>
>> hi all:
>> I have some questions:
>> 1. if I need to capture all the data host capture from bus, usb mon
>> binary can reach this goal?
>
> Yes.
>
>> 2. if #1 is Yes. from usb m
hi alan
2013/11/15 Alan Stern :
> On Fri, 15 Nov 2013, vichy wrote:
>
>> hi Alan
>>
>> 2013/11/14 Alan Stern :
>> > On Thu, 14 Nov 2013, vichy wrote:
>> >
>> >> hi all:
>> >> I have some questions:
>> >> 1. if I need
hi all:
My connection like below
ehci --> high speed hub -> full speed device
I have some questions about period scheduling.
1. when creating qh for full speed device, why we set EHCI_TUNE_RL_TT.
isn't it possible the full speed device return NAK during transaction?
that mean once it rea
hi Alan:
2013/12/1 Alan Stern :
> On Fri, 29 Nov 2013, vichy wrote:
>
>> hi all:
>> My connection like below
>> ehci --> high speed hub -> full speed device
>>
>> I have some questions about period scheduling.
>> 1. when creating qh for full speed
hi
2013/12/2 Alan Stern :
> On Sun, 1 Dec 2013, vichy wrote:
>
>> hi Alan:
>>
>> 2013/12/1 Alan Stern :
>> > On Fri, 29 Nov 2013, vichy wrote:
>> >
>> >> hi all:
>> >> My connection like below
>> >> ehci --> h
Hi all:
I have some questions about bandwidth calculation
1. why tt time need to include one maxp bus time ?
qh->tt_usecs = NS_TO_US (think_time +
usb_calc_bus_time (urb->dev->speed,
is_input, 0, max_packet (maxp)));
2. in tt_available, below is
Hi Alan:
2014-01-31 2:23 GMT+08:00 Alan Stern :
> On Fri, 31 Jan 2014, vichy wrote:
>
>> Hi all:
>> I have some questions about bandwidth calculation
>> 1. why tt time need to include one maxp bus time ?
>> qh->tt_usecs = NS_TO_US (think_time +
>>
hi Alan:
2014-02-07 23:40 GMT+08:00 Alan Stern :
> On Fri, 7 Feb 2014, vichy wrote:
>
>> Hi Alan:
>>
>> 2014-01-31 2:23 GMT+08:00 Alan Stern :
>> > On Fri, 31 Jan 2014, vichy wrote:
>> >
>> >> Hi all:
>> >> I have some questions ab
BTW, I know "read the source code" is the duty for everyone who wants
to know the behavior of kernel. But is there any document or map can roughly
describe the whole flowchart of usb host driver. It's really complicated to
me.
Appreciate your help,
vichy
-
To unsubscribe from th
he default and least QH to
get every device's device descriptor, right?
Appreciate your help,
vichy
-Original Message-
From: Alan Stern [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 12, 2008 1:44 AM
To: Pandita, Vikram
Cc: vichy; linux-usb@vger.kernel.org
Subject: RE: Some Quest
s to do so?
Thanks for your help,
vichy
-
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
your help,
vichy
-
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
y, it will set PORT_CSC, PORT_PEC, PORT_OCC and PORT_RESET as 0.
I can understand why we set PORT_RESET as 0, but why we set other 3
parameters as 0, too.
Thanks for your help,
vichy
-
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message t
I got it.
Thanks for your help,
vichy
-Original Message-
From: Alan Stern [mailto:[EMAIL PROTECTED]
Sent: Monday, February 25, 2008 4:58 AM
To: vichy
Cc: linux-usb@vger.kernel.org
Subject: Re: Question about port reset
On Sun, 24 Feb 2008, vichy wrote:
> Dear all:
> Below is a p
if you designed two hosts that only send the schedules
without receiving anything.
Sincerely Yours,
vichy
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of krishna prasath
Sent: Tuesday, February 26, 2008 1:57 PM
To: linux-usb@vger.kernel.org
Subject: USB
hi all:
For HW bug, we have to mdelay(100) in getting root hub port status.
But it suffer system performance.
(The place we need to add is like below)
diff --git a/drivers/usb/host/xhci-hub.c b/drivers/usb/host/xhci-hub.c
index 388cfd8..9a6b841 100644
--- a/drivers/usb/host/xhci-hub.c
+++ b/drivers
hi alan:
2014-12-19 23:20 GMT+08:00 Alan Stern :
> On Fri, 19 Dec 2014, vichy wrote:
>
>> hi all:
>> For HW bug, we have to mdelay(100) in getting root hub port status.
>
> That's quite a bug! 100 ms is a very long delay. With a bug that big,
> it's questi
hi all:
after tracing and reading kernel usb source code about run time and
normal suspend.
1. how could we check the rum time suspend is work on some device?
By plugging in devices and check whether
/sys/bus/usb/devices/.../power/ is empty or not?
2. I plug in one mouse and found the device w
2015-01-05 23:40 GMT+08:00 Alan Stern :
> On Mon, 5 Jan 2015, vichy wrote:
>
>> hi all:
>> after tracing and reading kernel usb source code about run time and
>> normal suspend.
>> 1. how could we check the rum time suspend is work on some device?
>> By p
hi alan:
2015-01-06 8:39 GMT+08:00 vichy :
> 2015-01-05 23:40 GMT+08:00 Alan Stern :
>> On Mon, 5 Jan 2015, vichy wrote:
>>
>>> hi all:
>>> after tracing and reading kernel usb source code about run time and
>>> normal suspend.
>>> 1. how could w
hi all:
2015-01-06 16:06 GMT+08:00 vichy :
> hi alan:
>
> 2015-01-06 8:39 GMT+08:00 vichy :
>> 2015-01-05 23:40 GMT+08:00 Alan Stern :
>>> On Mon, 5 Jan 2015, vichy wrote:
>>>
>>>> hi all:
>>>> after tracing and reading kernel usb source
hi Alan:
2015-01-06 23:03 GMT+08:00 Alan Stern :
> On Tue, 6 Jan 2015, vichy wrote:
>
>> I use keyboard, it should be default support runtime suspend, for
>> testing runtime suspend like the attach log.
>> insert related modules, change related suspend parameters.
&g
hi alan:
2015-01-06 23:54 GMT+08:00 Alan Stern :
> On Tue, 6 Jan 2015, vichy wrote:
>
>> >> But I cannot see the keyboard go to suspend even I force autosuspend as 0.
>> >> is there any other way to trigger runtime suspend immediately instead
>> >> of w
hi all:
usually the usb_driver is matched by usb_device_id or usb_dynids.
But there is any of them above defined in usb fs driver.
if so, what is usb fs driver used for when registered in the usb_init
of core/usb.c?
appreciate all your kine explanation in the advance,
--
To unsubscribe from this l
hi Alan:
>> 3. for host part, runtime suspend/resume is only doing port
>> suspend/resume or both host and port going to suspend/resume?
>
> Only the port. However, when _all_ the devices attached to the host
> controlluer go into runtime suspend, the controller itself will also be
> put into ru
hi alan:
>
> Firstly, you should realize that a hub port can be put into suspend
> _only_ if a device is plugged into it. If nothing is plugged into a
> port then the port cannot be put into suspend.
>
> Secondly, you should realize that putting a USB device into suspend
> means the same thing as
>> Is 3rd situation you mentioned above the function will be called is
>> hcd->bus_suspend?
>
> hcd->bus_suspend will be called first, and shortly afterward
> ehci->suspend will be called (if this is an EHCI controller).
>
>> > Fourthly, you should realize that "controller itself will also be put
>
hi Alan:
> I don't understand your question.
>
> At full speed (12 Mb/s), the time required to transfer 188 bytes is
>
> (188 bytes) * (8 bits/byte) / (12 b/us) = 125.33 us,
>
> which is greater than 125 us.
@@ -1412,7 +1412,7 @@ sitd_slot_ok (
*/
uf = uframe & 7;
hi alan:
2014-02-14 23:36 GMT+08:00 Alan Stern :
> On Fri, 14 Feb 2014, vichy wrote:
>
>> hi Alan:
>>
>> > I don't understand your question.
>> >
>> > At full speed (12 Mb/s), the time required to transfer 188 bytes is
>> >
>&
hi all:
when I plug 3g modem dongle to ehci port, it works
But when I plug in xhci port, it cannot successfully doing the modem
mode change.
The related 3G modem driver should be independent by host type, right?
Below is my host environment
and I also attach log about plug in xhci and ehci.
( as y
hi all:
from xhci spec, Interrupter Target is the value between 0 and MaxIntrs-1.
But why the parameter pass to TRB_INTR_TARGTRB_INTR_TARGET is always 0.
Does that mean so far xhci host didn't support multi-interrupt as
MSI-X suggested?
Thanks for your help in advance,
--
To unsubscribe from this
hi David:
2014-03-04 19:40 GMT+08:00 David Laight :
> From: vichy
>> hi all:
>> from xhci spec, Interrupter Target is the value between 0 and MaxIntrs-1.
>> But why the parameter pass to TRB_INTR_TARGTRB_INTR_TARGET is always 0.
>>
>> Does that mean so f
hi all:
below is the source code about setting xhci port to ss.disable state
Why we need to or PORT_PE at this time?
Spec didn't mention about to "or PORT_PE" before setting xhci port to
ss.disable state.
/* Disable port */
if (link_state == USB_SS_PO
hi Greg:
2014-03-06 22:49 GMT+08:00 Greg KH :
> On Thu, Mar 06, 2014 at 10:35:24PM +0800, vichy wrote:
>> hi sarah:
>> > Can you send me the output of `sudo lsusb -v` for when the device is
>> > under EHCI and when it's under xHCI? Also, please take a usbmon trace
hi Sarah and Greg:
2014-03-06 23:25 GMT+08:00 vichy :
> hi Greg:
>
> 2014-03-06 22:49 GMT+08:00 Greg KH :
>> On Thu, Mar 06, 2014 at 10:35:24PM +0800, vichy wrote:
>>> hi sarah:
>>> > Can you send me the output of `sudo lsusb -v` for when the device is
>&
hi all:
recently we bump to system performance issue when usb irq take quite long.
I found below link for discussing how to short
http://permalink.gmane.org/gmane.linux.usb.general/89363
I have some questions about this patch.
1. is there patch or kernel config I can use to measure man/avage usb
hi Ming.lei:
2014-03-17 22:01 GMT+08:00 Alan Stern :
> On Sun, 16 Mar 2014, vichy wrote:
>
>> hi all:
>> recently we bump to system performance issue when usb irq take quite long.
>> I found below link for discussing how to short
>>
in http://permalink.gmane.org/gm
hi all:
2014-03-19 17:57 GMT+08:00 vichy :
> hi Ming.lei:
> 2014-03-17 22:01 GMT+08:00 Alan Stern :
>> On Sun, 16 Mar 2014, vichy wrote:
>>
>>> hi all:
>>> recently we bump to system performance issue when usb irq take quite long.
>>> I found belo
hi Ming
>>
>> in http://permalink.gmane.org/gmane.linux.usb.general/89363
>>
>> I have some questions about this patch.
>> 1. is there patch or kernel config I can use to measure man/avage usb
>> irq time consuming like the above link show
>
> One approach I like to use is trace event.
Would you pl
hi Ming:
>>> One approach I like to use is trace event.
>> Would you please let us how to to use trace event for calculate
>> max/average usb irq time?
>
> You can enable irq_handler_entry and irq_handler_exit event, then
> write a script easily to figure out the time consumed in ehci irq handler,
hi all:
I list my environment as below:
1. Arm platform with ehci support
2. plug in NTFS USB HD and play movie
3. plug out device suddenly.
I found there will be possibly that driver will reset port even there
is no device connected.
I purposely add below code in ehci-hub.c when we try to do por
hi Alan:
2014-04-03 20:52 GMT+08:00 Alan Stern :
> On Thu, 3 Apr 2014, vichy wrote:
>
>> hi all:
>> I list my environment as below:
>> 1. Arm platform with ehci support
>> 2. plug in NTFS USB HD and play movie
>> 3. plug out device suddenly.
>>
>>
hi Alan:
>> Your log contains the explanation:
>>
>>> Platform-ehci Platform-ehci.0: port 1 reset
>>
>> This is where the reset starts.
>>
>>> Platform-ehci Platform-ehci.0: in port reset sequence, GetStatus
>>> port:1 status 000100 0 ACK sig=se0 RESET
>>> usb 4-1: USB disconnect, device number 20
hi Alan:
2014-04-04 8:48 GMT+08:00 Alan Stern :
> On Thu, 3 Apr 2014, vichy wrote:
>
>> I add more description.
>> in Below #1, since connect status is zero, handshake will fail with
>> return -ETIMEDOUT.
>> Then go to #2 error label.
>> and finally hub_p
hi alan:
>> Why you think it is a bug in hardware?
>
> The timeout error means that the kernel told the controller to turn off
> the PORT_RESET bit, and 1000 us later the bit was still on. That's a
> hardware bug.
after checking my hardware I found if device is no connected and do
the port reset,
hi Alan:
2014-04-07 10:06 GMT+08:00 Alan Stern :
> On Sun, 6 Apr 2014, vichy wrote:
>
>> hi alan:
>> >> Why you think it is a bug in hardware?
>> >
>> > The timeout error means that the kernel told the controller to turn off
>> > the PORT_RESET b
hi Alan:
2014-04-09 6:58 GMT+08:00 Alan Stern :
> On Tue, 8 Apr 2014, vichy wrote:
>
>> > That's a different bit. USB_PORT_FEAT_C_RESET isn't the same as
>> > USB_PORT_FEAT_RESET.
>> what I am curious is,
>> if port reset bit will clear to 0 within 2
hi all:
When I plug in usb3.0 device for stressing test, once
usb_get_device_descriptor fail in hub_port_init.
we will call hub_port_disable(hub, port1, 0);
And usb3.0 device may not recover successfully only with below function
retval = hub_port_reset(hub, port1, udev, delay, false);
when we
hi all:
When I grep "HCD_FLAG_POLL_RH",
I ave some questions:
1. why this flag only seems used by xhci, uhci, ohci except ehci?
2. it seems to setup when pcd happen and need to poll port status.
And clear it when hcd_died, hcd_remove, hcd_suspend and no port change
in hub_status_data
3. if we once
hi Greg:
> Allways run your patches through checkpatch.pl so someone doesn't point
> out the formatting issues in it when you send it to the mailing list :)
Here it is
diff --git a/drivers/usb/core/hub.c b/drivers/usb/core/hub.c
index 090469e..2192776 100644
--- a/drivers/usb/core/hub.c
+++ b/dri
0001-When-plugging-in-usb3.0-device-once-get-descriptor-o.patch has
no obvious style problems and is ready for submission.
#
From 6915f0c8be03a79df3ee8ea5aeba2d223d822e18 Mon Sep 17 00:00:00 2001
From: vichy Kuo
Date: Mon, 14 Apr 2014 10:03:15 +0800
Subject: [PATCH] When plugging in usb3.0 device, once get descriptor or set
address
hi all:
I see usb_interrupt_msg do nothing but call usb_bulk_msg.
Why we still keep usb_interrupt_msg?
for old api compatibility?
thanks for your help in advance,
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majo
hi Alan:
2014-05-22 22:14 GMT+08:00 Alan Stern :
> On Thu, 22 May 2014, vichy wrote:
>
>> hi all:
>> I see usb_interrupt_msg do nothing but call usb_bulk_msg.
>> Why we still keep usb_interrupt_msg?
>> for old api compatibility?
>
> That's right. Also bec
hi all:
I have some questions:
1. is it possible to know period bandwidth for ehci controller from
sys or other additional configuration?
2. is it possible to know S/C bit in QHs which are linked in a frame?
thanks for your help in advance,
--
To unsubscribe from this list: send the line "unsubscri
hi all:
Sorry for not making my description more clearer.
in ehci controller,
1. is it possible to know the period bandwidth in a frame from sys or
other additional configuration?
2. is it possible to know how many bits in SMASK and CMASK are
assigned to 1 in a frame?
thanks for your help in a
hi Alan:
2014-05-23 22:34 GMT+08:00 Alan Stern :
> On Fri, 23 May 2014, vichy wrote:
>
>> hi all:
>> Sorry for not making my description more clearer.
>> in ehci controller,
>> 1. is it possible to know the period bandwidth in a frame from sys or
>> oth
hi Greg:
2014-05-31 0:02 GMT+08:00 Greg KH :
> On Fri, May 30, 2014 at 11:28:36PM +0800, che-chun Kuo wrote:
>> We found when we plug in/out usb3.0 device for stress testing, once
>> usb_get_device_descriptor fail in hub_port_init, we will call
>> hub_port_disable.
>> Then usb3.0 device may not r
hi all:
I use kernel 3.8.0
And when I plug in webcam in my platform xhci host, I get below message:
platform-xhci platform-xhci.0: ERROR no room on ep ring, try ring expansion
platform-xhci platform-xhci.0: ring expansion succeed, now has 4 segments
platform-xhci platform-xhci.0: ERROR Transfer e
hi Greg:
2014-06-17 22:25 GMT+08:00 Greg KH :
> On Tue, Jun 17, 2014 at 10:07:38PM +0800, vichy wrote:
>> hi all:
>> I use kernel 3.8.0
>
> That's a very old, and unsupported kernel version. I suggest you update
Yes. it is pretty old kernel.
But i have git diff the
hi alan:
2014-08-29 22:54 GMT+08:00 Alan Stern :
> On Fri, 29 Aug 2014, vichy wrote:
>
>> hi all:
>> I have read the article below and try to do the same operation on my device.
>> http://lwn.net/Articles/143397/
>>
>> My environment:
>> 1. my kernel i
hi Greg:
2014-08-30 2:31 GMT+08:00 Greg KH :
> On Fri, Aug 29, 2014 at 11:18:39AM +0800, vichy wrote:
>> hi all:
>> I have read the article below and try to do the same operation on my device.
>> http://lwn.net/Articles/143397/
>>
>> My environment:
>> 1. my
Device
bDeviceSubClass 2 ?
bDeviceProtocol 1 Interface Association
bMaxPacketSize064
bNumConfigurations 1
Device Status: 0x
(Bus Powered)
2014-09-12 13:46 GMT+08:00 vichy :
> hi all:
> My kernel is 3.8.0.
> and when I plug in "microsoft L
hi Clements:
2014-09-12 14:41 GMT+08:00 Clemens Ladisch :
> vichy wrote:
>>> ALSA sound/usb/clock.c:237 2:3:1: cannot get freq at ep 0x82
>>> ALSA sound/usb/mixer.c:929 5:2: cannot get min/max values for control 2 (id
>>> 5)
>>> ALSA sound/usb/mixer.c
hi all:
for iso transactions, we use below function to calculate trbs
addr = (u64) (urb->transfer_dma + urb->iso_frame_desc[i].offset);
td_len = urb->iso_frame_desc[i].length;
num_trbs = DIV_ROUND_UP(td_len + (addr & (TRB_MAX_BUFF_SIZE - 1)),
TRB_MAX_B
hi David:
> Because the trb buffers can't cross a 64k physical address boundary.
Is it only specific to iso scheduling or bulk also need to take care?
from your kind explanation, the trb buffer for Bulk also need to take
care crossing 64k physical boundary.
But i don't find it for bulk transfer.
B
hi David and All:
>> > Because the trb buffers can't cross a 64k physical address boundary.
>>
>> Is it only specific to iso scheduling or bulk also need to take care?
>> from your kind explanation, the trb buffer for Bulk also need to take
>> care crossing 64k physical boundary.
>> But i don't fin
hi Mathias:
>
> In xhci-ring.c, static int xhci_queue_isoc_tx():
>
> /* Calculate TRB length */
> trb_buff_len = TRB_MAX_BUFF_SIZE - (addr & ((1 << TRB_MAX_BUFF_SHIFT) - 1));
>
> where addr = start_addr + urb->iso_frame_desc[i].offset;
>
> this limits the trb_buff_len to stop the trb buffer at
hi Mathias:
> As I understood it, it is ok to cross page boundaries as long as the buffer
> is physically contiguous. As our dma case should be.
> xhci specification section 3.2.8 says that:
>
> "Note that no constraints are placed on the TRB Length fields in a
> Scatter/Gather list. Classically
hi david:
>> platform-xhci platform-xhci.0: ERROR no room on ep ring, try ring expansion
>> platform-xhci platform-xhci.0: ring expansion succeed, now has 4 segments
>> platform-xhci platform-xhci.0: ERROR Transfer event TRB DMA ptr not
>> part of current TD
>>
>> under what circumstance the cont
hi david:
2014-06-17 23:50 GMT+08:00 David Laight :
> From: vichy
>> hi david:
>>
>> >> platform-xhci platform-xhci.0: ERROR no room on ep ring, try ring
>> >> expansion
>> >> platform-xhci platform-xhci.0: ring expansion succeed, now has 4
hi David:
2014-06-18 16:45 GMT+08:00 David Laight :
> From: vichy
>> hi david:
> ...
>> > From one of the patches (not applied) I sent last November ...
>> > Include the unknown address when the DMA pointer from an event isn't part
>> > of the curre
hi all:
when i trace xhci source, I found in skip_isoc_td, there is a
possibility to increase de-queue pointer twice.
in skip_isoc_td:
/* Update ring dequeue pointer */
while (ep_ring->dequeue != td->last_trb)
inc_deq(xhci, ep_ring);
inc_deq(xhci, ep_ring);
w
hi David:
2014-06-18 22:33 GMT+08:00 David Laight :
> From: vichy
> ...
>> and I get error message as
>> platform-xhci: ERROR Transfer event TRB DMA ptr 483702160 not part of
>> current TD
>> platform-xhci: trb_comp_code = 0x1, event status -115, buffer
>>
hi Mathias:
2014-06-24 16:38 GMT+08:00 Mathias Nyman :
> On 06/23/2014 03:44 PM, David Laight wrote:
>> From: vichy
>>> hi all:
>>> when i trace xhci source, I found in skip_isoc_td, there is a
>>> possibility to increase de-queue pointer twice.
>>>
hi all:
when I trace xhci_queue_isoc_tx, I found ISO TD should look like
ISO TRB --> Normal TRB --> Normal TRB
But when I dump ep segment during Iso transfer I get below result
1. Why most of them are ISO TRBs?
2. Why there is only 1 normal TRB
appreciate your help in advance,
ep ring segment:
p
hi Paul:
> Please read section 3.2.11 in the xHCI spec, which is freely available on
> the web.
I found what you mean.
I dump "ep context", "ep ring" and "event ring" for handling short package.
Driver prepare ep ring like below
xhci.0: @2796e150 279cfb04 000404fc 80021415 /
hi Paul:
>> Driver prepare ep ring like below
>> xhci.0: @2796e150 279cfb04 000404fc 80021415 //xx
>> xhci.0: @2796e160 279d 06f8 0625 //normal
>> xhci.0: @2796e170 279d06f8 0bf4 80021625
>>
>> but event ring g
hi Paul
My questions are
1. The xhci controller seems not handle the normal TRB for short package.
as you can see the length of event package for normal package is 0.
am I correct?
2. if above #1 is correct, how xhci controller get the left 0x6f8 data
in orig
hi Jiri:
2014-08-22 15:45 GMT+08:00 Jiri Kosina :
> On Fri, 22 Aug 2014, CheChun Kuo wrote:
>
>> HID IR device will not response to any command send from host when
>> it is finishing paring and tring to reset itself. During this period of
>> time, usb_cleaer_halt will be fail and if hid_star
hi alan and all:
> I recently posted (but did not submit) a more comprehensive solution to
> this and other related problems. For example, HID devices typically
> run at low speed or full speed. When attached through a hub to an EHCI
> controller (very common on modern systems), unplugging the d
hi all:
below patch introduce unbind and rebind interfaces during usb reset
https://lists.ubuntu.com/archives/kernel-team/2014-April/042177.html
"If a driver claims additional interfaces, the
claim may fail because the old binding instance may still own the
additional interface when the new instanc
hi Alan:
>
> I originally tried using usb_reset_device, and it caused a deadlock:
>
> Unplug the HID device.
>
> I/O error occurs. hid_io_error schedules reset_work.
>
> The reset_work callback routine is hid_reset. It calls
> usb_reset_device.
>
> The rese
hi Alan:
>> "usb_unbind_and_rebind_marked_interfaces" is called if config
>> parameter is not null,
>> it seems no matter post_reset routine fail or not.
>
> Yes, that's right. I should have said: "Because the post_reset routine
> failed, usb_unbind_and_rebind_marked_interfaces indirectly calls
>
hi Oliver:
2014-08-25 18:21 GMT+08:00 Oliver Neukum :
> On Fri, 2014-08-22 at 14:23 -0400, Alan Stern wrote:
>> On Sat, 23 Aug 2014, vichy wrote:
>>
>> > from your patch, I have some questions:
>> > a. in Alan's version, if both HID_CLEAR_HALT and HID_RESE
hi Alan:
>> After usb_reset_device, the whole enumeration will run again,
>
> No, only part of the enumeration. The kernel does read the device and
> config descriptors again. But if the reset succeeded, the kernel
> doesn't carry out any of the other parts of enumeration.
here the kernel you mea
hi all:
I have read the article below and try to do the same operation on my device.
http://lwn.net/Articles/143397/
My environment:
1. my kernel is 3.16
2. device descriptor is attached.
3. below are my operation logs:
# echo -n "4-2:1.0" > /sys/bus/usb/drivers/uas/unbind
# echo -n "4-2:1.0
hi Alan:
2015-01-19 0:49 GMT+08:00 Alan Stern :
> On Sun, 18 Jan 2015, vichy wrote:
>
>> after tracing the source, I only can find the ehci_suspend is called
>> when system hibernate/suspend.
>> rpm_suspend use below method to find out suspend callback
&
hi alan
2015-01-19 1:06 GMT+08:00 Alan Stern :
> On Sun, 18 Jan 2015, Chechun Kuo wrote:
>
>> for some platform ehci controller, it is possible there is no port power
>> control capability in the root hub.
>> And we add port power control determination when getting root hub port
>> status.
>
> W
2015-01-19 1:04 GMT+08:00 Alan Stern :
> On Sun, 18 Jan 2015, Chechun Kuo wrote:
>
>> In check_port_resume_type, we will check port power status to determine
>> whether the status should change to -ENODEV.
>> If all ports power control of the hub are handled at once, the port power
>> status may
100 matches
Mail list logo