From: Yoshihiro Shimoda <shimoda.yoshihiro@renesas.com>
To: linux-sh@vger.kernel.org
Subject: Re: INTC issue
Date: Tue, 17 Feb 2009 06:21:51 +0000 [thread overview]
Message-ID: <499A577F.8070401@renesas.com> (raw)
In-Reply-To: <498AD5E4.8050809@renesas.com>
Hi Magnus-san!
I am very sorry for late reply.
Magnus Damm wrote:
- snip -
> How about the attached patch? It should fix the issue on sh7785 with
> only a few lines of added code.
Thank you for your comment and patch.
> Note that with this patch you now should use only one linux interrupt
> for the special hardware blocks that come with multiple vectors but
> only a single masking method. Look at the DMAC0/DMAC1/SCIF0/SCIF1 intc
> table changes for more information. The interrupt calculated from the
> first INTC_VECT in vectors[] is used to for all vectors with the same
> enum_id.
>
> Please let me know if the patch solves your issue. I'll break out the
> patch and fix up other processors and post a proper patch set in a
> little while if this change solves your problem.
When I used this patch and change DMAC driver, my issue was solved!
But I think that I might as well change DMAC only. For example, when SCIF
driver get same interrupt number, SCIF driver use sci_mpxed_interrupt().
Because this function check interrupt flag, overheads increase just a little.
The DMAC driver changes:
- fix register maps for SH7785. :)
- change DMAC irq number.
- add IRQF_SHARED flag of request_irq().
- add dummy args of request_irq() in sh_dmac_init().
Thanks,
Yoshihiro Shimoda
next prev parent reply other threads:[~2009-02-17 6:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 12:04 INTC issue Yoshihiro Shimoda
2009-02-10 8:13 ` Magnus Damm
2009-02-10 10:28 ` Yoshihiro Shimoda
2009-02-12 12:09 ` Magnus Damm
2009-02-17 6:21 ` Yoshihiro Shimoda [this message]
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=499A577F.8070401@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