From: Yoshihiro Shimoda <shimoda.yoshihiro@renesas.com>
To: linux-sh@vger.kernel.org
Subject: INTC issue
Date: Thu, 05 Feb 2009 12:04:52 +0000 [thread overview]
Message-ID: <498AD5E4.8050809@renesas.com> (raw)
Hi,
I found INTC issue. For example, an interrupt is prohibited when I handle it as follows.
1) Driver A call request_irq of DMAC ch0
2) Driver B call request_irq of DMAC ch1.
3) Driver A call free_irq of DMAC ch0.
4) Driver B use DMAC ch1, but DMAC ch1 interrupt disabled.
The interrupt mask register of SH7785 is INT2MSKR.
The bit 11 of INT2MSKR is DMAC channels 0 to 5 interrupts mask bit.
I think that it is necessary to count the number of times admitted
an interrupt to solve this problem. I think that intc have a counter
every interrupt bit for a simple implementation method, but there
is much waste.
Any ideas?
Thanks,
Yoshihiro Shimoda
next reply other threads:[~2009-02-05 12:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 12:04 Yoshihiro Shimoda [this message]
2009-02-10 8:13 ` INTC issue Magnus Damm
2009-02-10 10:28 ` Yoshihiro Shimoda
2009-02-12 12:09 ` Magnus Damm
2009-02-17 6:21 ` Yoshihiro Shimoda
2009-02-24 14:12 ` Magnus Damm
2009-02-25 4:11 ` Yoshihiro Shimoda
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=498AD5E4.8050809@renesas.com \
--to=shimoda.yoshihiro@renesas.com \
--cc=linux-sh@vger.kernel.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: link
Be 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