From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh: extend INTC with struct intc_hw_desc
Date: Tue, 09 Feb 2010 09:27:32 +0000 [thread overview]
Message-ID: <20100209092732.GB17722@linux-sh.org> (raw)
In-Reply-To: <20100209042446.30785.32661.sendpatchset@rxone.opensource.se>
On Tue, Feb 09, 2010 at 01:24:46PM +0900, Magnus Damm wrote:
> This patch updates the INTC code by moving all vectors,
> groups and registers from struct intc_desc to struct
> intc_hw_desc.
>
> The idea is that INTC tables should go from using the
> macro(s) DECLARE_INTC_DESC..() only to using struct
> intc_desc with name and hw initialized using the macro
> INTC_HW_DESC(). This move makes it easy to initialize
> an extended struct intc_desc in the future.
On Tue, Feb 09, 2010 at 01:29:22PM +0900, Magnus Damm wrote:
> Extend the shared INTC code with force_enable support to
> allow keeping mask bits statically enabled. Needed by
> upcoming INTC SDHI patches that mux together a bunch of
> vectors to a single linux interrupt which is masked by
> a priority register, but needs individual mask bits
> constantly enabled.
These two have been rolled in to the sh/intc-extension topic branch and
folded in to the sh tree. When you have patches ready for the genesis
tree that depend on these make sure you have the dependencies clearly
stated and I'll roll them in there at that point, too.
prev parent reply other threads:[~2010-02-09 9:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-09 4:24 [PATCH] sh: extend INTC with struct intc_hw_desc Magnus Damm
2010-02-09 9:27 ` Paul Mundt [this message]
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=20100209092732.GB17722@linux-sh.org \
--to=lethal@linux-sh.org \
--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;
as well as URLs for NNTP newsgroup(s).