From: Daniel Palmer <daniel@0x0f.com>
To: soc@kernel.org
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
mark-pk.tsai@mediatek.com, arnd@arndb.de, maz@kernel.org,
Daniel Palmer <daniel@0x0f.com>
Subject: [PATCH v2 3/5] ARM: mstar: Add interrupt to pm_uart
Date: Fri, 2 Oct 2020 22:34:16 +0900 [thread overview]
Message-ID: <20201002133418.2250277-4-daniel@0x0f.com> (raw)
In-Reply-To: <20201002133418.2250277-1-daniel@0x0f.com>
Since we now have support for the interrupt controller pm_uart's
interrupt is routed through it make sense to wire up it's interrupt
in the device tree.
The interrupt is the same for all known chips so it goes in the
base dtsi.
Signed-off-by: Daniel Palmer <daniel@0x0f.com>
---
arch/arm/boot/dts/mstar-v7.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/mstar-v7.dtsi b/arch/arm/boot/dts/mstar-v7.dtsi
index aec841b52ca4..f07880561e11 100644
--- a/arch/arm/boot/dts/mstar-v7.dtsi
+++ b/arch/arm/boot/dts/mstar-v7.dtsi
@@ -113,6 +113,7 @@ pm_uart: uart@221000 {
compatible = "ns16550a";
reg = <0x221000 0x100>;
reg-shift = <3>;
+ interrupts-extended = <&intc_irq GIC_SPI 34 IRQ_TYPE_LEVEL_HIGH>;
clock-frequency = <172000000>;
status = "disabled";
};
--
2.27.0
next prev parent reply other threads:[~2020-10-02 13:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 13:34 [PATCH v2 0/5] ARM: mstar: wire up interrupt controllers Daniel Palmer
2020-10-02 13:34 ` [PATCH v2 1/5] ARM: mstar: Select MStar intc Daniel Palmer
2020-10-02 13:34 ` [PATCH v2 2/5] ARM: mstar: Add interrupt controller to base dtsi Daniel Palmer
2020-10-02 13:34 ` Daniel Palmer [this message]
2020-10-02 13:34 ` [PATCH v2 4/5] ARM: mstar: Add mstar prefix to all of the dtsi/dts files Daniel Palmer
2020-10-02 13:34 ` [PATCH v2 5/5] ARM: mstar: Fix up the fallout from moving the dts/dtsi files Daniel Palmer
2020-10-03 19:48 ` [PATCH v2 0/5] ARM: mstar: wire up interrupt controllers Olof Johansson
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=20201002133418.2250277-4-daniel@0x0f.com \
--to=daniel@0x0f.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark-pk.tsai@mediatek.com \
--cc=maz@kernel.org \
--cc=soc@kernel.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).