mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jason Cooper <jason@lakedaemon.net>
To: Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>
Cc: linux-kernel@vger.kernel.org, linux@openrisc.net,
	jonas@southpole.se, tglx@linutronix.de, geert@linux-m68k.org
Subject: Re: [PATCH v4] openrisc: irq: use irqchip framework
Date: Tue, 1 Jul 2014 08:25:14 -0400	[thread overview]
Message-ID: <20140701122514.GF23978@titan.lakedaemon.net> (raw)
In-Reply-To: <20140621200202.GH21711@titan.lakedaemon.net>

On Sat, Jun 21, 2014 at 04:02:02PM -0400, Jason Cooper wrote:
> Stefan,
> 
> On Mon, May 26, 2014 at 11:31:42PM +0300, Stefan Kristiansson wrote:
> > In addition to consolidating the or1k-pic with other interrupt
> > controllers, this makes OpenRISC less tied to its on-cpu
> > interrupt controller.
> > 
> > All or1k-pic specific parts are moved out of irq.c and into
> > drivers/irqchip/irq-or1k-pic.c
> > 
> > In that transition, the funtionality have been divided into
> > three chip variants.
> > One that handles level triggered interrupts, one that handles edge
> > triggered interrupts and one that handles the interrupt
> > controller that is present in the or1200 OpenRISC cpu
> > implementation.
> > 
> > Signed-off-by: Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>
> > ---
> > Changes in v2:
> >  - Move or1k-pic related code into irq-or1k-pic
> >  - Add documentation for device tree bindings
> > 
> > Changes in v3:
> >  - Split level-, edge-triggered and or1200 implementation into seperate
> >    chip variants.
> > 
> > Changes in v4:
> >  - Fix typos in documentation
> > ---
> >  .../interrupt-controller/opencores,or1k-pic.txt    |  23 +++
> >  arch/openrisc/Kconfig                              |   1 +
> >  arch/openrisc/include/asm/irq.h                    |   3 +
> >  arch/openrisc/kernel/irq.c                         | 146 ++---------------
> >  drivers/irqchip/Kconfig                            |   4 +
> >  drivers/irqchip/Makefile                           |   1 +
> >  drivers/irqchip/irq-or1k-pic.c                     | 182 +++++++++++++++++++++
> >  7 files changed, 227 insertions(+), 133 deletions(-)
> >  create mode 100644 Documentation/devicetree/bindings/interrupt-controller/opencores,or1k-pic.txt
> >  create mode 100644 drivers/irqchip/irq-or1k-pic.c
> 
> I've now applied this to irqchip/unstable with Jonas' Ack to get it some
> time in -next.  As the name implies, I can rebase or edit this as
> needed.

Now moved into irqchip/core.

thx,

Jason.

      reply	other threads:[~2014-07-01 12:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-26 20:31 Stefan Kristiansson
2014-05-26 20:52 ` Geert Uytterhoeven
2014-05-27  6:47   ` Jonas Bonn
2014-05-29 20:28     ` Stefan Kristiansson
2014-05-30 11:08       ` Jonas Bonn
2014-06-21  2:04       ` Jason Cooper
2014-06-21  7:13         ` Stefan Kristiansson
2014-06-21 20:02 ` Jason Cooper
2014-07-01 12:25   ` Jason Cooper [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=20140701122514.GF23978@titan.lakedaemon.net \
    --to=jason@lakedaemon.net \
    --cc=geert@linux-m68k.org \
    --cc=jonas@southpole.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@openrisc.net \
    --cc=stefan.kristiansson@saunalahti.fi \
    --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

all inboxes | Powered by JetHome®