2016-12-26 9:01 GMT+01:00 Baolin Wang :
> On some platfroms(like x86 platform), when one core is running the USB gadget
> irq thread handler by dwc3_thread_interrupt(), meanwhile another core also can
> respond other interrupts from dwc3 controller and modify the event buffer by
> dwc3_interrupt()
Hi,
On 27 December 2016 at 18:52, Janusz Dziedzic wrote:
> 2016-12-26 9:01 GMT+01:00 Baolin Wang :
>> On some platfroms(like x86 platform), when one core is running the USB gadget
>> irq thread handler by dwc3_thread_interrupt(), meanwhile another core also
>> can
>> respond other interrupts fro
Hi,
Lu Baolu writes:
> On 12/26/2016 04:01 PM, Baolin Wang wrote:
>> On some platfroms(like x86 platform), when one core is running the USB gadget
>> irq thread handler by dwc3_thread_interrupt(), meanwhile another core also
>> can
>> respond other interrupts from dwc3 controller and modify the
Hi,
Janusz Dziedzic writes:
> 2016-12-26 9:01 GMT+01:00 Baolin Wang :
>> On some platfroms(like x86 platform), when one core is running the USB gadget
>> irq thread handler by dwc3_thread_interrupt(), meanwhile another core also
>> can
>> respond other interrupts from dwc3 controller and modify
Hi,
Baolin Wang writes:
> Hi,
>
> On 27 December 2016 at 18:52, Janusz Dziedzic
> wrote:
>> 2016-12-26 9:01 GMT+01:00 Baolin Wang :
>>> On some platfroms(like x86 platform), when one core is running the USB
>>> gadget
>>> irq thread handler by dwc3_thread_interrupt(), meanwhile another core a
Hi,
Hans de Goede writes:
> usb_get_dr_mode() expects the device-property to be spelled
> "dr_mode" not "dr-mode".
>
> Spelling it properly fixes the following warning showing up in dmesg:
> [ 8704.500545] dwc3 dwc3.2.auto: Configuration mismatch. dr_mode forced to
> gadget
>
> Signed-off-by: H
Hi,
Krzysztof Opasiak writes:
> Since:
>
> commit 855ed04a3758 ("usb: gadget: udc-core: independent registration
> of gadgets and gadget drivers")
>
> if we load gadget module but there is no free udc available
> then it will be stored on a pending gadgets list.
>
> $ modprobe g_zero.ko
> $ modp
Hi,
Alan Stern writes:
> On Tue, 6 Dec 2016, Andrey Konovalov wrote:
>
>> Hi!
>>
>> I've got the following error report while running the syzkaller fuzzer.
>>
>> ep0_write() doesn't check the length, so a user can cause an
>> out-of-bounds with both size and data controlled.
>> There's a comme
Hi,
Chunfeng Yun writes:
> the issue is introduced when @is_u3_ip is used in mtu3_device_enabe()
> before initialized in mtu3_mem_alloc(), so get global IP information
> at first before used by following functins.
>
> Signed-off-by: Chunfeng Yun
patch doesn't apply to my testing/fixes. Please
Hi,
John Youn writes:
> Calling platform_device_add_properties() replaces existing properties so
> the "linux,sysdev_is_parent" property doesn't get set. Add this property
> to each platform.
>
> Fixes: d64ff406e51e ("usb: dwc3: use bus->sysdev for DMA configuration")
> Signed-off-by: John Youn
Hi John,
John Youn writes:
> The dwc2 driver triggers several hundred checkpatch warnings and
> checks. None of them are actual problems but this is still very noisy.
> This series fixes most of those issues.
>
> The first patch in the series is the result of running checkpatch with
> '--fix'. A
Hi,
Andrey Konovalov writes:
> Hi!
>
> I've got the following error report while running the syzkaller fuzzer.
>
> On commit 3c49de52d5647cda8b42c4255cf8a29d1e22eff5 (Dec 2).
>
> WARNING: CPU: 0 PID: 5257 at drivers/usb/gadget/udc/dummy_hcd.c:672
> dummy_free_request+0x153/0x170
> Kernel panic -
Now that we're handling so many transfers at a time
and for some dwc3 revisions LPM events *must* be
enabled, we can fall into a situation where too many
events fire and we start receiving Overflow events.
Let's do what XHCI does and allocate a full page for
the Event Ring, this will avoid any fut
commit 8897a761c371ceefda98570953185daa3c059ad1 upstream
No Response Update Transfer is a special type of
Update Transfer command which can be used whenever
we're not relying on XferNotReady to prepare
transfers. With this, we don't need to wait for
CMDACT to be cleared and issue further commands
commit 514f227b20addf01297b3df24be6b4161f69 upstream.
The cmd argument we pass to
dwc3_send_gadget_ep_cmd() could contain extra
arguments embedded. When checking for StartTransfer
command, we need to make sure to match only lower 4
bits which contain the actual command and ignore the
rest.
Cc
commit 0416e494ce7d ("usb: dwc3: ep0: correct cache
sync issue in case of ep0_bounced") introduced a bug
where we would leak DMA resources which would cause
us to starve the system of them resulting in failing
DMA transfers.
Fix the bug by making sure that we always unmap EP0
requests since those
For now this is just a cleanup patch, no functional
changes. We will be using the new function to fix a
bug introduced long ago by commit 0416e494ce7d
("usb: dwc3: ep0: correct cache sync issue in case
of ep0_bounced") and further worsened by commit
c0bd5456a470 ("usb: dwc3: ep0: handle non maxpack
Let's call dwc3_ep0_prepare_one_trb() explicitly
because there are occasions where we will need more
than one TRB to handle an EP0 transfer.
A follow-up patch will fix one bug related to
multiple-TRB Data Phases when it comes to
mapping/unmapping requests for DMA.
Cc:
Reported-by: Janusz Dziedzi
Hi,
On 27 December 2016 at 19:11, Felipe Balbi wrote:
>
> Hi,
>
> Baolin Wang writes:
>> Hi,
>>
>> On 27 December 2016 at 18:52, Janusz Dziedzic
>> wrote:
>>> 2016-12-26 9:01 GMT+01:00 Baolin Wang :
On some platfroms(like x86 platform), when one core is running the USB
gadget
i
From: Heikki Krogerus
Intel Gemini Lake SoC has the same DWC3 than Broxton. Add
the new ID to the supported Devices.
Signed-off-by: Heikki Krogerus
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/dwc3-pci.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/usb/dwc3/dwc3-pci.c b/d
On Thu, 2016-12-22 at 17:44 -0500, Alan Stern wrote:
> I don't see how this patch fixes anything. Unless I'm mistaken, it
> just avoids the problem by preventing the system from issuing the
> command that provokes the error, rather than really fixing the
> underlying error.
Please clarify. If a r
On Thu, Dec 22, 2016 at 05:11:20PM +0100, Jérémy Lefaure wrote:
> From: Jérémy Lefaure
>
> The function bfin_fifo_offset is defined but not used:
>
> drivers/usb/musb/blackfin.c:36:12: warning: ‘bfin_fifo_offset’ defined
> but not used [-Wunused-function]
> static u32 bfin_fifo_offset(u8 epnum)
On Mon, 26 Dec 2016, Linus Torvalds wrote:
> On Dec 26, 2016 4:04 PM, "Alan Stern" wrote:
>
>
> Note that the usage of tmp in the "if (unlikely(req->td->dmadesc == 0)) {"
> branch really is not conflicting, because that branch breaks out of the
> enclosing "while" loop.
>
>
> No.
>
> Look clo
On Tue, 27 Dec 2016, Felipe Balbi wrote:
>
> Hi,
>
> Alan Stern writes:
> > On Tue, 6 Dec 2016, Andrey Konovalov wrote:
> >
> >> Hi!
> >>
> >> I've got the following error report while running the syzkaller fuzzer.
> >>
> >> ep0_write() doesn't check the length, so a user can cause an
> >> ou
On Tue, 27 Dec 2016, Oliver Neukum wrote:
> On Thu, 2016-12-22 at 17:44 -0500, Alan Stern wrote:
> > I don't see how this patch fixes anything. Unless I'm mistaken, it
> > just avoids the problem by preventing the system from issuing the
> > command that provokes the error, rather than really fix
On Tue, 2016-12-27 at 10:20 -0500, Alan Stern wrote:
> On Tue, 27 Dec 2016, Oliver Neukum wrote:
>
> > On Thu, 2016-12-22 at 17:44 -0500, Alan Stern wrote:
> > > I don't see how this patch fixes anything. Unless I'm mistaken, it
> > > just avoids the problem by preventing the system from issuing
Hi Alan,
On Tuesday 27 December 2016 08:50 PM, Alan Stern wrote:
On Tue, 27 Dec 2016, Oliver Neukum wrote:
On Thu, 2016-12-22 at 17:44 -0500, Alan Stern wrote:
I don't see how this patch fixes anything. Unless I'm mistaken, it
just avoids the problem by preventing the system from issuing th
Sorry, first time patcher here, and forgot to include the list when I
sent this patch to Jiri and Benjamin last week.
The Futaba TOSD-5711BB VFD crashes when the initial HID report is requested,
register the display in hid-ids and tell hid-quirks to not do the init.
Signed-off-by: Alex Wood
Hi,
On Tue, 2016-12-27 at 13:22 +0200, Felipe Balbi wrote:
> Hi,
>
> Chunfeng Yun writes:
> > the issue is introduced when @is_u3_ip is used in mtu3_device_enabe()
> > before initialized in mtu3_mem_alloc(), so get global IP information
> > at first before used by following functins.
> >
> > Sig
I'm not entirely sure either, that is why I wanted the specs.
Alan sent me the PLX NET2280 specs, but I'm using the USB3380/USB3381 - the
USB3 version of the device.
As it seems from the code, the HW interface is mostly the same, with some minor
changes, so it is the same driver (net2280.c) but w
On Tue, 27 Dec 2016, George Cherian wrote:
> Hi Alan,
>
>
> On Tuesday 27 December 2016 08:50 PM, Alan Stern wrote:
> > On Tue, 27 Dec 2016, Oliver Neukum wrote:
> >
> >> On Thu, 2016-12-22 at 17:44 -0500, Alan Stern wrote:
> >>> I don't see how this patch fixes anything. Unless I'm mistaken, i
Hi!
Any idea how find root of problem?
Thanks.
--
Best Regards,
Mike Gavrilov.
system.log.bz2
Description: BZip2 compressed data
32 matches
Mail list logo
