On 2017-01-18 13:46, Mark Brown wrote:
> On Wed, Jan 18, 2017 at 10:33:07AM +0100, Jan Kiszka wrote:
>> On 2017-01-18 09:21, Robert Jarzmik wrote:
>
>> +while (1) {
>
> This bit worries me a bit, as this can be either :
> - hogging the SoC's CPU, endlessly running
> - or
On Wed, Jan 18, 2017 at 10:33:07AM +0100, Jan Kiszka wrote:
> On 2017-01-18 09:21, Robert Jarzmik wrote:
> +while (1) {
> >>> This bit worries me a bit, as this can be either :
> >>> - hogging the SoC's CPU, endlessly running
> >>> - or even worse, blocking the CPU for ever
> >>>
On 2017-01-18 09:21, Robert Jarzmik wrote:
> Jan Kiszka writes:
>
>> On 2017-01-17 08:54, Robert Jarzmik wrote:
>>> Jan Kiszka writes:
>>>
When using the a device with edge-triggered interrupts, such as MSIs,
the interrupt handler has to ensure that there is a point in time during
Jan Kiszka writes:
> On 2017-01-17 08:54, Robert Jarzmik wrote:
>> Jan Kiszka writes:
>>
>>> When using the a device with edge-triggered interrupts, such as MSIs,
>>> the interrupt handler has to ensure that there is a point in time during
>>> its execution where all interrupts sources are sile
On 2017-01-16 20:46, Jan Kiszka wrote:
> On 2017-01-16 20:07, Andy Shevchenko wrote:
>> On Mon, 2017-01-16 at 19:44 +0100, Jan Kiszka wrote:
>>> When using the a device with edge-triggered interrupts, such as MSIs,
>>> the interrupt handler has to ensure that there is a point in time
>>> during
>>>
On 2017-01-17 14:11, Jarkko Nikula wrote:
> On 01/17/2017 10:10 AM, Jan Kiszka wrote:
>> On 2017-01-17 08:58, Robert Jarzmik wrote:
>>> Jan Kiszka writes:
>>>
When using the a device with edge-triggered interrupts, such as MSIs,
the interrupt handler has to ensure that there is a point i
On 01/17/2017 10:10 AM, Jan Kiszka wrote:
On 2017-01-17 08:58, Robert Jarzmik wrote:
Jan Kiszka writes:
When using the a device with edge-triggered interrupts, such as MSIs,
the interrupt handler has to ensure that there is a point in time during
its execution where all interrupts sources are
On 2017-01-17 08:58, Robert Jarzmik wrote:
> Jan Kiszka writes:
>
>> When using the a device with edge-triggered interrupts, such as MSIs,
>> the interrupt handler has to ensure that there is a point in time during
>> its execution where all interrupts sources are silent so that a new
>> event ca
On 2017-01-17 08:54, Robert Jarzmik wrote:
> Jan Kiszka writes:
>
>> When using the a device with edge-triggered interrupts, such as MSIs,
>> the interrupt handler has to ensure that there is a point in time during
>> its execution where all interrupts sources are silent so that a new
>> event ca
Jan Kiszka writes:
> When using the a device with edge-triggered interrupts, such as MSIs,
> the interrupt handler has to ensure that there is a point in time during
> its execution where all interrupts sources are silent so that a new
> event can trigger a new interrupt again.
>
> This is achiev
Jan Kiszka writes:
> When using the a device with edge-triggered interrupts, such as MSIs,
> the interrupt handler has to ensure that there is a point in time during
> its execution where all interrupts sources are silent so that a new
> event can trigger a new interrupt again.
>
> This is achiev
On 2017-01-16 20:07, Andy Shevchenko wrote:
> On Mon, 2017-01-16 at 19:44 +0100, Jan Kiszka wrote:
>> When using the a device with edge-triggered interrupts, such as MSIs,
>> the interrupt handler has to ensure that there is a point in time
>> during
>> its execution where all interrupts sources ar
On Mon, 2017-01-16 at 19:44 +0100, Jan Kiszka wrote:
> When using the a device with edge-triggered interrupts, such as MSIs,
> the interrupt handler has to ensure that there is a point in time
> during
> its execution where all interrupts sources are silent so that a new
> event can trigger a new i
13 matches
Mail list logo
