Hello guys,
Currently i've done this in xhci-pci.c
#define PCI_VENDOR_ID_RENESAS 0x1912
#define PCI_DEVICE_ID_RENESAS_UPD720201 0x0014
if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
pdev->device == PCI_DEVICE_ID_RENESAS_UPD720201 &&
On Tue, Feb 04 2014, Robert Baldyga wrote:
> This code is an example. Don't you think it would be better to keep it
> simple?
PS. Of course another approach is to use two threads one for ep0 and the
other for transfers. Yet another, is to add AIO to ep0 in the kernel.
--
Best regards,
From: Michal Nazarewicz
> On Tue, Feb 04 2014, Robert Baldyga wrote:
> > This code is an example. Don't you think it would be better to keep it
> > simple?
>
> PS. Of course another approach is to use two threads one for ep0 and the
> other for transfers. Yet another, is to add AIO to ep0 in the
From: Sarah> Sharp
> On Wed, Feb 05, 2014 at 09:44:20AM +, David Laight wrote:
> > From: Mark Lord
> > > >> Which means that the controller is obeying the rules, and the software
> > > >> is wrong.
> > > ..
> > > > In this case, the bug has been worked around (not perfectly), but we've
> > > >
On 02/04/14 20:10, Sarah Sharp wrote:
And there's code in the xHCI driver to ignore the second successful
event. See ep->last_td_was_short. Yes, this is a slight race
condition, and we should wait for the successful event. However, we
have not seen any issues with this race condition.
Hi,
S
It seems like this function was intended to have special handling for
urb statuses of -ENOENT and -ECONNRESET. But now it just prints some
debugging and returns at the start of the function.
I have removed the dead code, it's still in the git history if anyone
wants to revive it.
Signed-off-by:
The AX88772B occasionally send rx packets that cross urb boundaries
and the remaining partial packet is sent with no header.
When the buffer with a partial packet is of less number of octets
than the value of hard_header_len the buffer is discarded by the
usbnet module. This is causing dropped pack
On Thu, 2014-02-06 at 13:56 +0100, Emil Goode wrote:
> The AX88772B occasionally send rx packets that cross urb boundaries
> and the remaining partial packet is sent with no header.
> When the buffer with a partial packet is of less number of octets
> than the value of hard_header_len the buffer i
I experienced the following WARN with a Renesas uPD720201 controller :
xhci_hcd :02:00.0: WARN Successful completion on short TX: needs
XHCI_TRUST
Adding the XHCI_NEC_HOST quirk solved the issue.
It's possible that this doesn't apply to all Renesas hosts, however it appears
they only offi
From: Emil Goode
> The AX88772B occasionally send rx packets that cross urb boundaries
> and the remaining partial packet is sent with no header.
> When the buffer with a partial packet is of less number of octets
> than the value of hard_header_len the buffer is discarded by the
> usbnet module. T
On Thu, Feb 06 2014, David Laight wrote:
> From: Michal Nazarewicz
>> On Tue, Feb 04 2014, Robert Baldyga wrote:
>> > This code is an example. Don't you think it would be better to keep it
>> > simple?
>>
>> PS. Of course another approach is to use two threads one for ep0 and the
>> other for trans
Hi Vivek,
This patch is just adding the PHY driver. I would also like to look at
some users of it, to see how this works when put together.
For now, please see my comments inline.
On 20.01.2014 14:42, Vivek Gautam wrote:
Add a new driver for the USB 3.0 PHY on Exynos5 series of SoCs.
The new
Hello David,
Thank's for the review.
On Thu, Feb 06, 2014 at 01:37:12PM +, David Laight wrote:
> From: Emil Goode
> > The AX88772B occasionally send rx packets that cross urb boundaries
> > and the remaining partial packet is sent with no header.
> > When the buffer with a partial packet is o
On Fri, Feb 07, 2014 at 12:23:19AM +1100, renev...@internode.on.net wrote:
> I experienced the following WARN with a Renesas uPD720201 controller :
>
> xhci_hcd :02:00.0: WARN Successful completion on short TX: needs
> XHCI_TRUST
>
> Adding the XHCI_NEC_HOST quirk solved the issue.
>
>
> I
From: Igor Gnatenko
> On Thu, 2014-02-06 at 13:56 +0100, Emil Goode wrote:
> > The AX88772B occasionally send rx packets that cross urb boundaries
> > and the remaining partial packet is sent with no header.
> > When the buffer with a partial packet is of less number of octets
> > than the value of
From: Daniel J Blueman
> Hi Freddy et al,
I've copied this to linux-usb.
> I'm experiencing poor network performance using an ASIX AX88179_178A
> USB3 to ethernet adapter using any recent linux kernel (eg 3.11),
> using an Intel XHCI USB3 controller.
There a several problems with the xhci driver
On Thu, Feb 06, 2014 at 01:07:25AM +0100, Gerd W. wrote:
> Dear Sirs
>
> I´ve an USB to Serial Adapter ,who works under Linux mint 16.
> I use it for control Label Printers they connect to Serial.
> Please add and set this Driver for Device 067b:2303 Prolific Technology,
> Inc. PL2303 Serial Port
On Thu, Feb 06, 2014 at 07:42:33PM +1100, renev...@internode.on.net wrote:
> Hello guys,
>
> Currently i've done this in xhci-pci.c
>
> #define PCI_VENDOR_ID_RENESAS 0x1912
> #define PCI_DEVICE_ID_RENESAS_UPD720201 0x0014
>
>
> if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
>
I have a ShuttlePRO v2 (Contour Design Inc) that identifies itself as a USB
HID. The kernel properly detects its and I can receive events from the
device. The ShuttlePRO v2 is a media controller for use with video editing
software, et cetera. It has a jog dial for frame-by-frame movement. Next, it
On Thu, Feb 06, 2014 at 03:39:02PM +, David Laight wrote:
> From: Daniel J Blueman
> > Hi Freddy et al,
>
> I've copied this to linux-usb.
>
> > I'm experiencing poor network performance using an ASIX AX88179_178A
> > USB3 to ethernet adapter using any recent linux kernel (eg 3.11),
> > using
From: Sarah Sharp
> > I have seem line rate Ge from my ax88179 card, but only with a
> > patched kernel.
>
> David, did you mean you have the same line rate as Daniel?
No I meant I've seen it saturate a Ge link (with sufficiently large frames).
With very small frames the tx rate gets limited to
From: Felipe Balbi
[ 18.606414] [] (__schedule+0x5c/0x50c) from []
(schedule_timeout+0x1f4/0x25c)
[ 18.623809] [] (schedule_timeout+0x1f4/0x25c) from []
(wait_for_common+0xc8/0x1ac)
[ 18.649291] [] (wait_for_common+0xc8/0x1ac) from []
(omap_i2c_xfer+0x338/0x488)
[ 18.674499] [] (omap_i
On Thu, Feb 06, 2014 at 09:25:37PM +0200, Ivaylo Dimitrov wrote:
> From: Felipe Balbi
I can't take a patch that the author doesn't sign off on, sorry.
Please wait a week or so so that Felipe can return from vacation.
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe
[ Please make sure to reply to all recipients including the linux-usb
list. ]
On Thu, Feb 06, 2014 at 08:23:10PM +0100, Gerd W. wrote:
> Am 06.02.2014 17:38, schrieb Johan Hovold:
> > On Thu, Feb 06, 2014 at 01:07:25AM +0100, Gerd W. wrote:
> >> Dear Sirs
> >>
> >> I´ve an USB to Serial Adapter
On Fri, 31 Jan 2014, Dan Williams wrote:
> Assume that the peer of a superspeed port is the port with the same id
> on the shared_hcd root hub. This identification scheme is required of
> external hubs by the USB3 spec [1]. However, for root hubs, tier mismatch
> may be in effect [2]. Tier mism
On Thu, 6 Feb 2014, Alan Stern wrote:
> It would also be a good idea to verify that peer->peer is NULL before
> doing these assignments.
Now I see that you did this in patch 2. Might as well do it in patch
1 instead.
> > + spin_lock(&peer_lock);
> > + if (peer) {
> > + peer->peer
On Fri, 31 Jan 2014, Dan Williams wrote:
> ACPI identifies peer ports by setting their 'group_token' and
> 'group_position' _PLD data to the same value. If a platform has tier
> mismatch [1] , ACPI can override the default, USB3 defined, peer port
> association for internal hubs. External hubs f
On Fri, 31 Jan 2014, Dan Williams wrote:
> For example:
Topic sentence? A reader seeing this could be forgiven for wondering
"Example of what?".
> usb2/2-1/2-1:1.0/port1/peer => ../../../../usb3/3-1/3-1:1.0/port1
> usb2/2-1/2-1:1.0/port2/peer => ../../../../usb3/3-1/3-1:1.0/port2
> usb2/2-1/2-1
On Fri, 31 Jan 2014, Dan Williams wrote:
> ClearPortFeature(PORT_POWER) on a usb3 port places the port in either a
> DSPORT.Powered-off-detect / DSPORT.Powered-off-reset loop, or the
> DSPORT.Powered-off state. There is no way to ensure that RX
> terminations will persist in this state, so it is
On Fri, 31 Jan 2014, Dan Williams wrote:
> Three reasons:
> 1/ It's an invalid operation on usb3 ports
> 2/ There's no guarantee of when / if a usb2 port has entered an error
>state relative to PORT_POWER request
> 3/ The port is active / powered at this point, so khubd will clear it as
>a
On Fri, 31 Jan 2014, Dan Williams wrote:
> The port pm_runtime implementation unconditionally clears FEAT_C_ENABLE
> after clearing PORT_POWER, but the bit is reserved on usb3 hub ports.
> We expect khubd to be suspended at this time so we need to clear any
> errors for usb2 ports.
I'm not sure w
Hi there,
So I have a problem in the field on kernel 3.7 which is looking more
and more like some sort of EHCI scheduler bug (very occasional
usb_submit_urb failures in snd-usb-audio wedge the entire USB stack
until reboot). Because it's only happening in the field and I cannot
repro locally (and
On Fri, 31 Jan 2014, Dan Williams wrote:
> If a port is powered-off, or in the process of being powered-off, prevent
> khubd from operating on it. Otherwise, the following sequence of events
> leading to an unintended disconnect may occur:
>
> Events:
> (0)
> (1) hub 2-2:1.0: hub_resume
> (2) h
On Thu, 6 Feb 2014, Alan Stern wrote:
> On Fri, 31 Jan 2014, Dan Williams wrote:
>
> > If a port is powered-off, or in the process of being powered-off, prevent
> > khubd from operating on it. Otherwise, the following sequence of events
> > leading to an unintended disconnect may occur:
> >
> >
On Thu, 6 Feb 2014, Devin Heitmueller wrote:
> Hi there,
>
> So I have a problem in the field on kernel 3.7 which is looking more
> and more like some sort of EHCI scheduler bug (very occasional
> usb_submit_urb failures in snd-usb-audio wedge the entire USB stack
> until reboot). Because it's o
On Thu, Feb 06, 2014 at 03:28:13PM +, David Laight wrote:
> From: Igor Gnatenko
> > On Thu, 2014-02-06 at 13:56 +0100, Emil Goode wrote:
> > > The AX88772B occasionally send rx packets that cross urb boundaries
> > > and the remaining partial packet is sent with no header.
> > > When the buffer
On Thu, Feb 6, 2014 at 12:07 PM, Alan Stern wrote:
> But come to think of it, you don't _really_ depend on the fact that the
> USB-2 root hub is registered first. What matters is that the _primary_
> hcd is registered first.
>
>> + */
>> + if (!hdev->parent) {
>> + struct usb
Hi Alan,
Thanks for the time and effort on the review, really appreciate it.
On Thu, Feb 6, 2014 at 12:07 PM, Alan Stern wrote:
> On Fri, 31 Jan 2014, Dan Williams wrote:
>
>> Assume that the peer of a superspeed port is the port with the same id
>> on the shared_hcd root hub. This identificati
On Thu, Feb 06, 2014 at 04:53:46PM +, TheDiveO wrote:
> I have a ShuttlePRO v2 (Contour Design Inc) that identifies itself as a USB
> HID. The kernel properly detects its and I can receive events from the
> device. The ShuttlePRO v2 is a media controller for use with video editing
> software, e
Ok it appears I was wrong about the NEC quirk.
Here is what i'm seeing at the moment:
The ax88179 is only working for me on the Renesas uPD720201 via a USB 3.0 HUB.
However for some reason once I use the hub I get :
xhci_hcd :02:00.0: WARN Successful completion on short TX: needs
XHCI_TRU
On Friday, February 07, 2014 11:36 AM, Peter Chen wrote:
> On Wed, Feb 05, 2014 at 10:30:35AM +0900, Jingoo Han wrote:
> > Use the wrapper function for retrieving the platform data instead
> > of accessing dev->platform_data directly. This is a cosmetic change
> > to make the code simpler and enhan
If the high-speed device does not enter full-speed idle after
wakeup on disconnect logic has effected, there will be an
unexpected disconnect wakeup interrupt due to the bus is still SE0.
Signed-off-by: Peter Chen
Hi Alan,
If you can't met this issue, it may due to your hardware enables
WKDN af
On Fri, Feb 07, 2014 at 01:11:49PM +0900, Jingoo Han wrote:
> On Friday, February 07, 2014 11:36 AM, Peter Chen wrote:
> > On Wed, Feb 05, 2014 at 10:30:35AM +0900, Jingoo Han wrote:
> > > Use the wrapper function for retrieving the platform data instead
> > > of accessing dev->platform_data direct
Dear Joe ：
I'm sorry that I reply so late, because I have just spent new
chinese year.
I will resubmit SR9800 Driver today.
Thanks a lot.
2014-02-07
liujunliang_ljl
发件人： Joe Perches
发送时间： 2014-01-28 16:59:38
收件人： liujunliang_ljl
抄送：
From: Hayes Wang
Date: Thu, 6 Feb 2014 11:55:48 +0800
> The submission of the interrupt transfer should be done after setting
> the bit of WORK_ENABLE, otherwise the callback function would have
> the opportunity to be returned directly.
>
> Clear the bit of WORK_ENABLE before killing the interr
On Wed, Feb 05, 2014 at 10:30:35AM +0900, Jingoo Han wrote:
> Use the wrapper function for retrieving the platform data instead
> of accessing dev->platform_data directly. This is a cosmetic change
> to make the code simpler and enhance the readability.
>
> Signed-off-by: Jingoo Han
> ---
> driv
On Fri, Jan 3, 2014 at 4:45 PM, Peter Chen wrote:
> We need to use gadget_is_otg to check if the gadget is really
> otg support at runtime, other composite gadget drivers have already
> followed this method.
>
> Signed-off-by: Peter Chen
> ---
> drivers/usb/gadget/printer.c |2 +-
> 1 files
On Fri, Jan 10, 2014 at 3:54 PM, Peter Chen wrote:
> We already have CONFIG_USB_OTG which can cover all CONFIG_USB_OTG_FSM
> does.
>
> Cc: Jun Li
> Cc: Anton Tikhomirov
> Signed-off-by: Peter Chen
> ---
> drivers/usb/phy/Kconfig | 11 +--
> drivers/usb/phy/Makefile |2 +-
> 2 fi
On Mon, Jan 20, 2014 at 2:48 PM, Peter Chen wrote:
>
>
>
>>
>> Hi Felipe & Shawn,
>>
>> The serial adds power management support for MXS PHY, it includes:
>>
>> - Add one PHY API .set_wakeup, and related API implementation at mxs phy
>> driver
>> - misc changes and bug fixes for mxs phy to support
ok so the nic died even via the hub now it looks like certain traffic does it.
reverting the fragment patch didnt help.
argh.
On Friday 07 February 2014 13:32:56 renev...@internode.on.net wrote:
> Ok it appears I was wrong about the NEC quirk.
>
>
> Here is what i'm seeing at the moment:
>
>
On Wed, Feb 05, 2014 at 10:30:35AM +0900, Jingoo Han wrote:
> Use the wrapper function for retrieving the platform data instead
> of accessing dev->platform_data directly. This is a cosmetic change
> to make the code simpler and enhance the readability.
>
> Signed-off-by: Jingoo Han
> ---
> driv
From: Dan Carpenter
Date: Thu, 6 Feb 2014 15:53:19 +0300
> It seems like this function was intended to have special handling for
> urb statuses of -ENOENT and -ECONNRESET. But now it just prints some
> debugging and returns at the start of the function.
>
> I have removed the dead code, it's st
On Tue, Jan 28, 2014 at 04:28:44PM +0100, Michael Grzeschik wrote:
> This patch makes it possible to set the chipidea udc into full-speed only
> mode.
> It is set by the oftree property "maximum-speed = full-speed".
>
> Signed-off-by: Michael Grzeschik
> Signed-off-by: Marc Kleine-Budde
> ---
>
On Fri, Feb 07, 2014 at 01:47:18PM +0800, Peter Chen wrote:
> On Fri, Jan 3, 2014 at 4:45 PM, Peter Chen wrote:
> > We need to use gadget_is_otg to check if the gadget is really
> > otg support at runtime, other composite gadget drivers have already
> > followed this method.
> >
> > Signed-off-by:
From: Liu Junliang
Signed-off-by: Liu Junliang
---
drivers/net/usb/Kconfig | 16 +
drivers/net/usb/Makefile |1 +
drivers/net/usb/sr9800.c | 874 ++
drivers/net/usb/sr9800.h | 202 +++
4 files changed, 1093 insertions(+)
create mode
55 matches
Mail list logo
