From: Olof Johansson <olof@lixom.net>
To: Daniel Palmer <daniel@0x0f.com>
Cc: soc@kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux@armlinux.org.uk, w@1wt.eu
Subject: Re: [RFC PATCH 2/3] ARM: mstar: msc313-intc interrupt controller driver
Date: Fri, 21 Aug 2020 11:46:03 -0700 [thread overview]
Message-ID: <20200821184603.GA3407@lx2k> (raw)
In-Reply-To: <20200730130044.2037509-3-daniel@0x0f.com>
Hi,
On Thu, Jul 30, 2020 at 10:00:43PM +0900, Daniel Palmer wrote:
> Add a driver for the two peripheral interrupt controllers
> in MStar MSC313 and other MStar/Sigmastar Armv7 SoCs.
>
> Supports both the "IRQ" and "FIQ" controllers that
> forward interrupts from the various IP blocks inside the
> SoC to the ARM GIC.
>
> They are basically the same thing except for one difference:
> The FIQ controller needs to clear the interrupt and the IRQ
> controller doesn't.
Sorry for the late response, going through patches we might have missed or that
need replies now...
This needs to go to the irqchip maintainers for review. If you get their
acked/reviewed-by, we can merge it through our tree if that is easier. But they
need to sign off on it. Feel free to cc soc@kernel.org on them though, and we
always merge the dts changes through our tree.
-Olof
next prev parent reply other threads:[~2020-08-21 19:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-30 13:00 [RFC PATCH 0/3] ARM: mstar: msc313 intc driver Daniel Palmer
2020-07-30 13:00 ` [RFC PATCH 1/3] dt: bindings: interrupt-controller: Add binding description for msc313-intc Daniel Palmer
2020-07-31 18:21 ` Rob Herring
2020-07-31 18:23 ` Rob Herring
2020-07-30 13:00 ` [RFC PATCH 2/3] ARM: mstar: msc313-intc interrupt controller driver Daniel Palmer
2020-08-21 18:46 ` Olof Johansson [this message]
2020-07-30 13:00 ` [RFC PATCH 3/3] ARM: mstar: Add interrupt controller to base dtsi Daniel Palmer
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=20200821184603.GA3407@lx2k \
--to=olof@lixom.net \
--cc=daniel@0x0f.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=soc@kernel.org \
--cc=w@1wt.eu \
/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).