linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] r8a7779: Route all interrupts to ARM
Date: Thu, 21 Jun 2012 11:45:31 +0000	[thread overview]
Message-ID: <201206211345.31969.rjw@sisk.pl> (raw)
In-Reply-To: <1340109108-9354-1-git-send-email-phil.edworthy@renesas.com>

Hi,

Can you please provide a changelog describing why the change is being made?

Rafael


On Tuesday, June 19, 2012, Phil Edworthy wrote:
> 
> Signed-off-by: Phil Edworthy <phil.edworthy@renesas.com>
> ---
>  arch/arm/mach-shmobile/intc-r8a7779.c |    7 +++++++
>  1 files changed, 7 insertions(+), 0 deletions(-)
> 
> diff --git a/arch/arm/mach-shmobile/intc-r8a7779.c b/arch/arm/mach-shmobile/intc-r8a7779.c
> index 550b23d..f04fad4 100644
> --- a/arch/arm/mach-shmobile/intc-r8a7779.c
> +++ b/arch/arm/mach-shmobile/intc-r8a7779.c
> @@ -35,6 +35,9 @@
>  #define INT2SMSKCR3 0xfe7822ac
>  #define INT2SMSKCR4 0xfe7822b0
>  
> +#define INT2NTSR0 0xfe700060
> +#define INT2NTSR1 0xfe700064
> +
>  static int r8a7779_set_wake(struct irq_data *data, unsigned int on)
>  {
>  	return 0; /* always allow wakeup */
> @@ -49,6 +52,10 @@ void __init r8a7779_init_irq(void)
>  	gic_init(0, 29, gic_dist_base, gic_cpu_base);
>  	gic_arch_extn.irq_set_wake = r8a7779_set_wake;
>  
> +	/* route all interrupts to ARM */
> +	__raw_writel(0xffffffff, INT2NTSR0);
> +	__raw_writel(0x3fffffff, INT2NTSR1);
> +
>  	/* unmask all known interrupts in INTCS2 */
>  	__raw_writel(0xfffffff0, INT2SMSKCR0);
>  	__raw_writel(0xfff7ffff, INT2SMSKCR1);
> 


      reply	other threads:[~2012-06-21 11:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-19 12:31 [PATCH] r8a7779: Route all interrupts to ARM Phil Edworthy
2012-06-21 11:45 ` Rafael J. Wysocki [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=201206211345.31969.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --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).