From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Yuriy Kolerov <yuriy.kolerov@synopsys.com>,
<linux-snps-arc@lists.infradead.org>
Cc: Alexey Brodkin <Alexey.Brodkin@synopsys.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARCv2: intc: Use kflag if STATUS32.IE must be reset
Date: Fri, 30 Sep 2016 14:18:35 -0700 [thread overview]
Message-ID: <b95120e6-010b-0822-e915-2f1abf964a56@synopsys.com> (raw)
In-Reply-To: <1473695703-29547-1-git-send-email-yuriy.kolerov@synopsys.com>
On 09/12/2016 08:55 AM, Yuriy Kolerov wrote:
> In the end of "arc_init_IRQ" STATUS32.IE flag is going to be affected by
> "flag" instruction but "flag" never touches IE flag on ARCv2. So "kflag"
> instruction must be used instead of "flag".
>
> Signed-off-by: Yuriy Kolerov <yuriy.kolerov@synopsys.com>
> ---
> arch/arc/kernel/intc-arcv2.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arc/kernel/intc-arcv2.c b/arch/arc/kernel/intc-arcv2.c
> index 6c24faf..62b59409 100644
> --- a/arch/arc/kernel/intc-arcv2.c
> +++ b/arch/arc/kernel/intc-arcv2.c
> @@ -74,7 +74,7 @@ void arc_init_IRQ(void)
> tmp = read_aux_reg(0xa);
> tmp |= STATUS_AD_MASK | (irq_prio << 1);
> tmp &= ~STATUS_IE_MASK;
> - asm volatile("flag %0 \n"::"r"(tmp));
> + asm volatile("kflag %0 \n"::"r"(tmp));
Revisiting this in light of ongoing 2 priority interrupt support for HS38 cores.
It seems there is no need to fiddle with interrupt bits here at all.
init/main.c now has well known checkpoints where it explicitly disables the
interrupts in early boot code and enables them when time is right. So when we land
in arc_init_IRQ() interrupts have already been disabled.
So I'm dropping this patch and instead adding another one which removes the intr
bits touching part !
OK ?
-Vineet
prev parent reply other threads:[~2016-09-30 21:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 15:55 Yuriy Kolerov
2016-09-20 21:48 ` Vineet Gupta
2016-09-30 21:18 ` Vineet Gupta [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=b95120e6-010b-0822-e915-2f1abf964a56@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=Alexey.Brodkin@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=yuriy.kolerov@synopsys.com \
/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
all inboxes | Powered by JetHome®