From: Thomas Gleixner <tglx@linutronix.de>
To: Stefan Agner <stefan@agner.ch>
Cc: jason@lakedaemon.net, marc.zyngier@arm.com,
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
Subject: Re: [PATCH RESEND v3 0/3] irqchip: vf610-mscm: add support for MSCM interrupt router
Date: Mon, 26 Jan 2015 11:16:45 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.11.1501261115300.5526@nanos> (raw)
In-Reply-To: <1421309046-22452-1-git-send-email-stefan@agner.ch>
On Thu, 15 Jan 2015, Stefan Agner wrote:
> 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.
>
> 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.
>
> This resend version of this patchset is rebased on v3.19-rc4.
Has the discussion with Marc on the original V3 set been resolved?
What about the DT bindings? I'm relucant to pick that up w/o acks from
the DT folks.
Thanks,
tglx
next prev parent reply other threads:[~2015-01-26 10:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 8:04 [PATCH RESEND v3 0/3] irqchip: vf610-mscm: add support for MSCM interrupt router Stefan Agner
2015-01-15 8:04 ` [PATCH RESEND v3 1/3] " Stefan Agner
[not found] ` <1421309046-22452-1-git-send-email-stefan-XLVq0VzYD2Y@public.gmane.org>
2015-01-15 8:04 ` [PATCH RESEND v3 2/3] irqchip: vf610-mscm: dt-bindings: add MSCM bindings Stefan Agner
[not found] ` <1421309046-22452-3-git-send-email-stefan-XLVq0VzYD2Y@public.gmane.org>
2015-01-26 13:36 ` Mark Rutland
2015-01-26 14:18 ` Stefan Agner
2015-01-28 10:31 ` Stefan Agner
2015-01-15 8:04 ` [PATCH RESEND v3 3/3] ARM: dts: vf610: add Miscellaneous System Control Module (MSCM) Stefan Agner
2015-01-26 10:16 ` Thomas Gleixner [this message]
2015-01-26 11:55 ` [PATCH RESEND v3 0/3] irqchip: vf610-mscm: add support for MSCM interrupt router Stefan Agner
[not found] ` <36990c90fa3d2ee0849227f31cbafb54-XLVq0VzYD2Y@public.gmane.org>
2015-01-26 12:51 ` Marc Zyngier
2015-01-26 13:40 ` Mark Rutland
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=alpine.DEB.2.11.1501261115300.5526@nanos \
--to=tglx@linutronix.de \
--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=stefan@agner.ch \
--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