From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 00/03] sh: SDHI vector merge
Date: Tue, 09 Feb 2010 09:28:14 +0000 [thread overview]
Message-ID: <20100209092814.GC17722@linux-sh.org> (raw)
In-Reply-To: <20100209064940.31154.52216.sendpatchset@rxone.opensource.se>
On Tue, Feb 09, 2010 at 03:49:40PM +0900, Magnus Damm wrote:
> [PATCH 01/03] sh: sh7722/Migo-R SDHI vector merge
> [PATCH 02/03] sh: sh7723/AP325 SDHI vector merge
> [PATCH 03/03] sh: sh7724/Ecovec24/KFR2R09/MS7724SE SDHI vector merge
>
> These patches merge the SDHI interrupt vectors in the INTC tables
> for sh7722, sh7723 and sh7724 processors. The interrupt number in
> Linux is also changed to the first of the vectors, so the board
> specific platform data is also updated for a bunch of boards.
>
> With these patches in place we are one step closer to SDHI hotplug.
On Tue, Feb 09, 2010 at 04:17:20PM +0900, Magnus Damm wrote:
> This patch updates the shared INTC code to use
> set_irq_chained_handler() for intc_redirect_irq().
>
> With this in place request_irq() on a merged irq
> which has been redirected will now return -EINVAL
> instead of 0 together with a crash. This thanks to
> the protection of the IRQ_NOREQUEST flag set for
> chained interrupt handlers.
On Tue, Feb 09, 2010 at 05:22:30PM +0900, Magnus Damm wrote:
> Break out sh7723 div4 clocks for SIU and IRDA as
> reparent / enable clocks. Similar to the SIU clock
> patch for sh7722 by Guennadi.
All applied, thanks.
prev parent reply other threads:[~2010-02-09 9:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-09 6:49 [PATCH 00/03] sh: SDHI vector merge Magnus Damm
2010-02-09 9:28 ` 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=20100209092814.GC17722@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).