Re: [PATCH 2/2] usb-uas: update MAINTAINERS entry
On Fri, Jan 25, 2013 at 04:32:16PM -0800, Sarah Sharp wrote: > On Fri, Jan 25, 2013 at 03:19:22PM +0100, Gerd Hoffmann wrote: > > Hi, > > > > >> diff --git a/MAINTAINERS b/MAINTAINERS > > >> index 8ae709e..c5b37de 100644 > > >> --- a/MAINTAINERS > > >> +++ b/MAINTAINERS > > >> @@ -7911,9 +7911,10 @@ F:drivers/net/wireless/ath/ar5523/ > > >> USB ATTACHED SCSI > > >> M: Matthew Wilcox > > >> M: Sarah Sharp > > >> +M: Gerd Hoffmann > > > > > > Should Matthew be removed from this? > > > > Dunno, Sarah? > > Matthew has said he doesn't have time to work on UAS, so I would suggest > removing him. Can someone send me a patch doing this please? thanks, greg k-h -- 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 http://vger.kernel.org/majordomo-info.html
Re: [PATCH 2/2] usb-uas: update MAINTAINERS entry
Hi, >> Problem is that uas is pretty much the only device using streams, >> so uas will be the one who triggers any stream bugs in xhci. >> I have no idea how solid xhci streams support is at the moment. > > The xHCI streams support isn't well tested, because the UAS devices I > had were so buggy that I couldn't fully test them, and the UAS driver > didn't (doesn't still?) properly support cancellation or device reset. There have been a number of improvements fixes there, it should do alot better now. > Also, I do know there are a couple of streams work-arounds that need to > be created for the Intel Panther Point xHCI host controller, so I would > suggest testing with an NEC/Renesas xHCI host instead. I will get > around to implementing them, but other bugs have taken a higher > priority. Hmm. I have a nec xhci for that, but streams not working on Intel pretty much blocks removing the BROKEN tag from uas :( cheers, Gerd -- 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 http://vger.kernel.org/majordomo-info.html
Re: [PATCH 2/2] usb-uas: update MAINTAINERS entry
On Fri, Jan 25, 2013 at 03:19:22PM +0100, Gerd Hoffmann wrote: > Hi, > > >> diff --git a/MAINTAINERS b/MAINTAINERS > >> index 8ae709e..c5b37de 100644 > >> --- a/MAINTAINERS > >> +++ b/MAINTAINERS > >> @@ -7911,9 +7911,10 @@ F: drivers/net/wireless/ath/ar5523/ > >> USB ATTACHED SCSI > >> M:Matthew Wilcox > >> M:Sarah Sharp > >> +M:Gerd Hoffmann > > > > Should Matthew be removed from this? > > Dunno, Sarah? Matthew has said he doesn't have time to work on UAS, so I would suggest removing him. > > Also, any word on when I can remove the CONFIG_BROKEN marking on this > > driver? > > With the patches in -next uas itself should be reasonable solid. > > Problem is that uas is pretty much the only device using streams, > so uas will be the one who triggers any stream bugs in xhci. > I have no idea how solid xhci streams support is at the moment. The xHCI streams support isn't well tested, because the UAS devices I had were so buggy that I couldn't fully test them, and the UAS driver didn't (doesn't still?) properly support cancellation or device reset. So the first SCSI command that the device didn't like basically hung the driver. Also, I do know there are a couple of streams work-arounds that need to be created for the Intel Panther Point xHCI host controller, so I would suggest testing with an NEC/Renesas xHCI host instead. I will get around to implementing them, but other bugs have taken a higher priority. > Sarah, is there some way to avoid using streams? The UAS specs seems to > imply using streams is mandatory when connected to a USB-3 port, is that > correct? Is there some way to force usb3 devices into usb2 mode even > when plugged into a usb3 port? I'd like to have a no_streams module > option if possible ... USB 3.0 UAS devices are really supposed to be using streams. You might as well just use Bulk-only-Transport (BoT) if you're not using streams. As for forcing a USB 3.0 port to USB 2.0 speeds, I think you could write a userspace program to use usbfs to disable the USB 3.0 port. I've never tried it though. 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 http://vger.kernel.org/majordomo-info.html
Re: [PATCH 2/2] usb-uas: update MAINTAINERS entry
On Fri, Jan 25, 2013 at 04:04:33PM +0100, Gerd Hoffmann wrote: > > Oh, and any hints on what device on the market today actually follows > > the UAS spec so I can buy one for testing? > > /me asked the same a while ago, here is the reply > > > > I would suggest getting a TI UAS evaluation board. They seem to be the > most stable UAS device out there: > > http://www.ti.com/tool/tusb9261demo > > I have one of their boards from a year or so ago, but I suspect there's > a new revision by now. I got the sample from Kevin Main , > and I suspect he might give you one for free as well. Ah, I already have one of these somewhere, I was wondering if there were devices you could buy on the market just yet. I guess not, which is fine. thanks, greg k-h -- 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 http://vger.kernel.org/majordomo-info.html
Re: [PATCH 2/2] usb-uas: update MAINTAINERS entry
Hi, >> Sarah, is there some way to avoid using streams? The UAS specs seems to >> imply using streams is mandatory when connected to a USB-3 port, is that >> correct? Is there some way to force usb3 devices into usb2 mode even >> when plugged into a usb3 port? I'd like to have a no_streams module >> option if possible ... > > Well, I think we want to use streams, that's the whole advantage of UAS > over the old spec. Sure, but being able to turn them off for trouble-shooting purposes would still be useful IMO. > I wasn't aware that the bugs were in the xhci > driver, I thought they were in the uas driver, but I could be totally > wrong. Oh, uas had bugs too, pretty serious ones included, no question. > Oh, and any hints on what device on the market today actually follows > the UAS spec so I can buy one for testing? /me asked the same a while ago, here is the reply I would suggest getting a TI UAS evaluation board. They seem to be the most stable UAS device out there: http://www.ti.com/tool/tusb9261demo I have one of their boards from a year or so ago, but I suspect there's a new revision by now. I got the sample from Kevin Main , and I suspect he might give you one for free as well. Another option might be to use the Linux UAS gadget stack with a OMAP5 board with the Synopsis Designware 3 USB 3.0 device controller. You could talk with Sebastian Andrzej Siewior , since he has been doing a lot of work on the UAS gadget driver lately. cheers, Gerd -- 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 http://vger.kernel.org/majordomo-info.html
Re: [PATCH 2/2] usb-uas: update MAINTAINERS entry
On Fri, Jan 25, 2013 at 03:19:22PM +0100, Gerd Hoffmann wrote: > Hi, > > >> diff --git a/MAINTAINERS b/MAINTAINERS > >> index 8ae709e..c5b37de 100644 > >> --- a/MAINTAINERS > >> +++ b/MAINTAINERS > >> @@ -7911,9 +7911,10 @@ F: drivers/net/wireless/ath/ar5523/ > >> USB ATTACHED SCSI > >> M:Matthew Wilcox > >> M:Sarah Sharp > >> +M:Gerd Hoffmann > > > > Should Matthew be removed from this? > > Dunno, Sarah? > > > Also, any word on when I can remove the CONFIG_BROKEN marking on this > > driver? > > With the patches in -next uas itself should be reasonable solid. > > Problem is that uas is pretty much the only device using streams, > so uas will be the one who triggers any stream bugs in xhci. > I have no idea how solid xhci streams support is at the moment. > > Sarah, is there some way to avoid using streams? The UAS specs seems to > imply using streams is mandatory when connected to a USB-3 port, is that > correct? Is there some way to force usb3 devices into usb2 mode even > when plugged into a usb3 port? I'd like to have a no_streams module > option if possible ... Well, I think we want to use streams, that's the whole advantage of UAS over the old spec. I wasn't aware that the bugs were in the xhci driver, I thought they were in the uas driver, but I could be totally wrong. Oh, and any hints on what device on the market today actually follows the UAS spec so I can buy one for testing? thanks, greg k-h -- 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 http://vger.kernel.org/majordomo-info.html
Re: [PATCH 2/2] usb-uas: update MAINTAINERS entry
Hi, >> diff --git a/MAINTAINERS b/MAINTAINERS >> index 8ae709e..c5b37de 100644 >> --- a/MAINTAINERS >> +++ b/MAINTAINERS >> @@ -7911,9 +7911,10 @@ F:drivers/net/wireless/ath/ar5523/ >> USB ATTACHED SCSI >> M: Matthew Wilcox >> M: Sarah Sharp >> +M: Gerd Hoffmann > > Should Matthew be removed from this? Dunno, Sarah? > Also, any word on when I can remove the CONFIG_BROKEN marking on this > driver? With the patches in -next uas itself should be reasonable solid. Problem is that uas is pretty much the only device using streams, so uas will be the one who triggers any stream bugs in xhci. I have no idea how solid xhci streams support is at the moment. Sarah, is there some way to avoid using streams? The UAS specs seems to imply using streams is mandatory when connected to a USB-3 port, is that correct? Is there some way to force usb3 devices into usb2 mode even when plugged into a usb3 port? I'd like to have a no_streams module option if possible ... cheers, Gerd -- 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 http://vger.kernel.org/majordomo-info.html
Re: [PATCH 2/2] usb-uas: update MAINTAINERS entry
On Fri, Jan 25, 2013 at 02:52:09PM +0100, Gerd Hoffmann wrote: > Cc: Sarah Sharp > Signed-off-by: Gerd Hoffmann > --- > MAINTAINERS |3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/MAINTAINERS b/MAINTAINERS > index 8ae709e..c5b37de 100644 > --- a/MAINTAINERS > +++ b/MAINTAINERS > @@ -7911,9 +7911,10 @@ F: drivers/net/wireless/ath/ar5523/ > USB ATTACHED SCSI > M: Matthew Wilcox > M: Sarah Sharp > +M: Gerd Hoffmann Should Matthew be removed from this? Also, any word on when I can remove the CONFIG_BROKEN marking on this driver? greg k-h -- 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 http://vger.kernel.org/majordomo-info.html
[PATCH 2/2] usb-uas: update MAINTAINERS entry
Cc: Sarah Sharp Signed-off-by: Gerd Hoffmann --- MAINTAINERS |3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/MAINTAINERS b/MAINTAINERS index 8ae709e..c5b37de 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -7911,9 +7911,10 @@ F: drivers/net/wireless/ath/ar5523/ USB ATTACHED SCSI M: Matthew Wilcox M: Sarah Sharp +M: Gerd Hoffmann L: linux-usb@vger.kernel.org L: linux-s...@vger.kernel.org -S: Supported +S: Maintained F: drivers/usb/storage/uas.c USB CDC ETHERNET DRIVER -- 1.7.9.7 -- 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 http://vger.kernel.org/majordomo-info.html
