[<prev] [next>] [day] [month] [year] [list]
Message-ID: <063D6719AE5E284EB5DD2968C1650D6D0F6B5460@AcuExch.aculab.com>
Date: Thu, 30 Jan 2014 15:59:48 +0000
From: David Laight <David.Laight@...LAB.COM>
To: "linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Sarah Sharp <sarah.a.sharp@...ux.intel.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
David Miller <davem@...emloft.net>
Subject: [PATCH RFC 0/1] usb: Tell xhci when usb data might be misaligned
I've marked this as RFC because I'm not sure whether this should
go through the usb tree or netdev.
I'm also not 100% sure that the code that generates a urb should
'know' the entire aligment rules of the host controller.
However this was already done when the flag was added to indicate
that 'unconstrained' fragmentation was supported by xhci.
This patch fixes problems with long scatter-gather lists on xhci bulk
endpoints by removing the limit on the number of entries and requesting
that the code that generates urb mark those that might have misaligned
fragments - which need special treatment.
The xhci driver cannot give a simple limit to the number of fragments
in a non-aligned transfer because it has to further split the fragments
on 64k address boundaries.
The only code (I can find) that currently generates non-aligned tranfers
is in usbnet.
It is important that all these patches be applied together.
More specifically the change xhci-ring.c must be applied AFTER the
change to usbnet.c.
Failure to do so will break some configurations including those using
the ax88179_178a usb ethernet on hosts with the Intel Panther Point
chipset (which I think is the newest one).
David Laight (1):
usb: Tell xhci when usb data might be misaligned
drivers/net/usb/usbnet.c | 1 +
drivers/usb/host/xhci-ring.c | 12 ++++++++----
drivers/usb/host/xhci.c | 8 ++++++--
include/linux/usb.h | 1 +
4 files changed, 16 insertions(+), 6 deletions(-)
--
1.8.1.2
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists