public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Colin Cross <ccross@android.com>, Russell King <linux@arm.linux.org.uk>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Catalin Marinas <catalin.marinas@arm.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Abhijeet Dharmapurikar <adharmap@codeaurora.org>
Subject: Re: [PATCH] ARM: gic: Allow gic arch extensions to provide irqchip flags
Date: Sat, 09 Jul 2011 17:03:13 -0700	[thread overview]
Message-ID: <4E18EC41.2080102@ti.com> (raw)
In-Reply-To: <1307925960-28839-1-git-send-email-ccross@android.com>

On 6/12/2011 5:45 PM, Colin Cross wrote:
> Tegra can benefit from the IRQCHIP_MASK_ON_SUSPEND flag, allow it
> to be passed to the gic irq chip.
>
> Signed-off-by: Colin Cross<ccross@android.com>

I missed this patch. Looks good to me and I think can
be merged in rc as well.
Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>

> ---
>   arch/arm/common/gic.c |    1 +
>   1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/common/gic.c b/arch/arm/common/gic.c
> index 8d62e07..a6c28a0 100644
> --- a/arch/arm/common/gic.c
> +++ b/arch/arm/common/gic.c
> @@ -576,6 +576,7 @@ void __init gic_init(unsigned int gic_nr, unsigned int irq_start,
>   	if (gic_nr == 0)
>   		gic_cpu_base_addr = cpu_base;
>
> +	gic_chip.flags |= gic_arch_extn.flags;
>   	gic_dist_init(gic, irq_start);
>   	gic_cpu_init(gic);
>   	gic_cpu_pm_init(gic);

Russell,
Any thoughts on this fix?

Regards
Santosh

  reply	other threads:[~2011-07-10  0:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-13  0:45 [PATCH] ARM: gic: Allow gic arch extensions to provide irqchip flags Colin Cross
2011-07-10  0:03 ` Santosh Shilimkar [this message]
2011-07-10  0:08   ` Colin Cross

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=4E18EC41.2080102@ti.com \
    --to=santosh.shilimkar@ti.com \
    --cc=adharmap@codeaurora.org \
    --cc=catalin.marinas@arm.com \
    --cc=ccross@android.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=tglx@linutronix.de \
    /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