From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Eddie Huang <eddie.huang@mediatek.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Jason Cooper <jason@lakedaemon.net>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, srv_heupstream@mediatek.com,
Pawel Moll <pawel.moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Catalin Marinas <catalin.marinas@arm.com>,
Mark Brown <broonie@linaro.org>,
Will Deacon <will.deacon@arm.com>,
linux-kernel@vger.kernel.org,
Robert Richter <rrichter@cavium.com>,
Sascha Hauer <kernel@pengutronix.de>,
Kumar Gala <galak@codeaurora.org>,
Olof Johansson <olof@lixom.net>,
"Joe.C" <yingjoe.chen@mediatek.com>,
Thomas Gleixner <tglx@linutronix.de>,
yh.chen@mediatek.com
Subject: Re: [PATCH 2/4] irqchip: mediatek: Add support for mt8173
Date: Wed, 10 Dec 2014 12:00:38 +0100 [thread overview]
Message-ID: <2545975.QDuBFbG7BN@wuerfel> (raw)
In-Reply-To: <1418208602-35584-3-git-send-email-eddie.huang@mediatek.com>
On Wednesday 10 December 2014 18:50:00 Eddie Huang wrote:
> From: Yingjoe Chen <yingjoe.chen@mediatek.com>
>
> MT8173 intpol have 32 more irq pins, add support to it.
>
> Signed-off-by: Yingjoe Chen <yingjoe.chen@mediatek.com>
> Signed-off-by: Eddie Huang <eddie.huang@mediatek.com>
>
How about adding a property for the number of irq pins and leave the
old compatible string in place? I don't think it would be good if
we have to update this driver for each new SoC that uses this
irqchip just to change one number.
Arnd
next parent reply other threads:[~2014-12-10 11:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1418208602-35584-1-git-send-email-eddie.huang@mediatek.com>
[not found] ` <1418208602-35584-3-git-send-email-eddie.huang@mediatek.com>
2014-12-10 11:00 ` Arnd Bergmann [this message]
2014-12-10 14:37 ` [PATCH 2/4] irqchip: mediatek: Add support for mt8173 Yingjoe Chen
2014-12-10 14:41 ` Arnd Bergmann
[not found] ` <1418208602-35584-4-git-send-email-eddie.huang@mediatek.com>
2014-12-10 14:27 ` [PATCH 3/4] arm64: dts: Add mediatek MT8173 SoC and evaluation board dts and Makefile Yingjoe Chen
2014-12-10 14:50 ` Matthias Brugger
2014-12-11 12:47 ` Eddie Huang
2014-12-11 13:02 ` Matthias Brugger
2014-12-12 7:45 ` Eddie Huang
2014-12-11 18:02 ` Mark Rutland
2014-12-12 6:52 ` Sascha Hauer
2014-12-15 11:28 ` Mark Rutland
[not found] ` <1418371705.423.31.camel@mtksdaap41>
2014-12-12 16:42 ` Jason Cooper
2014-12-15 13:32 ` Mark Rutland
2014-12-15 12:59 ` Mark Rutland
[not found] ` <1418719615.8392.17.camel@mtksdaap41>
2014-12-16 10:17 ` 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=2545975.QDuBFbG7BN@wuerfel \
--to=arnd@arndb.de \
--cc=broonie@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=eddie.huang@mediatek.com \
--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=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=olof@lixom.net \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=rrichter@cavium.com \
--cc=srv_heupstream@mediatek.com \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.com \
--cc=yh.chen@mediatek.com \
--cc=yingjoe.chen@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