mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Yuriy Kolerov <yuriy.kolerov@synopsys.com>,
	<linux-snps-arc@lists.infradead.org>
Cc: <Alexey.Brodkin@synopsys.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/4] Use build registers for getting numbers of interrupts
Date: Wed, 1 Feb 2017 12:58:24 -0800	[thread overview]
Message-ID: <e3e7f7c8-57f3-e9da-158d-6bae19dd87a8@synopsys.com> (raw)
In-Reply-To: <1485863124-26426-1-git-send-email-yuriy.kolerov@synopsys.com>

On 01/31/2017 03:45 AM, Yuriy Kolerov wrote:
> A summary:
> 
>   * Use build registers for getting numbers of interrupts both for
>     core interrupt controller and for IDU interrupt controller.
>   * Set a default priority for all core interrupt to prevent
>     unexpected switching of banks of registers.
>   * Remove option for setting number of interrupts since it does
>     not affect a number of interrupts in IRQ domains and breaks
>     portability since it is impossible to change size of table of
>     interrupts after linkage.
> 
> Change in v2:
> 
>   * Squash some commits.
>   * Do not move a structure for control register of core intc to
>     the header since it is used only once.
> 
> Yuriy Kolerov (4):
>   ARCv2: IRQ: Move structure for build register of core intc to the
>     header
>   ARCv2: IRQ: Remove option for setting number of interrupts
>   ARCv2: IRQ: Use build registers for getting numbers of interrupts
>   ARCv2: IRQ: Set a default priority for all core interrupts
> 
>  arch/arc/Kconfig               | 11 -----------
>  arch/arc/include/asm/arcregs.h | 11 +++++++++++
>  arch/arc/include/asm/irq.h     | 32 +++++++++++++++++++++++++++++---
>  arch/arc/kernel/entry-arcv2.S  |  3 ++-
>  arch/arc/kernel/intc-arcv2.c   | 31 ++++++++++++++++++++-----------
>  arch/arc/kernel/mcip.c         | 31 +++++++++++++++++++------------
>  include/soc/arc/mcip.h         | 17 +++++++++++++++++
>  7 files changed, 98 insertions(+), 38 deletions(-)
> 

Hi Yuriy,

I've reworked your series a bit and pushed to my for-next.

Care to take a look please.

Thx,
-Vineet

  parent reply	other threads:[~2017-02-01 20:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-31 11:45 Yuriy Kolerov
2017-01-31 11:45 ` [PATCH v2 1/4] ARCv2: IRQ: Move structure for build register of core intc to the header Yuriy Kolerov
2017-01-31 17:40   ` Vineet Gupta
2017-01-31 18:15   ` Vineet Gupta
2017-01-31 11:45 ` [PATCH v2 2/4] ARCv2: IRQ: Remove option for setting number of interrupts Yuriy Kolerov
2017-01-31 17:40   ` Vineet Gupta
2017-01-31 11:45 ` [PATCH v2 3/4] ARCv2: IRQ: Use build registers for getting numbers " Yuriy Kolerov
2017-01-31 17:46   ` Vineet Gupta
2017-01-31 11:45 ` [PATCH v2 4/4] ARCv2: IRQ: Set a default priority for all core interrupts Yuriy Kolerov
2017-01-31 17:54   ` Vineet Gupta
2017-02-01 12:54     ` Yuriy Kolerov
2017-02-01 20:58 ` Vineet Gupta [this message]
2017-02-01 23:59   ` [PATCH v2 0/4] Use build registers for getting numbers of interrupts Yuriy Kolerov

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=e3e7f7c8-57f3-e9da-158d-6bae19dd87a8@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®