From: Mark-PK Tsai <mark-pk.tsai@mediatek.com>
To: <daniel@0x0f.com>, Mark-PK Tsai <mark-pk.tsai@mediatek.com>
Cc: <alix.wu@mediatek.com>, <devicetree@vger.kernel.org>,
<jason@lakedaemon.net>, <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-mediatek@lists.infradead.org>, <matthias.bgg@gmail.com>,
<maz@kernel.org>, <robh+dt@kernel.org>, <tglx@linutronix.de>,
<yj.chiang@mediatek.com>
Subject: Re: [PATCH v2 1/2] irqchip: irq-mst: Add MStar interrupt controller support
Date: Mon, 24 Aug 2020 10:36:08 +0800 [thread overview]
Message-ID: <20200824023608.12694-1-mark-pk.tsai@mediatek.com> (raw)
In-Reply-To: <CAFr9PXni=BmDY6_iuJPnYb3d6XB1VrxE6WP3YtSBxT6NciZMMA@mail.gmail.com>
From: Daniel Palmer <daniel@0x0f.com>
>Hi Mark-PK,
>
>On Thu, 20 Aug 2020 at 00:38, Mark-PK Tsai <mark-pk.tsai@mediatek.com> wrote:
>>
>> Add MStar interrupt controller support using hierarchy irq
>> domain.
>>
>> Signed-off-by: Mark-PK Tsai <mark-pk.tsai@mediatek.com>
>
>I've integrated this version into my MStar/SigmaStar tree and tested
>on an MStar MSC313E
>based board (BreadBee) and I'm happy to say it seems to be working:
>
>$ cat /proc/interrupts
> CPU0
>17: 1219 GIC-0 29 Level arch_timer
>18: 0 GIC-0 30 Level arch_timer
>21: 0 GIC-0 42 Level arm-pmu
>24: 0 mst-intc 44 Level 1f002400.rtc
>30: 0 mst-intc 2 Level 1f006000.wdt
>31: 0 mst-intc 0 Level 1f006040.timer
>32: 0 mst-intc 1 Level 1f006080.timer
>33: 0 mst-intc 12 Level 1f0060c0.timer
>34: 0 mst-intc 40 Level 1f200400.bdma
>35: 3977 mst-intc 41 Level 1f200400.bdma
>37: 196 mst-intc 34 Level ttyS0
>40: 0 mst-intc 30 Level soc:usbphy@0
><snip>
>
>So here's my tested by:
>
>Tested-by: Daniel Palmer <daniel@thingy.jp>
>
Thanks for your test.
>I don't think your series contained an update to MAINTAINERS.
>If/when you add this could you add my address above as a reviewer so
>I'm in the loop if anyone makes changes to this going forward?
>
Sure, I will add your address in there. :)
Can I just add a patch in this thread which only contain MAINTAINERS update?
next prev parent reply other threads:[~2020-08-24 2:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 3:42 [PATCH 0/2] " Mark-PK Tsai
2020-08-19 3:42 ` [PATCH 1/2] irqchip: irq-mst: " Mark-PK Tsai
2020-08-19 8:14 ` Marc Zyngier
2020-08-19 13:31 ` Mark-PK Tsai
2020-08-19 13:42 ` Marc Zyngier
2020-08-19 14:55 ` Mark-PK Tsai
2020-08-19 15:24 ` Marc Zyngier
2020-08-19 3:42 ` [PATCH 2/2] dt-bindings: interrupt-controller: Add MStar interrupt controller Mark-PK Tsai
2020-08-25 21:48 ` Rob Herring
2020-08-26 7:50 ` Mark-PK Tsai
2020-08-19 15:37 ` [PATCH v2 1/2] irqchip: irq-mst: Add MStar interrupt controller support Mark-PK Tsai
2020-08-20 12:36 ` Daniel Palmer
2020-08-20 12:47 ` Marc Zyngier
2020-09-02 6:59 ` Mark-PK Tsai
2020-08-22 4:48 ` Daniel Palmer
2020-08-24 2:36 ` Mark-PK Tsai [this message]
2020-08-24 2:48 ` [PATCH] MAINTAINERS: Add maintenance information for MStar Interrupt Controller Mark-PK Tsai
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=20200824023608.12694-1-mark-pk.tsai@mediatek.com \
--to=mark-pk.tsai@mediatek.com \
--cc=alix.wu@mediatek.com \
--cc=daniel@0x0f.com \
--cc=devicetree@vger.kernel.org \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=maz@kernel.org \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
--cc=yj.chiang@mediatek.com \
/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
all inboxes | Powered by JetHome®