[En-Nut-Discussion] Scheduling out of Interrupt sometimes take a timertick NAP
harald.kipp at egnite.de
Mon Mar 9 16:38:38 CET 2015
On 09.03.2015 15:22, Nathan Moore wrote:
> On Mon, Mar 9, 2015 at 8:57 AM, Harald Kipp <harald.kipp at egnite.de> wrote:
>> Btw. in
>> earlier releases this function was named NutEventPostAsync(), which IMHO
>> better reflects its behavior. This function is not limited to interrupt
> As far as I can tell there is still a NutEventPostAsync() which is
> different from NutEventPostFromIrq();
This gives the lie to my explanations. I misconceived the inner working
of NutEventPostFromIrq(). It's not an external function but a macro and
therefore the volatile attribute is required.
Many thanks, Nathan. I vow to have a closer look next time, before
posting false statements.
More information about the En-Nut-Discussion