From: Manuel Lauss <mano@roarinelk.homelinux.net>
To: linux-sh@vger.kernel.org
Subject: Re: Questions about the interrupt controller
Date: Fri, 29 Feb 2008 20:35:14 +0000 [thread overview]
Message-ID: <47C86C82.3060908@roarinelk.homelinux.net> (raw)
In-Reply-To: <38b2ab8a0802290508t5e20a0cmfd04e35f0fc533a3@mail.gmail.com>
> The possible case where it couldn't be used is when the irqs are edge
> triggered.
>
> Another drawback is that we can't mask one single IRL irq but we have
> to mask all IRQs whose priority are less than the IRL irq's priority,
According to the SH7760 datasheet, the INTC compares the priority of
_every_ interrupt (IRL, On-chip peripheral) to the IMASK register. If
IRQ priority is HIGHER than the level set in IMASK then the interrupt is
accepted and the exception handler is invoked.
So no, I don't believen you can have a "sane" IRL irq handling scheme
only with IMASK irq chip.
>> >> > The documentation says: "Other compatible interrupt controllers can be
>> >> > cascaded with INTC.". Where can I find some details about that ?
>> >>
>> >> have a look at set_irq_chained_handler() function, for example:
>> >>
>> >
>> > [snip]
>> >
>> > Actually I'm wondering what does 'compatible' mean.... ?
>>
>> 4 lines which are pulled low to signal IRQ condition and the ~bitmask of
>> those 4 lines indicates the number of the irq to trigger?
>> Thats my understanding of how it works...
>>
>
> Do you know any datasheets out there describing this ?
Take the SH7751/SH7760/SH7780 datasheets for example, it's described in
the INTC chapter (Page 217 of the 7760 manual).
> In the same vein, could you point out some good documents about the SH
> architecture ? The ones available from Renesas web site aren't very good
> IMHO
Maybe ST has some manuals for their ST40 based parts (also SH4 variants)
on their site.
--
ml.
next prev parent reply other threads:[~2008-02-29 20:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-29 13:08 Questions about the interrupt controller Francis Moreau
2008-02-29 15:32 ` Manuel Lauss
2008-02-29 16:19 ` Francis Moreau
2008-02-29 17:20 ` Manuel Lauss
2008-02-29 17:29 ` Manuel Lauss
2008-02-29 17:35 ` Manuel Lauss
2008-02-29 20:02 ` Francis Moreau
2008-02-29 20:05 ` Francis Moreau
2008-02-29 20:35 ` Manuel Lauss [this message]
2008-03-03 15:55 ` Stuart MENEFY
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=47C86C82.3060908@roarinelk.homelinux.net \
--to=mano@roarinelk.homelinux.net \
--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