From: Chen Zhong <chen.zhong@mediatek.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Chen Zhong <chen.zhong@mediatek.com>,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
linux-mediatek@lists.infradead.org, linux-input@vger.kernel.org,
Matthias Brugger <matthias.bgg@gmail.com>,
Lee Jones <lee.jones@linaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] mfd: mt6397: Add PMIC keys support to MT6397 driver
Date: Wed, 2 Aug 2017 11:17:20 +0800 [thread overview]
Message-ID: <1501643840-21485-5-git-send-email-chen.zhong@mediatek.com> (raw)
In-Reply-To: <1501643840-21485-1-git-send-email-chen.zhong@mediatek.com>
This patch adds compatible strings and interrupts for pmic keys
which serves as child device of MFD.
Signed-off-by: Chen Zhong <chen.zhong@mediatek.com>
---
drivers/mfd/mt6397-core.c | 28 +++++++++++++++++++++++++++-
1 file changed, 27 insertions(+), 1 deletion(-)
diff --git a/drivers/mfd/mt6397-core.c b/drivers/mfd/mt6397-core.c
index 04a601f..a3225b6 100644
--- a/drivers/mfd/mt6397-core.c
+++ b/drivers/mfd/mt6397-core.c
@@ -43,6 +43,22 @@
},
};
+static const struct resource mt6323_keys_resources[] = {
+ {
+ .start = MT6323_IRQ_STATUS_PWRKEY,
+ .end = MT6323_IRQ_STATUS_FCHRKEY,
+ .flags = IORESOURCE_IRQ,
+ },
+};
+
+static const struct resource mt6397_keys_resources[] = {
+ {
+ .start = MT6397_IRQ_PWRKEY,
+ .end = MT6397_IRQ_HOMEKEY,
+ .flags = IORESOURCE_IRQ,
+ },
+};
+
static const struct mfd_cell mt6323_devs[] = {
{
.name = "mt6323-regulator",
@@ -50,6 +66,11 @@
}, {
.name = "mt6323-led",
.of_compatible = "mediatek,mt6323-led"
+ }, {
+ .name = "mtk-pmic-keys",
+ .num_resources = ARRAY_SIZE(mt6323_keys_resources),
+ .resources = mt6323_keys_resources,
+ .of_compatible = "mediatek,mt6323-keys"
},
};
@@ -71,7 +92,12 @@
}, {
.name = "mt6397-pinctrl",
.of_compatible = "mediatek,mt6397-pinctrl",
- },
+ }, {
+ .name = "mtk-pmic-keys",
+ .num_resources = ARRAY_SIZE(mt6397_keys_resources),
+ .resources = mt6397_keys_resources,
+ .of_compatible = "mediatek,mt6397-keys"
+ }
};
static void mt6397_irq_lock(struct irq_data *data)
--
1.7.9.5
prev parent reply other threads:[~2017-08-02 3:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 3:17 [PATCH 0/4] Add MediaTek PMIC keys support Chen Zhong
2017-08-02 3:17 ` [PATCH 1/4] dt-bindings: input: Add document bindings for mtk-pmic-keys Chen Zhong
2017-08-02 3:17 ` [PATCH 2/4] dt-bindings: mfd: Add bindings for the keys as subnode of PMIC Chen Zhong
2017-08-02 3:17 ` [PATCH 3/4] input: Add MediaTek PMIC keys support Chen Zhong
2017-08-02 5:10 ` Dmitry Torokhov
2017-08-02 13:41 ` Chen Zhong
[not found] ` <1501643840-21485-4-git-send-email-chen.zhong-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2017-08-02 10:33 ` Matthias Brugger
[not found] ` <a6b77a6e-00bb-8aa1-86fe-f158bd96abbc-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-08-02 13:46 ` Chen Zhong
2017-08-02 3:17 ` Chen Zhong [this message]
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=1501643840-21485-5-git-send-email-chen.zhong@mediatek.com \
--to=chen.zhong@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@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).