From: jason@lakedaemon.net (Jason Cooper)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] irqchip: irq-mvebu-odmi: new driver for platform MSI on Marvell 7K/8K
Date: Fri, 19 Feb 2016 14:50:26 +0000 [thread overview]
Message-ID: <20160219145026.GC958@io.lakedaemon.net> (raw)
In-Reply-To: <56C72B01.4060005@arm.com>
On Fri, Feb 19, 2016 at 02:47:29PM +0000, Marc Zyngier wrote:
> On 19/02/16 14:28, Jason Cooper wrote:
> > On Fri, Feb 19, 2016 at 02:15:46PM +0000, Marc Zyngier wrote:
> >> On 19/02/16 13:34, 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
> >>
> >> Reviewed-by: Marc Zyngier <marc.zyngier@arm.com>
> >>
> >> I'll queue that for 4.6.
> >
> > I had it on my list to queue up, but you beat me to it. :-)
>
> Ah, sorry! The reason I was eager to queue it is because I have some
> related changes in the GIC/GICv2m department, simplifying a few things
> there:
>
> http://git.kernel.org/cgit/linux/kernel/git/maz/arm-platforms.git/commit/?h=irq/gic-4.6&id=9b29f74f6b4b56aa4bb5cc91474aa2451de5c628
>
> I'll post this on the list later today.
ah, no problem. Whichever is easiest for you. Just let me know.
thx,
Jason.
next prev parent reply other threads:[~2016-02-19 14:50 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 [this message]
2016-02-19 15:57 ` Jason Cooper
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=20160219145026.GC958@io.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=linux-arm-kernel@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 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).