From: Jason Cooper <jason@lakedaemon.net>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Marc Zyngier <marc.zyngier@arm.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Andrew Lunn <andrew@lunn.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Gregory Clement <gregory.clement@free-electrons.com>,
Nadav Haklai <nadavh@marvell.com>,
Lior Amsalem <alior@marvell.com>
Subject: Re: [PATCH v3] irqchip: irq-mvebu-odmi: new driver for platform MSI on Marvell 7K/8K
Date: Fri, 19 Feb 2016 15:57:28 +0000 [thread overview]
Message-ID: <20160219155728.GD958@io.lakedaemon.net> (raw)
In-Reply-To: <1455888883-5127-1-git-send-email-thomas.petazzoni@free-electrons.com>
On Fri, Feb 19, 2016 at 02:34:43PM +0100, Thomas Petazzoni wrote:
> This commits adds a new irqchip driver that handles the ODMI
> controller found on Marvell 7K/8K processors. The ODMI controller
> provide MSI interrupt functionality to on-board peripherals, much like
> the GIC-v2m.
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
> Changes v2 -> v2:
> - Express NODMIS_SHIFT, NODMIS_PER_FRAME, NODMIS_MASK in term of each
> other. Suggested by Marc Zyngier.
> - Rework the global bitmask allocation to make sure we allocate a
> number of longs rather than a number of bytes, to avoid having the
> bitmap API (which operates on longs) access memory we haven't
> explicitly allocated. Reported by Marc Zyngier.
>
> Changes v1 -> v2:
> - Better commit title, as suggested by Marc Zyngier.
> - Improve the DT binding documentation, as suggested by Marc Zingier:
> add a reference to the GIC documentation, be more specific about
> the marvell,spi-base values, and add the requirement of the
> interrupt-parent property.
> - As suggested by Marc Zyngier, use a single global bitmap to
> allocate all ODMIs, regardless of the frame they belong to. As part
> of this change, the hwirq used to identify the interrupt inside the
> ODMI irqdomain are 0-based (instead of being based on their
> corresponding SPI base value), which allows to significantly
> simplify the allocation/free logic.
> ---
> .../marvell,odmi-controller.txt | 41 ++++
> drivers/irqchip/Kconfig | 4 +
> drivers/irqchip/Makefile | 1 +
> drivers/irqchip/irq-mvebu-odmi.c | 248 +++++++++++++++++++++
> 4 files changed, 294 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/interrupt-controller/marvell,odmi-controller.txt
> create mode 100644 drivers/irqchip/irq-mvebu-odmi.c
Applied to irqchip/mvebu with Marc's Reviewed-by.
thx,
Jason.
prev parent reply other threads:[~2016-02-19 15:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 13:34 [PATCH v3] irqchip: irq-mvebu-odmi: new driver for platform MSI on Marvell 7K/8K Thomas Petazzoni
2016-02-19 14:15 ` Marc Zyngier
2016-02-19 14:17 ` Thomas Petazzoni
2016-02-19 14:28 ` Jason Cooper
2016-02-19 14:47 ` Marc Zyngier
2016-02-19 14:50 ` Jason Cooper
2016-02-19 15:57 ` 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=20160219155728.GD958@io.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=alior@marvell.com \
--cc=andrew@lunn.ch \
--cc=gregory.clement@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=nadavh@marvell.com \
--cc=sebastian.hesselbarth@gmail.com \
--cc=tglx@linutronix.de \
--cc=thomas.petazzoni@free-electrons.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;
as well as URLs for NNTP newsgroup(s).