From: adharmap@codeaurora.org (Abhijeet Dharmapurikar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Common GIC entry macro code
Date: Wed, 10 Nov 2010 12:28:00 -0800 [thread overview]
Message-ID: <4CDB0050.3090509@codeaurora.org> (raw)
In-Reply-To: <20101110070043.18735.53764.sendpatchset@t400s>
Magnus,
The patch assumes that PPI's could be nothing but timers. On msm we
have other interrupts which are PPI's.
I have tested this and doesn't work for msm. The reason being we treat
PPI timer interrupts as usual interrupts, meaning use do_asm_IRQ()
instead of do_local_timer(). Besides there are other non timer
interrupts that are PPIs and we need do_asm_IRQ() to be called for them.
You might want to exclude msm from this patch.
> +++ work/arch/arm/include/asm/hardware/entry-macro-gic.S 2010-11-10 15:20:15.000000000 +0900
> + .macro get_irqnr_and_base, irqnr, irqstat, base, tmp
> +
> + ldr \irqstat, [\base, #GIC_CPU_INTACK]
> + /* bits 12-10 = src CPU, 9-0 = int # */
> +
> + ldr \tmp, =1021
> + bic \irqnr, \irqstat, #0x1c00
> + cmp \irqnr, #29
Not all the PPI's are timer interrupts on MSM. MSM would need this to be
compared to 15 rather than 29.
> --- 0001/arch/arm/mach-msm/include/mach/entry-macro-qgic.S
> +++ work/arch/arm/mach-msm/include/mach/entry-macro-qgic.S 2010-11-10 15:27:06.000000000 +0900
> - */
> -
> - .macro get_irqnr_and_base, irqnr, irqstat, base, tmp
> -
> - ldr \irqstat, [\base, #GIC_CPU_INTACK] /* bits 12-10 =srcCPU,
> - 9-0 =int # */
> -
> - bic \irqnr, \irqstat, #0x1c00 @mask src
> - cmp \irqnr, #15
See above line
Thanks,
Abhijeet
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
--
prev parent reply other threads:[~2010-11-10 20:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 7:00 [PATCH] ARM: Common GIC entry macro code Magnus Damm
2010-11-10 7:16 ` Shilimkar, Santosh
2010-11-10 7:35 ` Magnus Damm
2010-11-10 7:47 ` Srinidhi Kasagar
2010-11-10 20:28 ` Abhijeet Dharmapurikar [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=4CDB0050.3090509@codeaurora.org \
--to=adharmap@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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).