From: "Andreas Färber" <afaerber@suse.de>
To: Thomas Gleixner <tglx@linutronix.de>,
Jason Cooper <jason@lakedaemon.net>,
Marc Zyngier <marc.zyngier@arm.com>,
linux-arm-kernel@lists.infradead.org
Cc: 蒋丽琴 <jiang.liqin@geniatech.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
"Andreas Färber" <afaerber@suse.de>, "Roc He" <hepeng@zidoo.tv>
Subject: [RFC 0/3] arm64: Realtek RTD1295 IRQ mux
Date: Thu, 17 Aug 2017 12:11:37 +0200 [thread overview]
Message-ID: <20170817101140.32000-1-afaerber@suse.de> (raw)
Hello,
This series adds two IRQ muxes for the Realtek RTD1295 SoC.
Based on the reset controller series.
There being no public source code for RTD1295, the implementation is based on
register offsets seen in the DT, split up into two separate nodes.
A workaround for hanging timer initialization was taken from QNAP's rtk119x
GPL code dump and is not yet fully understood; that code also contains a quirk
for i2c3 in the iso mux that is not yet verified to be needed on RTD1295,
for lack of i2c driver, assuming a linear intr_status/intr_en mapping for now.
My convention here is to use a compatible string for the model that I've
tested (RTD1295) but a file name of rtd119x to indicate its RTD1195 heritage.
More experimental patches at:
https://github.com/afaerber/linux/commits/rtd1295-next
Have a lot of fun!
Cheers,
Andreas
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Jason Cooper <jason@lakedaemon.net>
Cc: Marc Zyngier <marc.zyngier@arm.com>
Cc: Roc He <hepeng@zidoo.tv>
Cc: 蒋丽琴 <jiang.liqin@geniatech.com>
Cc: devicetree@vger.kernel.org
Andreas Färber (3):
dt-bindings: interrupt-controller: Add Realtek RTD1295
arm64: dts: realtek: Add irq mux to RTD1295
irqchip: Add Realtek RTD1295 mux driver
.../interrupt-controller/realtek,rtd119x-mux.txt | 28 +++
arch/arm64/boot/dts/realtek/rtd1295.dtsi | 22 +++
drivers/irqchip/Makefile | 1 +
drivers/irqchip/irq-rtd119x-mux.c | 201 +++++++++++++++++++++
4 files changed, 252 insertions(+)
create mode 100644 Documentation/devicetree/bindings/interrupt-controller/realtek,rtd119x-mux.txt
create mode 100644 drivers/irqchip/irq-rtd119x-mux.c
--
2.12.3
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2017-08-17 10:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 10:11 Andreas Färber [this message]
[not found] ` <20170817101140.32000-1-afaerber-l3A5Bk7waGM@public.gmane.org>
2017-08-17 10:11 ` [RFC 1/3] dt-bindings: interrupt-controller: Add Realtek RTD1295 Andreas Färber
[not found] ` <20170817101140.32000-2-afaerber-l3A5Bk7waGM@public.gmane.org>
2017-08-22 2:14 ` Rob Herring
2017-08-25 19:41 ` Andreas Färber
2017-08-17 10:11 ` [RFC 2/3] arm64: dts: realtek: Add irq mux to RTD1295 Andreas Färber
[not found] ` <20170817101140.32000-4-afaerber@suse.de>
[not found] ` <da3b236f-08ec-837a-de18-4c22b30ce5ca@arm.com>
2017-08-18 17:21 ` [RFC 3/3] irqchip: Add Realtek RTD1295 mux driver Andreas Färber
[not found] ` <d7b03533-0442-4df9-7829-5e81f3ed6f34-l3A5Bk7waGM@public.gmane.org>
2017-08-18 17:47 ` Marc Zyngier
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=20170817101140.32000-1-afaerber@suse.de \
--to=afaerber@suse.de \
--cc=devicetree@vger.kernel.org \
--cc=hepeng@zidoo.tv \
--cc=jason@lakedaemon.net \
--cc=jiang.liqin@geniatech.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.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).