[Bug 1001456] HAL misses Interrupt Clear-Pending Registers handling:wasted processing power

[bugzilla-daemon at bugs dot ecos dot sourceware dot org]

Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001456

--- Comment #27 from Ilija Kocho <ilijak@siva.com.mk> 2012-09-27 12:05:14 BST ---
(In reply to comment #25)
> I still think this needs to be commented on by Nick as it involves a
> significant change to the HAL definition, and he's both the HAL in general and
> specifically Cortex-M HAL architect. So I'm assigning this to him and see if he
> grumbles :-). He can always assign it away if he's not interested in commenting
> on the API change.
> 
> But I wouldn't overstate the problem, as far I can tell this will only happen
> with certain designs of devices, and only then if certain situations combine,
> which therefore makes it uncommon. That's not to say it's irrelevant, but it's
> not like it happens every interrupt or anything like that.

Jifl, I think that we ought to resolve this issue.

In order to avoid API extension I proposed usage of
cyg_drv_interrupt_acknowledge() (effectively unused by Cortex-M) for which
Bernard has arguments that I respect (our discussion in comment #13 till
comment #20).

On the other hand the addition proposed by Bernard does not affect other
architectures because for them it compiles to empty statement so it could be
considered safe. The questions (for me) are:
    - Is there other alternative way to fix this issue?
    - If we add Bernard's function and associated macro do we bloat our API or
not?

Ilija

-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.