Oliver Neukum writes:
> On Tue, 2013-08-20 at 12:35 +0200, Bjørn Mork wrote:
>
>> bjorn@nemi:~$ mbimcli -d /dev/cdc-wdm0 --query-packet-service-state
>
> How does that work internally?
The userspace application/library creates a MBIM message and sends it to
the firmware by writing the complete p
The following patch is required to resolve remote wake issues with
certain devices.
Issue description:
If the remote wake is issued from the device in a specific timing
condition while the system is entering sleep state then it may cause
system to auto wake on subsequent sleep cycle.
Root cause:
It add a remote wakeup pci quirk for some special AMD platforms. This
quirk filters southbridge revision which is 0x39 or 0x3a.
Signed-off-by: Huang Rui
---
drivers/usb/host/pci-quirks.c | 14 +-
drivers/usb/host/pci-quirks.h | 1 +
2 files changed, 14 insertions(+), 1 deletion(-)
The following patch is required to resolve remote wake issues with
certain devices.
Issue description:
If the remote wake is issued from the device in a specific timing
condition while the system is entering sleep state then it may cause
system to auto wake on subsequent sleep cycle.
Root cause:
It adds all issue mice on AMD special platforms for remote wakeup quirk.
Some mice with on Pixart controller would trigger remote wakeup quirk on
some AMD special platforms, this patch added all issue mice which tested.
But some manufactures might overwrite vendor id and product id in the
firmwar
Hi Greg, Sarah, Alan,
The following patches are required to resolve remote wake issues with
certain devices.
Issue description:
If the remote wake is issued from the device in a specific timing
condition while the system is entering sleep state then it may cause
system to auto wake on subsequent
Hi All,
I'm very happy to announce libusbx-1.0.17.
2013-09-06: v1.0.17
* Hotplug callbacks now always get passed a libusb_context, even if it is
the default context. Previously NULL would be passed for the default context,
but since the first context created is the default context, and most
On Fri, 2013-09-06 at 12:19 +0200, Bjørn Mork wrote:
> I assume this separate channel for device management was added to MBIM
> because it wouldn't scale to keep adding new CDC notifications and
> requests. The MBIM management protocol is easily extended by adding
> new
> commands and services, inc
On Fri, 6 Sep 2013, Victor Leschuk wrote:
> Hello, thanks for the answer. Maybe I sound stupid but how can I tell
> g_mass_storage which controller to use? If I unload dummy_hcd and then
> try to modprobe g_mass_storage I get an error "no such device".
There is no way to tell g_mass_storage which
On Tue, Aug 20, 2013 at 05:35:46PM +0100, Sebastian Andrzej Siewior wrote:
> The support for both am335x-USB instances required changes to the device
> tree bindings. This patch reflects these changes in the bindings
> document.
>
> v3…v4:
> - remove the child node for USB. This is driver specific
On Fri, Sep 06, 2013 at 06:24:41PM +0800, Huang Rui wrote:
> It adds all issue mice on AMD special platforms for remote wakeup quirk.
>
> Some mice with on Pixart controller would trigger remote wakeup quirk on
> some AMD special platforms, this patch added all issue mice which tested.
>
> But so
On Fri, Sep 06, 2013 at 06:24:42PM +0800, Huang Rui wrote:
> It add a remote wakeup pci quirk for some special AMD platforms. This
> quirk filters southbridge revision which is 0x39 or 0x3a.
>
> Signed-off-by: Huang Rui
> ---
> drivers/usb/host/pci-quirks.c | 14 +-
> drivers/usb/hos
On Tue, Aug 20, 2013 at 05:35:47PM +0100, 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
> -
On Fri, Sep 06, 2013 at 06:24:44PM +0800, Huang Rui wrote:
> static void dl_done_list (struct ohci_hcd *);
> static void finish_unlinks (struct ohci_hcd *, u16);
> +static inline int root_port_reset (struct ohci_hcd *, unsigned);
How can a definition of a function be inline? :)
Can't you just
The Kconfig help text is talking about the U5500 which is no
longer supported by the kernel. Name the help text after the
config symbol which is more correct.
Signed-off-by: Linus Walleij
---
drivers/usb/musb/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers
On Fri, 6 Sep 2013, Huang Rui wrote:
> The following patch is required to resolve remote wake issues with
> certain devices.
>
> Issue description:
> If the remote wake is issued from the device in a specific timing
> condition while the system is entering sleep state then it may cause
> system t
Hi Alexander,
I've been noticing that you haven't been keeping up with the chipidea
patches being posted. Is there anything I can do here to help out with
that?
There seems to be lots of development activity in this area, and I don't
want to see things slow down for different developers if there
On Fri, 6 Sep 2013, Oleksij Rempel wrote:
> Hi Alan,
>
> i need more help.
>
> We have more test results now. Initial patch was probably fixing
> fallowing issue - bad performance on EP4/EP3 if Intr transfer is used.
> It is reproducible only on EHCI, but not reproducible on xHCI controller.
I
On Fri, Sep 06, 2013 at 02:02:04PM -0700, Sarah Sharp wrote:
> On Fri, Sep 06, 2013 at 06:24:43PM +0800, Huang Rui wrote:
> > The following patch is required to resolve remote wake issues with
> > certain devices.
> >
> > Issue description:
> > If the remote wake is issued from the device in a spe
On 09/04/2013 09:25 PM, Martin MOKREJŠ wrote:
Hi Xenia,
thank you. I tested this patch on 3.11 kernel and the messages don't appear
anymore
upon LPM-capable device disconnect (tested with ASMedia AS2105 devices).
Not much to show here, there is just no error/warning related to LPM
while handl
On Fri, Sep 06, 2013 at 06:24:43PM +0800, Huang Rui wrote:
> The following patch is required to resolve remote wake issues with
> certain devices.
>
> Issue description:
> If the remote wake is issued from the device in a specific timing
> condition while the system is entering sleep state then it
Am 06.09.2013 23:09, schrieb Alan Stern:
On Fri, 6 Sep 2013, Oleksij Rempel wrote:
Hi Alan,
i need more help.
We have more test results now. Initial patch was probably fixing
fallowing issue - bad performance on EP4/EP3 if Intr transfer is used.
It is reproducible only on EHCI, but not reprod
On Fri, 6 Sep 2013, Oleksij Rempel wrote:
> Am 06.09.2013 23:09, schrieb Alan Stern:
> > On Fri, 6 Sep 2013, Oleksij Rempel wrote:
> >
> >> Hi Alan,
> >>
> >> i need more help.
> >>
> >> We have more test results now. Initial patch was probably fixing
> >> fallowing issue - bad performance on EP4/
23 matches
Mail list logo
