public inbox for linux-sh@vger.kernel.org
 help / color / mirror / Atom feed
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 17:20:57 +0000	[thread overview]
Message-ID: <47C83EF9.6040901@roarinelk.homelinux.net> (raw)
In-Reply-To: <38b2ab8a0802290508t5e20a0cmfd04e35f0fc533a3@mail.gmail.com>

Francis Moreau wrote:
> Hello Manuel,
> 
> On Fri, Feb 29, 2008 at 4:32 PM, Manuel Lauss
> <mano@roarinelk.homelinux.net> wrote:
>>  Again, I can only tell for my SH7760 platform. You need to register your
>>  own irq_chip with mask/unmask/mask_ack callbacks. On the SH7760, the
>>  IRLs trigger as vectors 0-15, and one has to provide external logic to
>>  do the irq masking/acking. SH7780 and newer IIRC provide an INTC
>>  register for that.
>>
>>  This is code I use:
>>
> 
> [snip]
> 
> But couldn't you use make_imask_irq() instead ?

Yes, that works too; at least for the IRL irqs if the source does not
have to be acked (CF cards).


>>  > 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...

-- 
  ml.

  parent reply	other threads:[~2008-02-29 17:20 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 [this message]
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
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=47C83EF9.6040901@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