public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: ecos-bugs@ecos.sourceware.org Subject: [Bug 1001456] HAL misses Interrupt Clear-Pending Registers handling: wasted processing power Date: Thu, 27 Sep 2012 12:39:00 -0000 [thread overview] Message-ID: <20120927123852.8B4422F7800C@mail.ecoscentric.com> (raw) In-Reply-To: <bug-1001456-13@http.bugs.ecos.sourceware.org/> Please do not reply to this email. Use the web interface provided at: http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001456 Bernd Edlinger <bernd.edlinger@hotmail.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bernd.edlinger@hotmail.de --- Comment #28 from Bernd Edlinger <bernd.edlinger@hotmail.de> 2012-09-27 13:38:45 BST --- Hi Bernard, just one thing... personally I would not like to add more Kernel APIs unless it is absolutely necessary. In the hal/arm subtree when there is an interrupt, the function hal_IRQ_handler() gets called first. This function determines the highest priority irq, and updates the ISR (in service register), this would be a place to clear the interrupt pending bit for your architecture. Suppose the clear pending is done automatically in hal_IRQ_handler() and hal_interrupt_acknowledge is empty, then this would be a safe way to write the isr/dsr in the driver: isr() { HAL_INTERRUPT_MASK(vector); HAL_INTERRUPT_ACKNOWLEGE(); return CALL_DSR; } dsr() { now handle interrupt... HAL_INTERRUPT_UNMASK(vector); } this is in fact how most drivers are already written today. would'nt that be OK for you too? Regards, Bernd Edlinger -- 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.
next prev parent reply other threads:[~2012-09-27 12:39 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-16 14:26 [Bug 1001456] New: " bugzilla-daemon 2012-01-16 16:29 ` [Bug 1001456] " bugzilla-daemon 2012-02-09 14:23 ` bugzilla-daemon 2012-02-15 10:10 ` bugzilla-daemon 2012-02-15 10:48 ` bugzilla-daemon 2012-02-15 11:29 ` bugzilla-daemon 2012-02-16 15:30 ` bugzilla-daemon 2012-02-16 16:46 ` bugzilla-daemon 2012-02-23 9:05 ` bugzilla-daemon 2012-02-23 10:29 ` bugzilla-daemon 2012-04-02 8:10 ` bugzilla-daemon 2012-04-02 17:48 ` bugzilla-daemon 2012-04-02 21:22 ` bugzilla-daemon 2012-09-27 8:52 ` bugzilla-daemon 2012-09-27 12:39 ` bugzilla-daemon [this message] 2012-09-27 13:36 ` bugzilla-daemon 2012-09-27 18:09 ` bugzilla-daemon 2012-01-16 14:26 [Bug 1001456] New: " bugzilla-daemon 2012-01-24 16:11 ` [Bug 1001456] " bugzilla-daemon 2012-02-09 9:40 ` bugzilla-daemon 2012-02-09 11:30 ` bugzilla-daemon 2012-02-16 15:30 ` bugzilla-daemon 2012-02-23 9:58 ` bugzilla-daemon 2012-04-02 21:22 ` bugzilla-daemon 2012-09-26 16:15 ` bugzilla-daemon 2012-09-26 21:44 ` bugzilla-daemon
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20120927123852.8B4422F7800C@mail.ecoscentric.com \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=ecos-bugs@ecos.sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).