linux-kernel - Re: [PATCH v4] openrisc: irq: use irqchip framework

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20140701122514.GF23978@titan.lakedaemon.net>
Date:	Tue, 1 Jul 2014 08:25:14 -0400
From:	Jason Cooper <jason@...edaemon.net>
To:	Stefan Kristiansson <stefan.kristiansson@...nalahti.fi>
Cc:	linux-kernel@...r.kernel.org, linux@...ts.openrisc.net,
	jonas@...thpole.se, tglx@...utronix.de, geert@...ux-m68k.org
Subject: Re: [PATCH v4] openrisc: irq: use irqchip framework

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@...nalahti.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/