From: Vineet.Gupta1@synopsys.com (Vineet Gupta)
To: linux-snps-arc@lists.infradead.org
Subject: [PATCH v4 0/2] ARC: Set of patches for IRQ subsystem
Date: Tue, 8 Nov 2016 12:25:09 -0800 [thread overview]
Message-ID: <f6aa5332-bd7d-d37d-eda7-e6d7033005fc@synopsys.com> (raw)
In-Reply-To: <1478588912-3991-1-git-send-email-yuriy.kolerov@synopsys.com>
On 11/07/2016 11:08 PM, Yuriy Kolerov wrote:
> The first patch fixes misuse of IRQ numbers. In some places of the
> Linux kernel for ARC hardware IRQ numbers are used as virtual IRQ
> numbers and obviously it is wrong.
>
> The second patch forces the kernel to set a simple distribution mode
> for common interrupts in cases when such interrupts are routed to a
> single core.
>
> Yuriy Kolerov (2):
> ARC: IRQ: Do not use hwirq as virq and vice versa
> ARCv2: MCIP: Use IDU_M_DISTRI_DEST mode if there is only 1 destination
> core
>
> arch/arc/include/asm/smp.h | 4 ++--
> arch/arc/kernel/mcip.c | 33 ++++++++++++++++++++-------------
> arch/arc/kernel/smp.c | 13 +++++++++----
> 3 files changed, 31 insertions(+), 19 deletions(-)
Thx Yuriy.
Added to for-curr !
-Vineet
WARNING: multiple messages have this Message-ID (diff)
From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Yuriy Kolerov <yuriy.kolerov@synopsys.com>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>
Cc: "Alexey.Brodkin@synopsys.com" <Alexey.Brodkin@synopsys.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 0/2] ARC: Set of patches for IRQ subsystem
Date: Tue, 8 Nov 2016 12:25:09 -0800 [thread overview]
Message-ID: <f6aa5332-bd7d-d37d-eda7-e6d7033005fc@synopsys.com> (raw)
In-Reply-To: <1478588912-3991-1-git-send-email-yuriy.kolerov@synopsys.com>
On 11/07/2016 11:08 PM, Yuriy Kolerov wrote:
> The first patch fixes misuse of IRQ numbers. In some places of the
> Linux kernel for ARC hardware IRQ numbers are used as virtual IRQ
> numbers and obviously it is wrong.
>
> The second patch forces the kernel to set a simple distribution mode
> for common interrupts in cases when such interrupts are routed to a
> single core.
>
> Yuriy Kolerov (2):
> ARC: IRQ: Do not use hwirq as virq and vice versa
> ARCv2: MCIP: Use IDU_M_DISTRI_DEST mode if there is only 1 destination
> core
>
> arch/arc/include/asm/smp.h | 4 ++--
> arch/arc/kernel/mcip.c | 33 ++++++++++++++++++++-------------
> arch/arc/kernel/smp.c | 13 +++++++++----
> 3 files changed, 31 insertions(+), 19 deletions(-)
Thx Yuriy.
Added to for-curr !
-Vineet
next prev parent reply other threads:[~2016-11-08 20:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-08 7:08 [PATCH v4 0/2] ARC: Set of patches for IRQ subsystem Yuriy Kolerov
2016-11-08 7:08 ` Yuriy Kolerov
2016-11-08 7:08 ` [PATCH v4 1/2] ARC: IRQ: Do not use hwirq as virq and vice versa Yuriy Kolerov
2016-11-08 7:08 ` Yuriy Kolerov
2016-11-08 7:20 ` Vineet Gupta
2016-11-08 7:20 ` Vineet Gupta
2016-11-08 9:30 ` Noam Camus
2016-11-08 9:30 ` Noam Camus
2016-11-08 20:23 ` Vineet Gupta
2016-11-08 20:23 ` Vineet Gupta
2016-11-08 7:08 ` [PATCH v4 2/2] ARCv2: MCIP: Use IDU_M_DISTRI_DEST mode if there is only 1 destination core Yuriy Kolerov
2016-11-08 7:08 ` Yuriy Kolerov
2016-11-08 20:25 ` Vineet Gupta [this message]
2016-11-08 20:25 ` [PATCH v4 0/2] ARC: Set of patches for IRQ subsystem Vineet Gupta
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=f6aa5332-bd7d-d37d-eda7-e6d7033005fc@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=linux-snps-arc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.