From: Palmer Dabbelt <palmer@sifive.com>
To: tglx@linutronix.de, jason@lakedaemon.net, marc.zyngier@arm.com,
robh+dt@kernel.org, mark.rutland@arm.com
Cc: Palmer Dabbelt <palmer@sifive.com>,
aou@eecs.berkeley.edu, shorne@gmail.com,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-riscv@lists.infradead.org
Subject: Driver for the RISC-V Interrupt Controller
Date: Fri, 22 Jun 2018 16:20:03 -0700 [thread overview]
Message-ID: <20180622232006.12158-1-palmer@sifive.com> (raw)
The RISC-V ISA mandantes the presence of a simple, per-hart (hardware
thread) interrupt controller availiable to supervisor mode. This patch
set adds a driver for this interrupt controller.
The patch set itself has been around in various flavors for a while, but
as far as I remember it's never been properly cleaned up and submitted
before. As it currently stands it's essentially three seperate patches,
but as they're all intertwined I'm keeping them together. Sorry if
that's the wrong thing to do.
The patches are:
* A cleanup to arch/riscv to remove a bit of the old initialization
mechanism that snuck in to our arch port. This patch is trivial, so
unless there's any feedback on it specificly I'll include it in my
next pull request.
* The addition of device tree bindings to describe "riscv,cpu-intc".
* The actual irqchip driver. If this gets merged before the arch/riscv
patch then it'll cause our build to fail, but I'm assuming this will
be targeted at the next merge window so we should be safe.
next reply other threads:[~2018-06-22 23:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 23:20 Palmer Dabbelt [this message]
2018-06-22 23:20 ` [PATCH 1/3] RISC-V: Don't include irq-riscv-intc.h Palmer Dabbelt
2018-06-23 7:25 ` Christoph Hellwig
2018-06-22 23:20 ` [PATCH 2/3] dt-bindings: interrupt-controller: RISC-V local interrupt controller docs Palmer Dabbelt
2018-06-25 20:04 ` Christoph Böhmwalder
2018-08-02 20:30 ` Palmer Dabbelt
2018-07-03 20:10 ` Rob Herring
2018-06-22 23:20 ` [PATCH 3/3] irqchip: RISC-V Local Interrupt Controller Driver Palmer Dabbelt
2018-06-23 0:08 ` Randy Dunlap
2018-08-02 18:30 ` Palmer Dabbelt
2018-06-23 7:28 ` Christoph Hellwig
2018-06-23 8:56 ` Thomas Gleixner
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=20180622232006.12158-1-palmer@sifive.com \
--to=palmer@sifive.com \
--cc=aou@eecs.berkeley.edu \
--cc=devicetree@vger.kernel.org \
--cc=jason@lakedaemon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=shorne@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).