On Tue, Feb 16, 2016 at 10:43 PM, Anil Nair wrote:
> Hi,
>
> On Wed, Feb 17, 2016 at 12:00 PM, Greg KH wrote:
>> On Wed, Feb 17, 2016 at 11:47:56AM +0530, Anil Nair wrote:
>>> Hi All,
>>>
>>> I would like to contribute to Linux USB kernel but i am confused on
>>> where to start,
>>
>> If you don'
On Wed, Nov 6, 2013 at 12:33 PM, wrote:
>> On Wed, Nov 6, 2013 at 12:53 AM, wrote:
>>> Hi
>>>
>>> By performing iterative port suspend and resume (which results in
>>> function
>>> suspend and resume), ring expansion failure is observed. Attached device
>>> has multiple interfaces for which int
On Wed, Nov 6, 2013 at 12:53 AM, wrote:
> Hi
>
> By performing iterative port suspend and resume (which results in function
> suspend and resume), ring expansion failure is observed. Attached device
> has multiple interfaces for which interface host drivers are unlinking the
> urbs during functio
On Tue, Nov 5, 2013 at 6:21 AM, David Laight wrote:
>
> Close inspection shows that xhci_queue_isoc_tx() can only fail if
> prepare_transfer() gets an error from usb_hcd_link_urb_to_ep() for
> the first TD. The call to prepare_ring() cannot fail because an initial
> check is made to ensure the rin
On Mon, Oct 21, 2013 at 11:40 AM, Alan Stern wrote:
> On Sat, 19 Oct 2013, Andiry Xu wrote:
>
>> Hi Sarah, nice to see you again:) I'm still working on my PhD degree
>> at UC San Diego. I'm working with storage devices on Linux, but not on
>> driver. With fast
On Sat, Oct 19, 2013 at 9:45 PM, Sarah Sharp
wrote:
> On Sat, Oct 19, 2013 at 03:36:58PM -0400, Alan Stern wrote:
>> On Fri, 18 Oct 2013, Andiry Xu wrote:
>>
>> > Interesting. I used the following commands:
>> >
>> > #echo disabled > /sys/bus/pci
On Fri, Oct 18, 2013 at 3:06 PM, Alan Stern wrote:
> On Fri, 18 Oct 2013, Andiry Xu wrote:
>
>> On Wed, Oct 16, 2013 at 9:14 AM, Alan Stern
>> wrote:
>> > Sarah:
>> >
>> > While working on some general fixes for wakeup races during PCI
>> >
On Wed, Oct 16, 2013 at 9:14 AM, Alan Stern wrote:
> Sarah:
>
> While working on some general fixes for wakeup races during PCI
> suspend, I noticed that xhci_pci_suspend() ignores its do_wakeup
> argument. What's the story?
>
I believe it's simply because I don't know how to handle the argument
On Tue, Sep 25, 2012 at 2:19 PM, Sarah Sharp
wrote:
> On Tue, Sep 25, 2012 at 09:26:00AM +0300, Adrian Sandu wrote:
>> On Tue, Sep 25, 2012 at 12:38 AM, Sarah Sharp
>> wrote:
>> > Ok, so 3.4.11 doesn't work, and the log file was from 3.5.
>>
>> If you want I can provide a 3.4 log...
>
> Hmm, does
On Mon, Sep 24, 2012 at 3:35 PM, Sarah Sharp
wrote:
> On Mon, Sep 24, 2012 at 01:05:08PM -0700, Sarah Sharp wrote:
>> On Mon, Sep 24, 2012 at 03:50:04PM -0400, Alan Stern wrote:
>> > On Mon, 24 Sep 2012, Sarah Sharp wrote:
>> >
>> > > When a device with an isochronous endpoint is behind a hub plug
On Wed, Aug 29, 2012 at 6:53 AM, loody wrote:
> hi all:
> I saw there are 2 trbs about bandwidth as below:
>
> #define TRB_GET_BW 21
> #define TRB_BANDWIDTH_EVENT 35
>
> Would any one tell me where I can see driver use these 2 trbs for
> bandwidth checking,
> since I cannot grep the i
On Thu, Aug 23, 2012 at 12:53 AM, wrote:
> From: Manoj Iyer
>
> On Intel Panther Point chipset USB 3.0 devices show up as
> high-speed devices on powerup, but after an s3 cycle they are
> correctly recognized as SuperSpeed. At powerup switch the port
> to xHCI so that USB 3.0 devices are correct
On Fri, Aug 24, 2012 at 7:16 PM, Sami Farin wrote:
> On Sun, Jul 15, 2012 at 11:14:13 -0400, Alan Stern wrote:
> ...
>> In past years I have found that Genesys's devices tend to be rather
>> buggy. This card reader continues the tradition. Basically, although
>> the firmware works reasonably wel
On Wed, Aug 22, 2012 at 7:30 PM, Miroslav Sabljic
wrote:
> On 08/21/2012 01:33 PM, Andiry Xu wrote:
>
>>> Not sure. it's hard to debug via software side because software seems
>>> does not do anything wrong. If you disable USB3 support in BIOS the
>>> port
a
better solution than your original patch.
Thanks,
Andiry
>
> On Tue, 21 Aug 2012, Andiry Xu wrote:
>
>> On Tue, Aug 21, 2012 at 12:06 PM, wrote:
>>>
>>> From: Manoj Iyer
>>>
>>> USB 3.0 devices show up as high-speed devices on powerup
rt - Works fine.
> 4. USB 2.0 Device on 2.0 port - Works fine.
> 5. USB 2.0 Device on SS hub on 3.0 port - Works fine.
> 6. USB 2.0 Device on 2.0 hub on 3.0 port - Works fine.
> 7. USB 3.0 Device on 2.0 hub on 3.0 port - Works fine.
> 8. USB 3.0 Device on SS hub on 2.0 port - Wo
On Tue, Aug 21, 2012 at 12:06 PM, wrote:
> From: Manoj Iyer
>
> USB 3.0 devices show up as high-speed devices on powerup, after an
> s3 cycle they are correctly recognized as SuperSpeed. At powerup
> unconditionally switch the port to xHCI like we do when we resume
> from suspend.
>
> BugLink: h
Adding Linux-USB back..
On Tue, Aug 21, 2012 at 7:31 PM, Andiry Xu wrote:
> On Mon, Aug 20, 2012 at 8:17 PM, Miroslav Sabljic
> wrote:
>> On 08/19/2012 03:29 PM, Andiry Xu wrote:
>>
>>> Thanks. The dmesg indicates the device does not respond the address
>>>
On Tue, Aug 21, 2012 at 3:46 AM, Arnaud René Ober
wrote:
> On 08/20/2012 09:39 PM, Alan Stern wrote:
>>
>> Please use Reply-To-All so that your messages get sent to the mailing
>> list as well as to me.
>>
>> On Sun, 19 Aug 2012, Arnaud René Ober wrote:
>>
>>> On 08/19/2012 03:53 PM, Alan Stern wr
On Sun, Aug 19, 2012 at 6:13 PM, Dr. Ing. Dieter Jurzitza
wrote:
> Dear Andiry,
> I do not know wether or not you received this email as you quit from AMD and I
> accidentally lost your new email address when the reply came in
> If you find the time to look further into this I would be very h
On Sat, Aug 18, 2012 at 8:16 PM, Miroslav Sabljic
wrote:
> On 08/18/2012 12:33 PM, Andiry Xu wrote:
>
>>> From the dmesg, it looks like your xhci host controller is in a mess.
>>
>> It either does not respond to the address device command, or just
>> return an
On Fri, Aug 17, 2012 at 10:58 PM, Miroslav Sabljic
wrote:
> Hi all!
>
> I'm not sure is this the right place to make this question so please point
> me to correct place and I will resend my question.
>
> I'm having problems with latest kernel v3.6-rc1. I'm using Ubuntu 12.04 with
> latest updates,
On 07/13/2012 10:41 PM, Matt Causey wrote:
On Fri, Jul 13, 2012 at 7:13 AM, Andiry Xu wrote:
On 07/13/2012 09:56 AM, Matt Causey wrote:
On Thu, Jul 12, 2012 at 12:54 PM, Matt Causey
wrote:
On Thu, Jul 12, 2012 at 2:04 AM, Andiry Xu wrote:
On 07/12/2012 10:53 AM, Matt Causey wrote
t solution is to use another SS hub which
passes USB-IF certification.
Thanks,
Andiry
--- Original Message ---
Sender : Andiry Xu
Date : Jul 13, 2012 17:11 (GMT+09:00)
Title : Re: usb 2.0 device connected on Super Speed HUB on USB 3.0 Port throws
error during enumeration on 3.4 k
with the following two scnearios:
1. xHCI root hub --- SS hub --- some other USB 2.0 devices
2. xHCI root hub --- some other SS hub or HS hub --- the same USB2.0 device
Thanks,
Andiry
--- Original Message ---
Sender : Andiry Xu
Date : Jul 13, 2012 16:29 (GMT+09:00)
Title : Re: usb
On 07/13/2012 02:49 PM, VIKAS SAJJAN C wrote:
Hi ,
I am working on 3.4 kernel , when i try to connect a USB 2.0 device on Super
Speed HUB , i get following error.
usb 3-1.1: Device not responding to set address.
usb 3-1.1: device not accepting address 3, error -71
any inputs will be of great h
On 07/13/2012 03:19 AM, Dr. Ing. Dieter Jurzitza wrote:
Hi Andiry, hi Sarah,
Andiry is right, the test patch was applied. Please advise what I can do on
top of this ...
Thank you for all your time and all your efforts,
take care
Sarah,
What do you suggest? What should we do with a interrupt
On 07/13/2012 12:26 AM, Richard Adams wrote:
Hi,
I've recently been doing some development work with the latest Linux
Kernel (3.4& 3.5rc6) and I'm experiencing problems with USB3 on both.
I've been in conversation with the developers at gphoto and they've
directed me to you?
1) The problem oc
On 07/13/2012 09:56 AM, Matt Causey wrote:
On Thu, Jul 12, 2012 at 12:54 PM, Matt Causey wrote:
On Thu, Jul 12, 2012 at 2:04 AM, Andiry Xu wrote:
On 07/12/2012 10:53 AM, Matt Causey wrote:
On Wed, Jul 11, 2012 at 11:03 AM, Matt Causey
wrote:
On Wed, Jul 11, 2012 at 10:12 AM, Matt Causey
On 07/12/2012 01:47 AM, Dr. Ing. Dieter Jurzitza wrote:
Dear Sarah,
dear Andiry,
as I do not know wheter or not attachements to emails are tolerated in the
mailing list, I send this directly to you - please advise if I'd send that
somewhere else.
Please find attached the result of dmesg after log
On 07/12/2012 10:53 AM, Matt Causey wrote:
On Wed, Jul 11, 2012 at 11:03 AM, Matt Causey wrote:
On Wed, Jul 11, 2012 at 10:12 AM, Matt Causey wrote:
On Tue, Jul 10, 2012 at 10:55 PM, Andiry Xu wrote:
On 07/11/2012 01:56 AM, Matt wrote:
Lee Harris writes:
Hi Sarah
Whenever I
On 07/11/2012 03:37 AM, Dr. Ing. Dieter Jurzitza wrote:
Dear listmembers,
dear Sarah, dear Andiry,
Andiry's suggestion (uncomment the return 0 - statement) fixed my issue, the
usb soundcard remains active after a login-logout; however, as I understood
Sarah's comment this is no more than a plaste
On 07/11/2012 01:56 AM, Matt wrote:
Lee Harris writes:
Hi Sarah
Whenever I restart or coldboot, my external drive (3.5 sata in a USB3
enclosure) is not detected / initialised correctly. fdisk -l does not
show the drive at all.
I have found that I have to:
turn it off ( or disconnect the usb
On 07/08/2012 08:50 PM, Dr. Ing. Dieter Jurzitza wrote:
Dear listmembers,
recently I switched to a new pc, making use of an external USB sound device.
The problem: when I log off a kde-session and log in again, the sound device
vanishes. Issuing dmesg, I see:
On 07/06/2012 10:11 AM, Sarah Sharp wrote:
Some xHCI host controllers may have optional support for Latency
Tolerance Messaging (LTM). This allows USB 3.0 devices that support LTM
to pass information about how much latency they can tolerate to the xHC.
A PCI xHCI host will use this information t
35 matches
Mail list logo
