From: Hayes Wang
Date: Wed, 14 Aug 2013 20:54:39 +0800
> Enable tx checksum.
>
> Signed-off-by: Hayes Wang
Applied.
--
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/major
From: Hayes Wang
Date: Wed, 14 Aug 2013 20:54:40 +0800
> Use the interrupt transfer to replace polling link status.
>
> Signed-off-by: Hayes Wang
Applied.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordom
From: Hayes Wang
Date: Wed, 14 Aug 2013 20:54:38 +0800
> Enable the tx/rx aggregation which could contain one or more packets
> for each bulk in/out. This could reduce the loading of the host
> controller by sending less bulk transfer.
>
> The rx packets in the bulk in buffer should be 8-byte al
On 08/14/2013 06:27 PM, Philipp Zabel wrote:
> Hi Roger,
>
> Am Mittwoch, den 14.08.2013, 16:58 +0300 schrieb Roger Quadros:
>> Modelling the RESET line as a regulator supply wasn't a good idea
>> as it kind of abuses the regulator framework and also makes adaptation
>> code more complex.
>>
>> In
Peter Hyman writes:
> On 08/14/2013 01:42 PM, Bjørn Mork wrote:
> snip...
>
>> Great! And if you can snoop on Windows trying to figure out how to
>> switch the modes, then that would also help. I believe Wireshark with
>> usbpcap is the current state-of-the-art USB sniffer for Windows:
>> http:
Quoting Bjørn Mork :
snip...
>
> Thanks. The lsusb outputs show that there are no descriptor differences
> between the two modes. The diff you see is only the device address,
> which is a dynamic property and expected to change every time you plug
> in a device.
>
> Unfortunately there is a larg
Use a common naming scheme "mode0name.modename flags" for the
USB host pins to be consistent.
Signed-off-by: Roger Quadros
---
arch/arm/boot/dts/omap3-beagle.dts | 24
1 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/arch/arm/boot/dts/omap3-beagle.dts
The USB phy-nop nop driver expects the RESET line information
to be sent as a GPIO number via platform data. Adapt to that.
Signed-off-by: Roger Quadros
---
arch/arm/mach-omap2/usb-host.c | 11 +--
1 files changed, 1 insertions(+), 10 deletions(-)
diff --git a/arch/arm/mach-omap2/usb-
We no longer need to model the RESET line as a regulator since
the USB phy-nop driver accepts "reset-gpios" property.
Signed-off-by: Roger Quadros
---
arch/arm/boot/dts/omap4-panda-common.dtsi | 18 +-
1 files changed, 1 insertions(+), 17 deletions(-)
diff --git a/arch/arm/boo
Provide RESET GPIO and Power regulator for the USB PHY,
the USB Host port mode and the PHY device for the controller.
Also provide pin multiplexer information for USB host pins.
We also relocate omap3_pmx_core pin definations so that they
are close to omap3_pmx_wkup pin definations.
Signed-off-by
We no longer need to model the RESET line as a regulator since
the USB phy-nop driver accepts "reset-gpios" property.
Signed-off-by: Roger Quadros
---
arch/arm/boot/dts/omap5-uevm.dts | 13 +
1 files changed, 1 insertions(+), 12 deletions(-)
diff --git a/arch/arm/boot/dts/omap5-ue
Modelling the RESET line as a regulator supply wasn't a good idea
as it kind of abuses the regulator framework and also makes adaptation
code more complex.
Instead, manage the RESET gpio line directly in the driver. Update
the device tree binding information.
This also makes us easy to migrate to
We no longer need to model the RESET line as a regulator since
the USB phy-nop driver accepts "reset-gpios" property.
Signed-off-by: Roger Quadros
---
arch/arm/boot/dts/omap3-beagle.dts | 13 +
1 files changed, 1 insertions(+), 12 deletions(-)
diff --git a/arch/arm/boot/dts/omap3-
The platform data bits can be inferred from the other members of
struct usbhs_phy_data. So get rid of the platform_data member.
Build the platform data for the PHY device in usbhs_init_phys() instead.
Signed-off-by: Roger Quadros
---
arch/arm/mach-omap2/board-omap3beagle.c |6 --
arch/a
The GPIO number of the RESET line can be passed to the
driver using the gpio_reset member.
Signed-off-by: Roger Quadros
---
include/linux/usb/nop-usb-xceiv.h |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/include/linux/usb/nop-usb-xceiv.h
b/include/linux/usb/nop-usb
Hi,
Modelling the RESET line as a regulator supply wasn't a good idea
as it abuses the regulator framework and makes adaptation
code/data more complex.
Instead, manage the RESET gpio line directly in the driver.
This also makes us easy to migrate to a dedicated GPIO RESET controller
whenever it
* Sergei Shtylyov | 2013-08-14 22:39:49 [+0400]:
>Hello.
Hello Sergei,
> Perhaps it's worth documenting the "mg" prefix in
>Documentation/devicetree/bindings/vendor-prefixes.txt if it's
>official?
Okay, I sent a separate patch for this.
+- power : Should be "250". This signifies the contr
Hi,
On 08/14/2013 08:21 PM, Greg KH wrote:
On Wed, Aug 14, 2013 at 02:32:01PM +0200, Hans de Goede wrote:
Hi All,
As discussed a long while back, usbfs is currently missing bulk streams
support, and we ought to fix this. So this patch extends the usbfs API with
bulk stream support. Please revi
On Wed, Jul 31, 2013 at 05:29:40PM -0600, Stephen Warren wrote:
> On 07/31/2013 04:20 PM, Sergei Shtylyov wrote:
> > On 08/01/2013 02:06 AM, Stephen Warren wrote:
> ...
> >>> That's really horrible design.
> >>
> >> Yup. Both USB PHY and EHCI controller registers really are interleaved
> >> in
We should not use extra variable just to copy pointer value,
renaming parameter name serves pupose & removes extra variable.
Signed-off-by: Rupesh Gujare
---
drivers/staging/ozwpan/ozhcd.c |3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/staging/ozwpan/ozhcd.c b/d
We are assigning value to hport before returning, there is
no need to initialize it.
Signed-off-by: Rupesh Gujare
---
drivers/staging/ozwpan/ozhcd.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/ozwpan/ozhcd.c b/drivers/staging/ozwpan/ozhcd.c
index 4cd08d
Hayes Wang :
[...]
> diff --git a/drivers/net/usb/r8152.c b/drivers/net/usb/r8152.c
> index 11c51f2..abb0b9f 100644
> --- a/drivers/net/usb/r8152.c
> +++ b/drivers/net/usb/r8152.c
[...]
> @@ -315,13 +318,34 @@ struct tx_desc {
> u32 opts2;
> };
>
> +struct rx_agg {
> + struct list_hea
The support for both am335x-USB instances required changes to the device
tree bindings. This patch reflects these changes in the bindings
document.
v1…v2:
- use mg prefix for the Metor Graphics specific attributes
- use power in mA not in mA/2 as specifed in the USB2.0 specification
- use usbX-phy
This prefix is currently used for the musb driver.
Cc: Rob Herring
Cc: Pawel Moll
Cc: Mark Rutland
Cc: Stephen Warren
Cc: Ian Campbell
Cc: devicet...@vger.kernel.org
Signed-off-by: Sebastian Andrzej Siewior
---
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 i
This relfects the code and dts requires changes due to recent .dts
binding updates:
- use mg prefix for the Metor Graphics specific attributes
- use power in mA not in mA/2 as specifed in the USB2.0 specification
Signed-off-by: Sebastian Andrzej Siewior
---
arch/arm/boot/dts/am33xx.dtsi | 24 +++
omap-control device is present from OMAP4 onwards which
support device tree boots only. So get rid of platform data.
Signed-off-by: Roger Quadros
---
drivers/usb/phy/phy-omap-control.c | 18 +++---
include/linux/usb/omap_control_usb.h |4
2 files changed, 7 insertions(+)
Hi,
This patchset does the following:
* Get rid of omap_control_usb platform data as we support DT only.
* Restructure and add support for new PHY types. We now support the follwing
four types
TYPE_OMAP - if it has otghs_control mailbox register (e.g. on OMAP4)
TYPE_USB2 - if it has Power dow
omap_get_control_dev() is being deprecated as it doesn't support
multiple instances. As control device is present only from OMAP4
onwards which supports DT only, we use phandles to get the
reference to the control device.
As we don't support non-DT boot, we just bail out on probe
if device node is
This function was preventing us from supporting multiple
instances. Get rid of it. Since we support DT boots only,
users can get the control device phandle from the DT node.
Signed-off-by: Roger Quadros
---
drivers/usb/phy/phy-omap-control.c | 31 ++-
include/linu
omap_get_control_dev() is being deprecated as it doesn't support
multiple instances. As control device is present only from OMAP4
onwards which supports DT only, we use phandles to get the
reference to the control device.
As we don't support non-DT boot, we just bail out on probe
if device node is
Add support for new device types and in the process rid of "ti,type"
device tree property. The correct type of device will be determined
from the compatible string instead.
Introduce a compatible string for each device type. At the moment
we support 4 types Mailbox, USB2, USB3 and DRA7.
Update DT
Split otghs_ctrl and USB2 PHY power down into separate
omap-control-usb nodes. Get rid of "ti,type" property.
CC: Benoit Cousson
Signed-off-by: Roger Quadros
---
arch/arm/boot/dts/omap4.dtsi | 17 +++--
1 files changed, 11 insertions(+), 6 deletions(-)
diff --git a/arch/arm/boot/
omap_get_control_dev() is being deprecated as it doesn't support
multiple instances. As control device is present only from OMAP4
onwards which supports DT only, we use phandles to get the
reference to the control device.
Signed-off-by: Roger Quadros
---
drivers/usb/musb/omap2430.c | 22 ++
Split USB2 PHY and USB3 PHY into separate omap-control-usb
nodes. Get rid of "ti,type" property.
CC: Benoit Cousson
Signed-off-by: Roger Quadros
---
arch/arm/boot/dts/omap5.dtsi | 20
1 files changed, 12 insertions(+), 8 deletions(-)
diff --git a/arch/arm/boot/dts/omap5.
Hi Roger,
On 15/08/2013 15:15, Roger Quadros wrote:
Add support for new device types and in the process rid of "ti,type"
device tree property. The correct type of device will be determined
from the compatible string instead.
Introduce a compatible string for each device type. At the moment
we s
On Thu, 15 Aug 2013, Mark Brown wrote:
> On Wed, Aug 14, 2013 at 03:39:20PM -0400, Alan Stern wrote:
>
> > I don't see the point of all this. Obviously the device can't be used
> > until it physically appears on the bus. What benefit do you get from
> > registering it and making it available to
On Thu, 2013-08-15 at 11:02 +0200, Bjørn Mork wrote:
> Peter Hyman writes:
>
> > On 08/14/2013 01:42 PM, Bjørn Mork wrote:
> > snip...
> >
> >> Great! And if you can snoop on Windows trying to figure out how to
> >> switch the modes, then that would also help. I believe Wireshark with
> >> usbp
On Thu, 2013-08-15 at 03:47 -0500, Peter Hyman wrote:
> On 08/14/2013 06:03 PM, Dan Williams wrote:
> snip...
> > It's almost certainly not the domain of the driver to switch this mode,
> > it's the responsibility of userland. Kernel drivers must only talk to
> > the device, they are not supposed
On 08/15/2013 03:13 PM, Sebastian Andrzej Siewior wrote:
> This relfects the code and dts requires changes due to recent .dts
> binding updates:
> - use mg prefix for the Metor Graphics specific attributes
> - use power in mA not in mA/2 as specifed in the USB2.0 specification
Please ignore this o
Hi,
#1 is redo of the "usb: usb: dsps: update code to reflect recent binding
changes". I forgot to update evm's, beagle bone's and evmsk's .dts file.
Didn't notice it because during testing I forgot to copy the new .dtb
#2 adds a second USB port on beagle bone. It uses both musb instances (s
So I assumed that Beagle bone has only one USB port in host mode because
the micro USB connector had an USB-UART there. I was wrong a little. The
second port runs on host mode, but the micro USB plug is connected to an
internal HUB with two ports: one to the USB-UART and one to musb
instance one.
F
This is what I observe:
On the first connect, the musb starts with DEVCTL.Session set. On
disconnect, musb_core calls try_idle. That functions removes the Session
bit signalizing that the session is over (something that only in OTG is
required). A new device, that is plugged, is no longer recognize
musb_shutdown() removes always USB host and device.
musb_init_controller() adds host and device depending on port_mode. If
port mode is set to HOST then the removal of UDC leads only to:
|(NULL device *): gadget not registered.
and nothing else happens. if port mode is set to DEVICE and we remove
t
This relfects the code and dts requires changes due to recent .dts
binding updates:
- use mg prefix for the Metor Graphics specific attributes
- use power in mA not in mA/2 as specifed in the USB2.0 specification
Signed-off-by: Sebastian Andrzej Siewior
---
arch/arm/boot/dts/am335x-bone.dts |
On 08/15/2013 09:47 AM, Dan Williams wrote:
> On Thu, 2013-08-15 at 11:02 +0200, Bjørn Mork wrote:
>> Peter Hyman writes:
>>
>>> On 08/14/2013 01:42 PM, Bjørn Mork wrote:
>>> snip...
>>>
Great! And if you can snoop on Windows trying to figure out how to
switch the modes, then that would
On Tue, 13 Aug 2013, Daniel Mack wrote:
> > Does this seem reasonable?
>
> I think so, yes. But I'd like to comment on the actual patch, and also
> give it a try first of course. It took me some days to gather my setup
> again, but if you send a revised version, I hope to be able to test it
> in
On Wed, Aug 14, 2013 at 02:32:03PM +0200, Hans de Goede wrote:
> - /* Streams only apply to bulk endpoints. */
> - for (i = 0; i < num_eps; i++)
> + for (i = 0; i < num_eps; i++) {
> + /* Streams only apply to bulk endpoints. */
> if (!usb_endpoint_xfer_bulk(&e
The following changes since commit 5b146f7e016a8727a98b3d48e4f4e128d3624cd5:
Merge 3.11-rc4 into usb-next (2013-08-05 08:36:14 +0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/sarah/xhci.git
tags/for-usb-next-2013-08-15
for you to fetch changes
From: Xenia Ragiadakou
This patch replaces the calls to xhci_info() with calls to
xhci_dbg() and removes the unused xhci_info() definition
from xhci-hcd.
By replacing the xhci_info() with xhci_dbg(), the calls to
dev_info() are replaced with calls to dev_dbg() so that
their output can be dynamic
From: Xenia Ragiadakou
This patch replaces the calls to printk(KERN_DEBUG ...)
with either calls to xhci_dbg() or calls to pr_debug(),
depending on whether the xhci_hcd structure is available
at callsite, so that the correspoding debugging messages
are not enabled by default when CONFIG_DYNAMIC_D
From: Al Cooper
Add Device Tree match table to xhci-plat.c. Add DT bindings document.
Signed-off-by: Al Cooper
Cc: Sergei Shtylyov
Cc: Felipe Balbi
Signed-off-by: Sarah Sharp
---
Documentation/devicetree/bindings/usb/usb-xhci.txt | 14 ++
drivers/usb/host/xhci-plat.c
From: Xenia Ragiadakou
This patch creates a new event class, called xhci_log_event,
and defines the xhci_cmd_completion trace event used for
tracing the commands issued to xHC that generate a completion
event in the event ring.
This info can be used, later, to print, in a human readable
way, the
From: Xenia Ragiadakou
This patch defines a new trace event, which is called xhci_dbg_cancel_urb
and belongs to the event class xhci_log_msg, and adds tracepoints that
trace the debug messages related to the removal of a cancelled URB from
the endpoint's transfer ring.
Signed-off-by: Xenia Ragia
From: Xenia Ragiadakou
The function dma_set_mask() tests internally whether the dma_mask pointer
for the device is initialized and fails if the dma_mask pointer is NULL.
On pci platforms, the device dma_mask pointer is initialized, when pci
devices are enumerated, to point to the pci_dev->dma_mas
From: Xenia Ragiadakou
This patch defines a new trace event, which is called xhci_dbg_quirks
and belongs in the event class xhci_log_msg, and adds tracepoints that
trace the debug messages associated with xHCs' quirks.
Signed-off-by: Xenia Ragiadakou
Signed-off-by: Sarah Sharp
---
drivers/usb
From: Xenia Ragiadakou
This patch declares an event class for trace events that
trace messages with variadic arguments, called xhci_log_msg,
and defines a trace event for tracing the debug messages in
xhci_address_device() function, called xhci_dbg_address.
In order to implement this type of tra
From: Xenia Ragiadakou
This patch defines a new trace event, which is called xhci_dbg_context_change
and belongs in the event class xhci_log_msg, and adds tracepoints for tracing
the debug messages related to context updates performed with Configure Endpoint
and Evaluate Context commands.
Signed
From: Xenia Ragiadakou
This patch defines a new trace event, which is called xhci_dbg_ring_expansion
and belongs to the event class xhci_log_msg, and adds tracepoints that trace
the debug messages associated with the expansion of endpoint ring when there
is not enough space allocated to hold all
From: Xenia Ragiadakou
This patch defines a new trace event, which is called xhci_dbg_reset_ep
and belongs in the event class xhci_log_msg, and adds tracepoints that
trace the debug messages associated with resetting an endpoint after
the reception of a STALL packet.
Signed-off-by: Xenia Ragiada
From: Xenia Ragiadakou
CONFIG_USB_XHCI_HCD_DEBUGGING option is used to enable
verbose debugging output for the xHCI host controller
driver.
In the current version of the xhci-hcd driver, this
option must be turned on, in order for the debugging
log messages to be displayed, and users may need to
From: Xenia Ragiadakou
This patch defines a new trace event, which is called xhci_dbg_init
and belongs to the event class xhci_log_msg, and adds tracepoints that
trace the debug statements in the functions used to start and stop the
xhci-hcd driver.
Also, it removes an unnecessary cast of variab
From: Xenia Ragiadakou
This patch defines a new event class, called xhci_log_ctx,
that records in the ring buffer the context data, the
context type (input or output), the context dma and virtual
addresses, the context endpoint entries, the slot ID and
whether the xHC uses 64 byte context data st
* Roger Quadros | 2013-08-15 16:15:05 [+0300]:
>diff --git a/drivers/usb/phy/phy-omap-control.c
>b/drivers/usb/phy/phy-omap-control.c
>index a4dda8e..3b9ee83 100644
>--- a/drivers/usb/phy/phy-omap-control.c
>+++ b/drivers/usb/phy/phy-omap-control.c
>@@ -197,8 +197,13 @@ static int omap_control_us
* Roger Quadros | 2013-08-15 16:15:10 [+0300]:
>diff --git a/drivers/usb/phy/phy-omap-control.c
>b/drivers/usb/phy/phy-omap-control.c
>index 078c46f..d144c14 100644
>--- a/drivers/usb/phy/phy-omap-control.c
>+++ b/drivers/usb/phy/phy-omap-control.c
>@@ -187,11 +167,19 @@ void omap_control_usb_set
On 08/14/13 23:58, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20130814:
>
on i386 and x86_64:
drivers/usb/phy/phy-am335x-control.c:45:3: error: implicit declaration of
function '__WARN' [-Werror=implicit-function-declaration]
--
~Randy
--
To unsubscribe from this list: send the lin
On Thu, Aug 15, 2013 at 10:42:00AM -0400, Alan Stern wrote:
> On Thu, 15 Aug 2013, Mark Brown wrote:
> So why not bring the device to full power as soon as possible during
> boot, and have it registered on the bus in the usual way? Once that's
> done, the ordinary runtime PM mechanism will allow
Hi,
I was asked by Greg to post this to linux-usb. Please Cc: linux-pci or
linux-acpi
if you think they should take of that.
-
Hi,
I reported in the past all kinds of PCI/ACPI-related issues with this Dell
Vostro 3550 laptop, in respect to USB also problems with XHCI ports fallin
When the HWA encounters a STALL on a control endpoint, it should clear the
RPIPE_STALL feature on the RPIPE before processing the next transfer
request. Otherwise, all transfer requests on that endpoint after the
first STALL will fail because the RPIPE is still in the halted state.
This also
On Thu, 15 Aug 2013, Mark Brown wrote:
> On Thu, Aug 15, 2013 at 10:42:00AM -0400, Alan Stern wrote:
> > On Thu, 15 Aug 2013, Mark Brown wrote:
>
> > So why not bring the device to full power as soon as possible during
> > boot, and have it registered on the bus in the usual way? Once that's
> >
On Tue, Aug 06, 2013 at 02:17:42PM +0300, Jussi Kivilinna wrote:
> Patch fixes i2c-tiny-usb not to use stack as URB transfer_buffer. URB buffers
> need to be DMA-able, which stack is not.
>
> Patch is only compile tested.
>
> Cc: sta...@vger.kernel.org
> Signed-off-by: Jussi Kivilinna
Looks OK
> From: Wang, Yu Y [mailto:yu.y.w...@intel.com]
> Sent: Wednesday, August 14, 2013 8:09 PM
>
> > > From: Felipe Balbi [mailto:ba...@ti.com]
> > > Sent: Tuesday, August 13, 2013 1:30 PM
> > >
> > > On Tue, Aug 13, 2013 at 08:04:26PM +, Paul Zimmerman wrote:
> > > > > From: Felipe Balbi
> > > >
Hi,
On Tue, Aug 06, 2013 at 08:06:14PM +0300, Aaro Koskinen wrote:
> USB subsystem changes broke the USB peripheral/gadget on N800, N810 and
> RX-51/N900 during the merge window. We need to fix this in board files. I
> tested all these with 3.11-rc4 + g_ether + ssh.
Ping?
A.
> Aaro Koskinen (1)
On Thu, Aug 15, 2013 at 01:55:18PM -0400, Alan Stern wrote:
> On Thu, 15 Aug 2013, Mark Brown wrote:
> > On Thu, Aug 15, 2013 at 10:42:00AM -0400, Alan Stern wrote:
> > To be honest I don't see how that helps much if you're going to handle
> > the case where platform data is required to enumerate
Various minor cleanups to resource init and free code including two
actual memory leaks. These should be applied after the WUSB STALL patch
I submitted earlier.
Thomas Pugliese (3):
fix resource cleanup in error path in __wa_xfer_setup_segs
fix leak of urb in wa_xfer_destroy.
Use usb_init
The check to free the URB was the opposite of the correct case. This
patch removes the check altogether since the ptr will be NULL if the URB
was not allocated. Also use usb_free_urb instead of usb_put_urb.
Signed-off-by: Thomas Pugliese
---
drivers/usb/wusbcore/wa-xfer.c |9 -
In wa_seg_init, use usb_init_urb to init the URB object contained in the
transfer segment instead of initializing it manually. Use kmalloc to
allocate the memory for segment instead of kzalloc and then use memset
to set the non-URB portion of the transfer segment struct to 0 since
that was alr
Use usb_free_urb instead of kfree in error path and point to the correct
URB. Also remember to clean up the sg list for the URB if it was allocated.
Signed-off-by: Thomas Pugliese
---
drivers/usb/wusbcore/wa-xfer.c |6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/d
On 15.08.2013 20:55, Wolfram Sang wrote:
> On Tue, Aug 06, 2013 at 02:17:42PM +0300, Jussi Kivilinna wrote:
>> Patch fixes i2c-tiny-usb not to use stack as URB transfer_buffer. URB buffers
>> need to be DMA-able, which stack is not.
>>
>> Patch is only compile tested.
>>
>> Cc: sta...@vger.kernel.o
On Thu, 2013-08-15 at 10:47 -0500, Peter Hyman wrote:
> On 08/15/2013 09:47 AM, Dan Williams wrote:
> > On Thu, 2013-08-15 at 11:02 +0200, Bjørn Mork wrote:
> >> Peter Hyman writes:
> >>
> >>> On 08/14/2013 01:42 PM, Bjørn Mork wrote:
> >>> snip...
> >>>
> Great! And if you can snoop on Wind
Hi,
On 08/15/2013 12:42 PM, Hans de Goede wrote:
What device did you find? I have yet to see a shipping device with
streams...
I don't know about streams, I'm hoping that having a uasp device means it will
also use streams. So far I've been unable to get my hands on anything doing
uasp,
b
On Thu, 15 Aug 2013, Mark Brown wrote:
> On Thu, Aug 15, 2013 at 01:55:18PM -0400, Alan Stern wrote:
> > On Thu, 15 Aug 2013, Mark Brown wrote:
> > > On Thu, Aug 15, 2013 at 10:42:00AM -0400, Alan Stern wrote:
>
> > > To be honest I don't see how that helps much if you're going to handle
> > > th
Add a table explaining the module parameters that g_serial
digests.
Signed-off-by: Matt Porter
---
Documentation/usb/gadget_serial.txt | 13 +
1 file changed, 13 insertions(+)
diff --git a/Documentation/usb/gadget_serial.txt
b/Documentation/usb/gadget_serial.txt
index 61e67f6..d5
On 08/15/2013 03:31 PM, Dan Williams wrote:
snip...
> On Thu, 2013-08-15 at 10:47 -0500, Peter Hyman wrote:
>> snip...
>>
>> Please download AC250U_lsusb_pcap.tar.bz2 from:
>> https://app.box.com/s/6sln7t1na4pz6ij7ggpc
> The modem is speaking Sierra's proprietary CnS protocol. This is a
> propri
On Thu, Aug 15, 2013 at 04:42:01PM -0400, Alan Stern wrote:
> Okay. Here's a restatement of what you wrote above:
> In the case where platform data is required to enumerate the
> device, you need to know about the device prior to enumeration.
> Obviously true.
> You need to g
Good day,
I have a legalised lucrative business of eight million, five hundred thousand
united states dollars we both can execute and benefit from without any
difficulty.
Mr Rolando Biscocho Castillo.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a m
On Thu, Aug 15, 2013 at 05:25:39PM -0700, Greg KH wrote:
> On Thu, Aug 15, 2013 at 02:37:40PM -0500, Thomas Pugliese wrote:
> > Various minor cleanups to resource init and free code including two
> > actual memory leaks. These should be applied after the WUSB STALL patch
> > I submitted earlier.
On Thu, Aug 15, 2013 at 02:37:40PM -0500, Thomas Pugliese wrote:
> Various minor cleanups to resource init and free code including two
> actual memory leaks. These should be applied after the WUSB STALL patch
> I submitted earlier.
I didn't apply that, as Oliver had some objections to it. Care
On Thu, Aug 15, 2013 at 09:12:57AM -0700, Sarah Sharp wrote:
> The following changes since commit 5b146f7e016a8727a98b3d48e4f4e128d3624cd5:
>
> Merge 3.11-rc4 into usb-next (2013-08-05 08:36:14 +0800)
>
> are available in the git repository at:
>
>
> git://git.kernel.org/pub/scm/linux/kerne
Still not working on kernel version 3.11-rc5.
got this in dmesg :
"[ 95.281971] usb 3-4: new high-speed USB device number 2 using ehci-pci
[ 222.285109] cfg80211: Calling CRDA to update world regulatory domain
[ 222.297035] rtl8192cu: Chip version 0x11
[ 222.381548] rtl8192cu: MAC address: 0
On Tue, Aug 13, 2013 at 03:42:11PM -0700, Sarah Sharp wrote:
> On Mon, Aug 12, 2013 at 01:44:16PM -0700, Greg Kroah-Hartman wrote:
> > I tried to "cherry pick" this patch from my usb-next branch to my
> > usb-linus branch, but it fails :(
> >
> > So, could you "port" it, add a cc: stable line, and
From: Lan Tianyu
The pm qos NO_POWER_OFF flag is checked twice during usb device suspend
to see if the usb port power off condition is met. This is redundant and
also will prevent the port from being powered off if the NO_POWER_OFF
flag is changed to 1 from 0 after the device was already suspende
The following changes since commit 224563b6ce034b82f8511969d9496113da34fb2c:
Merge tag 'for-usb-next-2013-08-15' of
git://git.kernel.org/pub/scm/linux/kernel/git/sarah/xhci into usb-next
(2013-08-15 17:33:16 -0700)
are available in the git repository at:
gitol...@ra.kernel.org:/pub/scm/li
The following changes since commit ff8a43c10f1440f07a5faca0c1556921259f7f76:
USB: keyspan: fix null-deref at disconnect and release (2013-08-14 12:49:27
-0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/sarah/xhci.git
tags/for-usb-2013-08-15-step-
The xHCI platform driver calls into usb_add_hcd to register the irq for
its platform device. It does not want the xHCI generic driver to
register an interrupt for it at all. The original code did that by
setting the XHCI_BROKEN_MSI quirk, which tells the xHCI driver to not
enable MSI or MSI-X for
Userspace can tell the kernel to power off any USB port, including ones
that are visible and connectible to users. When an attached USB device
goes into suspend, the port will be powered off if the
pm_qos_no_port_poweroff file for its port is set to 0, the device does
not have remote wakeup enable
From: Alan Stern
The hub driver's usb_port_suspend() routine doesn't handle errors
related to Link Power Management properly. It always returns failure,
it doesn't try to clean up the wakeup setting, (in the case of system
sleep) it doesn't try to go ahead with the port suspend regardless,
and i
On Thu, Aug 15, 2013 at 06:35:49PM -0700, Sarah Sharp wrote:
> On Tue, Aug 13, 2013 at 03:42:11PM -0700, Sarah Sharp wrote:
> > On Mon, Aug 12, 2013 at 01:44:16PM -0700, Greg Kroah-Hartman wrote:
> > > I tried to "cherry pick" this patch from my usb-next branch to my
> > > usb-linus branch, but it
On Thu, Aug 15, 2013 at 06:35:49PM -0700, Sarah Sharp wrote:
> On Tue, Aug 13, 2013 at 03:42:11PM -0700, Sarah Sharp wrote:
> > On Mon, Aug 12, 2013 at 01:44:16PM -0700, Greg Kroah-Hartman wrote:
> > > I tried to "cherry pick" this patch from my usb-next branch to my
> > > usb-linus branch, but it
On Thu, Aug 15, 2013 at 06:44:03PM -0700, Sarah Sharp wrote:
> The following changes since commit 224563b6ce034b82f8511969d9496113da34fb2c:
>
> Merge tag 'for-usb-next-2013-08-15' of
> git://git.kernel.org/pub/scm/linux/kernel/git/sarah/xhci into usb-next
> (2013-08-15 17:33:16 -0700)
>
> are
On Thu, Aug 15, 2013 at 06:43:55PM -0700, Sarah Sharp wrote:
> The following changes since commit ff8a43c10f1440f07a5faca0c1556921259f7f76:
>
> USB: keyspan: fix null-deref at disconnect and release (2013-08-14 12:49:27
> -0700)
>
> are available in the git repository at:
>
> git://git.kern
1 - 100 of 114 matches
Mail list logo
