Hi John,
On 6 January 2017 at 03:08, John Youn wrote:
> On 12/28/2016 5:29 PM, John Youn wrote:
>>
>>
>>> Janusz Dziedzic writes:
>>> On some platfroms(like x86 platform), when one core is running the
>>> USB gadget
>>> irq thread
Hi John,
On 6 January 2017 at 03:08, John Youn wrote:
> On 12/28/2016 5:29 PM, John Youn wrote:
>>
>>
>>> Janusz Dziedzic writes:
>>> On some platfroms(like x86 platform), when one core is running the
>>> USB gadget
>>> irq thread handler by dwc3_thread_interrupt(), meanwhile another
On 12/28/2016 5:29 PM, John Youn wrote:
>
>
>> Janusz Dziedzic writes:
>> 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
On 12/28/2016 5:29 PM, John Youn wrote:
>
>
>> Janusz Dziedzic writes:
>> 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
Hi,
On 5 January 2017 at 19:19, Felipe Balbi wrote:
>
> Hi,
>
> Baolin Wang writes:
>
> [...]
>
> and you have triggered this with mailine? How? We don't write to GEVNT*
> registers from PM code and we only allow runtime_suspend with cable
>
Hi,
On 5 January 2017 at 19:19, Felipe Balbi wrote:
>
> Hi,
>
> Baolin Wang writes:
>
> [...]
>
> and you have triggered this with mailine? How? We don't write to GEVNT*
> registers from PM code and we only allow runtime_suspend with cable
> dettached.
Sorry for late reply
Hi,
Baolin Wang writes:
[...]
and you have triggered this with mailine? How? We don't write to GEVNT*
registers from PM code and we only allow runtime_suspend with cable
dettached.
>>>
>>> Sorry for late reply since I am busy on other things. I just
Hi,
Baolin Wang writes:
[...]
and you have triggered this with mailine? How? We don't write to GEVNT*
registers from PM code and we only allow runtime_suspend with cable
dettached.
>>>
>>> Sorry for late reply since I am busy on other things. I just agreed
>>> with the possible
Hi,
On 5 January 2017 at 17:26, Felipe Balbi wrote:
>
> Hi,
>
> Baolin Wang writes:
On 27 December 2016 at 18:52, Janusz Dziedzic
wrote:
> 2016-12-26 9:01 GMT+01:00 Baolin Wang
Hi,
On 5 January 2017 at 17:26, Felipe Balbi wrote:
>
> Hi,
>
> Baolin Wang writes:
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
Hi,
Baolin Wang writes:
>>> 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
Hi,
Baolin Wang writes:
>>> 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
On 3 January 2017 at 20:33, Felipe Balbi wrote:
>
> Hi,
>
> Baolin Wang writes:
>> On 28 December 2016 at 20:30, Janusz Dziedzic
>> wrote:
>>> 2016-12-27 13:16 GMT+01:00 Baolin Wang :
Hi,
On 3 January 2017 at 20:33, Felipe Balbi wrote:
>
> Hi,
>
> Baolin Wang writes:
>> On 28 December 2016 at 20:30, Janusz Dziedzic
>> wrote:
>>> 2016-12-27 13:16 GMT+01:00 Baolin Wang :
Hi,
On 27 December 2016 at 19:11, Felipe Balbi wrote:
>
> Hi,
>
> Baolin Wang
Hi,
Baolin Wang writes:
> On 28 December 2016 at 20:30, Janusz Dziedzic
> wrote:
>> 2016-12-27 13:16 GMT+01:00 Baolin Wang :
>>> Hi,
>>>
>>> On 27 December 2016 at 19:11, Felipe Balbi wrote:
Hi,
Baolin Wang writes:
> On 28 December 2016 at 20:30, Janusz Dziedzic
> wrote:
>> 2016-12-27 13:16 GMT+01:00 Baolin Wang :
>>> Hi,
>>>
>>> On 27 December 2016 at 19:11, Felipe Balbi wrote:
Hi,
Baolin Wang writes:
> Hi,
>
> On 27 December 2016 at 18:52,
On 28 December 2016 at 20:30, Janusz Dziedzic wrote:
> 2016-12-27 13:16 GMT+01:00 Baolin Wang :
>> Hi,
>>
>> On 27 December 2016 at 19:11, Felipe Balbi wrote:
>>>
>>> Hi,
>>>
>>> Baolin Wang writes:
On 28 December 2016 at 20:30, Janusz Dziedzic wrote:
> 2016-12-27 13:16 GMT+01:00 Baolin Wang :
>> 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
nux.intel.com>; Baolin Wang
> <baolin.w...@linaro.org>; Greg KH <gre...@linuxfoundation.org>; USB
> <linux-...@vger.kernel.org>; LKML <linux-kernel@vger.kernel.org>; Linaro
> Kernel Mailman List <linaro-ker...@lists.linaro.org>; Mark Brown
> <broo...@ke
ro
> Kernel Mailman List ; Mark Brown
>
> Subject: Re: [PATCH] usb: dwc3: gadget: Avoid race between dwc3 interrupt
> handler and irq thread handler
>
>
> Hi,
>
> Janusz Dziedzic writes:
> >>>> On some platfroms(like x86 platform), w
Hi,
Janusz Dziedzic writes:
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,
Janusz Dziedzic writes:
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
2016-12-27 12:05 GMT+01:00 Felipe Balbi :
> 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(),
2016-12-27 12:05 GMT+01:00 Felipe Balbi :
> 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
>>>
2016-12-27 13:16 GMT+01:00 Baolin Wang :
> 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
2016-12-27 13:16 GMT+01:00 Baolin Wang :
> 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
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 :
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
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
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
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
>>
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
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
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,
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
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
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
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 12/27/2016 10:58 AM, Baolin Wang wrote:
> Hi,
>
> On 27 December 2016 at 10:39, Lu Baolu wrote:
>> Hi,
>>
>> 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
Hi,
On 12/27/2016 10:58 AM, Baolin Wang wrote:
> Hi,
>
> On 27 December 2016 at 10:39, Lu Baolu wrote:
>> Hi,
>>
>> 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(),
Hi,
On 27 December 2016 at 10:39, Lu Baolu wrote:
> Hi,
>
> 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
Hi,
On 27 December 2016 at 10:39, Lu Baolu wrote:
> Hi,
>
> 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
Hi,
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 event buffer by
>
Hi,
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 event buffer by
>
44 matches
Mail list logo