From: Stefan Agner <stefan@agner.ch>
To: tglx@linutronix.de, jason@lakedaemon.net, marc.zyngier@arm.com
Cc: u.kleine-koenig@pengutronix.de, shawn.guo@linaro.org,
kernel@pengutronix.de, arnd@arndb.de, robh+dt@kernel.org,
pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
linux@arm.linux.org.uk, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, stefan@agner.ch
Subject: [PATCH v3 0/3] irqchip: vf610-mscm: add support for MSCM interrupt router
Date: Tue, 16 Dec 2014 22:45:44 +0100 [thread overview]
Message-ID: <1418766347-6225-1-git-send-email-stefan@agner.ch> (raw)
Splitted out version of the MSCM driver. My first driver based on the
routeable domain support and was part of the Vybrid Cortex-M4 support
patchset.
So far the MSCM interrupt router was initialized by the boot loader
and configured all interrupts for the Cortex-A5 CPU. There are two
use cases where a proper driver is necessary:
- To run Linux on the Cortex-M4. When the kernel is running on the
non-preconfigured CPU, the interrupt router need to be configured
properly.
- To support deeper sleep modes: LPSTOP clears the interrupt router
configuration, hence a driver needs to restore the configuration
on resume.
I created a seperate patchset for that driver which hopefully makes
it easier to get it into mergeable state.
The patchset is based on the master branch of Linus as of today.
Since I identified some registers likely to be used by other drivers
(e.g. CPU ID or the CPU Generate Interrupt Register) I also added
the "syscon" compatible string to make the registers available for
other drivers in case needed.
Changes since v2
- Use two cell layout for MSCM interrupt router
- Move peripheral interrupt properties to base device tree vfxxx.dtsi
- Use generic two cell xlate (irq_domain_xlate_twocell)
- Add syscon to compatible string
- Remove some line breaks for better readability
Changes since v1 (part of Vybrid Cortex-M4 support)
- Rewrite with irqdomain hierarchy
- Implemented as proper irqchip and move to driver/irqchip/
- Doesn't work on Cortex-M4 anymore (NVIC as parent is not yet
implemented)
Stefan Agner (3):
irqchip: vf610-mscm: add support for MSCM interrupt router
irqchip: vf610-mscm: dt-bindings: add MSCM bindings
ARM: dts: vf610: add Miscellaneous System Control Module (MSCM)
.../bindings/arm/freescale/fsl,vf610-mscm.txt | 19 +++
arch/arm/boot/dts/vf500.dtsi | 128 +-------------
arch/arm/boot/dts/vfxxx.dtsi | 42 +++++
arch/arm/mach-imx/Kconfig | 1 +
drivers/irqchip/Kconfig | 11 ++
drivers/irqchip/Makefile | 1 +
drivers/irqchip/irq-vf610-mscm.c | 186 +++++++++++++++++++++
7 files changed, 264 insertions(+), 124 deletions(-)
create mode 100644 Documentation/devicetree/bindings/arm/freescale/fsl,vf610-mscm.txt
create mode 100644 drivers/irqchip/irq-vf610-mscm.c
--
2.1.3
next reply other threads:[~2014-12-16 21:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-16 21:45 Stefan Agner [this message]
2014-12-16 21:45 ` [PATCH v3 1/3] irqchip: vf610-mscm: add support for MSCM interrupt router Stefan Agner
[not found] ` <1418766347-6225-1-git-send-email-stefan-XLVq0VzYD2Y@public.gmane.org>
2014-12-16 21:45 ` [PATCH v3 2/3] irqchip: vf610-mscm: dt-bindings: add MSCM bindings Stefan Agner
2014-12-16 21:45 ` [PATCH v3 3/3] ARM: dts: vf610: add Miscellaneous System Control Module (MSCM) Stefan Agner
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=1418766347-6225-1-git-send-email-stefan@agner.ch \
--to=stefan@agner.ch \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jason@lakedaemon.net \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=shawn.guo@linaro.org \
--cc=tglx@linutronix.de \
--cc=u.kleine-koenig@pengutronix.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).