Hi,
Rob Weber writes:
> On Tue, Mar 26, 2019 at 11:14:47AM +0200, Felipe Balbi wrote:
>> >> > dmesg output is short (4 lines) and is probably helpful to find the
>> >> > meaningful timestamps of the dwc3 traces. The sequence of events on the
>> >> > device seems to start around 1346 seconds and
dwc3_gadget_suspend() is called under dwc->lock spinlock. In such context
calling synchronize_irq() is not allowed. Move the problematic call out
of the protected block to fix the following kernel BUG during system
suspend:
BUG: sleeping function called from invalid context at kernel/irq/manage.c:
(fixing linux-usb email)
Felipe Balbi writes:
> Hi Greg,
>
> here's the first pull request for current -rc cycle. There really isn't
> much here yet, only some minor fixes and a new pci id.
>
> __
> < Not much >
> --
> \ ^__^
> \ (oo)\___
>
This is a Qualcomm based device with a QMI function on interface 4.
It is mode switched from 2020:2030 using a standard eject message.
T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 6 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=2020 ProdID=2031 Rev= 2.
When we read an array of integers from device properties,
the temporary buffer is allocated.
However, in case of dwc3_set_incr_burst_type() it's not freed.
Free allocated buffer immediately after use.
Signed-off-by: Andy Shevchenko
---
drivers/usb/dwc3/core.c | 3 +++
1 file changed, 3 insertio
On Tue, Mar 26, 2019 at 09:10:15AM +0100, Tassilo Horn wrote:
> Hi all,
>
> I've submitted this already at
> https://bugzilla.kernel.org/show_bug.cgi?id=203049 but Greg
> Kroah-Hartman told me that this is the right place.
>
> I've got this touchpad:
>
> https://www.amazon.com/Wireless-VOGEK-Rec
On Tue, Mar 26, 2019 at 09:15:57PM +0100, Mathieu Malaterre wrote:
> The returned value in status has never been used since
> commit 4296c70a5ec3 ("USB/xHCI: Enable USB 3.0 hub remote wakeup.")
> So remove 'status' completely.
>
> Remove warning (W=1):
>
> drivers/usb/core/hub.c:3671:8: warning
On 3/22/19 2:10 PM, Bin Liu wrote:
>
> Please explain the issue in details here, we will try to solve it.
I did some more troubleshooting, contrary to what I stated initially the
kernel version does not matter.
What changed the behaviour is that I was loading g_mass_storage on the
system working
Hello,
On Wed, Mar 27, 2019 at 11:02:28AM +0200, Felipe Balbi wrote:
> >> >> > dmesg output is short (4 lines) and is probably helpful to find the
> >> >> > meaningful timestamps of the dwc3 traces. The sequence of events on
> >> >> > the
> >> >> > device seems to start around 1346 seconds and en
Hello this is Mr Wong again from hongkong,Can we send the Swift as discuss best
regards.
Mr Wong Cheng
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
Hi Rob,
Rob Weber writes:
>> >> Felipe Balbi writes:
>> >> >>> Sure, that would be great. How can I download it? Any link which I can
>> >> >>> curl? You can send it to me only, if you want; no problem.
>> >> >>
>> >> >> You (and anyone reading) can download it here:
>> >> >> https://drive.goog
Greg KH writes:
Hi Greg,
>> I've submitted this already at
>> https://bugzilla.kernel.org/show_bug.cgi?id=203049 but Greg
>> Kroah-Hartman told me that this is the right place.
>>
>> I've got this touchpad:
>>
>> https://www.amazon.com/Wireless-VOGEK-Rechargeable-Multi-Touch-Navigation/dp/B07N
12 matches
Mail list logo
