hello, and thank you Christian for your comment and suggestion.
I will send a new version in the evening: I don't have devices exposing the
same behaviour, so I can't test the code completely.
Still, I will move the check at the suggested point.
But I am worried about interfering with MBIM device
On Saturday, July 08, 2017 01:51:15 PM Peter Chen wrote:
> On Fri, Jul 07, 2017 at 03:03:06PM +0200, Rafael J. Wysocki wrote:
> > On Friday, July 07, 2017 04:01:07 PM Peter Chen wrote:
> > > On Fri, Jul 07, 2017 at 03:13:48AM +0200, Rafael J. Wysocki wrote:
> > > > >
> > > > > - Can I write new co
On Sat, Jul 8, 2017 at 2:04 AM, Alan Stern wrote:
> On Fri, 7 Jul 2017, Alan Robertson wrote:
>
>> Sorry to return to this topic & appreciate it might be either specific
>> to either the Pi or the system(s) I'm connecting it to, but have now
>> had time to try a few more combinations out and would
Some firmwares in Huawei E3372H devices have been observed to switch back
to NTB 32-bit format after altsetting switch.
This patch implements a driver flag to check for the device settings and
set NTB format to 16-bit again if needed.
The flag has been activated for devices controlled by the huawei
On Thu, Jun 22, 2017 at 03:21:31PM +0200, Zoltán Böszörményi wrote:
> In order to make request_*muxed_region() behave more like
> mutex_lock(), a possible failure case needs to be eliminated.
> When drivers do not properly share the same I/O region, e.g.
> one is using request_region() and the othe
On Sat, 8 Jul 2017, Alan Robertson wrote:
> On Sat, Jul 8, 2017 at 2:04 AM, Alan Stern wrote:
> > On Fri, 7 Jul 2017, Alan Robertson wrote:
> >
> >> Sorry to return to this topic & appreciate it might be either specific
> >> to either the Pi or the system(s) I'm connecting it to, but have now
> >
On Sat, Jul 8, 2017 at 4:52 PM, Alan Stern wrote:
> On Sat, 8 Jul 2017, Alan Robertson wrote:
>
>> On Sat, Jul 8, 2017 at 2:04 AM, Alan Stern wrote:
>> > On Fri, 7 Jul 2017, Alan Robertson wrote:
>> >
>> >> Sorry to return to this topic & appreciate it might be either specific
>> >> to either the
Is there anything I can do to debug this issue?
On Thu, Jun 15, 2017 at 1:01 AM, Patrick Chilton wrote:
>> But for the above stuff, note that MBIM modems often (always?) do *not*
>> support DHCP on the net interface. You'll get best results by reading
>> the IP configuration using the MBIM proto
The current code tries to test for bits that are masked out by
usb_endpoint_maxp(). Instead, use the proper accessor to access
the new high bandwidth bits.
Signed-off-by: Benjamin Herrenschmidt
---
drivers/usb/gadget/udc/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/
Some UDC may want to allocate endpoints dynamically, either because
the HW supports an arbitrary large number or because (like the Aspeed
BMC SoCs), the pool of HW endpoints is shared between multiple gadgets.
The allocation side can be done rather easily using the existing
match_ep() UDC hook.
H
The Aspeed BMC SoCs support a "virtual hub" function. It provides some
HW support for a top-level USB2 hub behind which sit 5 gadget "ports".
This driver adds support for the full functionality, emulating the
hub standard requests and exposing 5 UDC gadget drivers corresponding
to the ports.
The
On Sat, 2017-07-08 at 14:38 -0500, Benjamin Herrenschmidt wrote:
> The Aspeed BMC SoCs support a "virtual hub" function. It provides some
> HW support for a top-level USB2 hub behind which sit 5 gadget "ports".
>
> This driver adds support for the full functionality, emulating the
> hub standard r
Alan Robertson wrote:
> On Sat, Jul 8, 2017 at 4:52 PM, Alan Stern wrote:
>> On Sat, 8 Jul 2017, Alan Robertson wrote:
>>
>>> On Sat, Jul 8, 2017 at 2:04 AM, Alan Stern
>>> wrote:
< snip >
>>> > Did you try enabling verbose debugging in g_mass_storage? This
>>> > requires setting CONFIG_USB_
On Fri, Jun 23, 2017 at 10:02 AM, Thang Q. Nguyen wrote:
> XHCI specification 1.1 does not require xHCI-compliant controllers
> to always enable hardware USB2 LPM. However, the current xHCI
> driver always enable it when seeing HLC=1.
> This patch supports an option for users to control disabling
On Sun, Jul 09, 2017 at 12:38:19PM +0700, Thang Q. Nguyen wrote:
> On Fri, Jun 23, 2017 at 10:02 AM, Thang Q. Nguyen wrote:
> > XHCI specification 1.1 does not require xHCI-compliant controllers
> > to always enable hardware USB2 LPM. However, the current xHCI
> > driver always enable it when seei
15 matches
Mail list logo
