From: Andreas Kemnade <andreas@kemnade.info>
To: knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net,
lee.jones@linaro.org, b.galvani@gmail.com,
linus.walleij@linaro.org, linux-kernel@vger.kernel.org,
linux-iio@vger.kernel.org, phh@phh.me, stefan@agner.ch,
letux-kernel@openphoenux.org, martin.blumenstingl@googlemail.com,
jic23@kernel.org
Cc: Andreas Kemnade <andreas@kemnade.info>
Subject: [PATCH RFC v3 3/4] mfd: rn5t618: add IRQ definitions for RN5T618
Date: Tue, 18 Feb 2020 07:17:24 +0100 [thread overview]
Message-ID: <20200218061725.22420-4-andreas@kemnade.info> (raw)
In-Reply-To: <20200218061725.22420-1-andreas@kemnade.info>
Previously, only the definitions for the RC5T619 were
available.
Signed-off-by: Andreas Kemnade <andreas@kemnade.info>
---
depends on:
https://lore.kernel.org/lkml/20191220122416.31881-1-andreas@kemnade.info/
Untested, IMHO only acceptable with a Tested-By.
Not needed for the RC5T619, feel free to ignore them if the whole series
would be delayed just because of missing Tested-By for this.
drivers/mfd/rn5t618.c | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
diff --git a/drivers/mfd/rn5t618.c b/drivers/mfd/rn5t618.c
index 321836f78120..6828fd40b0a1 100644
--- a/drivers/mfd/rn5t618.c
+++ b/drivers/mfd/rn5t618.c
@@ -58,6 +58,24 @@ static const struct regmap_config rn5t618_regmap_config = {
.cache_type = REGCACHE_RBTREE,
};
+static const struct regmap_irq rn5t618_irqs[] = {
+ REGMAP_IRQ_REG(RN5T618_IRQ_SYS, 0, BIT(0)),
+ REGMAP_IRQ_REG(RN5T618_IRQ_DCDC, 0, BIT(1)),
+ REGMAP_IRQ_REG(RN5T618_IRQ_ADC, 0, BIT(3)),
+ REGMAP_IRQ_REG(RN5T618_IRQ_GPIO, 0, BIT(4)),
+ REGMAP_IRQ_REG(RN5T618_IRQ_CHG, 0, BIT(6)),
+};
+
+static const struct regmap_irq_chip rn5t618_irq_chip = {
+ .name = "rn5t618",
+ .irqs = rn5t618_irqs,
+ .num_irqs = ARRAY_SIZE(rn5t618_irqs),
+ .num_regs = 1,
+ .status_base = RN5T618_INTMON,
+ .mask_base = RN5T618_INTEN,
+ .mask_invert = true,
+};
+
static const struct regmap_irq rc5t619_irqs[] = {
REGMAP_IRQ_REG(RN5T618_IRQ_SYS, 0, BIT(0)),
REGMAP_IRQ_REG(RN5T618_IRQ_DCDC, 0, BIT(1)),
@@ -92,6 +110,9 @@ static int rn5t618_irq_init(struct rn5t618 *rn5t618)
case RC5T619:
irq_chip = &rc5t619_irq_chip;
break;
+ case RN5T618:
+ irq_chip = &rn5t618_irq_chip;
+ break;
default:
irq_chip = NULL;
break;
--
2.20.1
next prev parent reply other threads:[~2020-02-18 6:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 6:17 [PATCH v3 0/4] mfd: rn5t618: add ADC support Andreas Kemnade
2020-02-18 6:17 ` [PATCH v3 1/4] mfd: rn5t618: add ADC subdevice for RC5T619 Andreas Kemnade
2020-02-18 6:17 ` [PATCH v3 2/4] iio: adc: rn5t618: Add ADC driver for RN5T618/RC5T619 Andreas Kemnade
2020-02-21 13:07 ` Jonathan Cameron
2020-02-21 17:27 ` Andreas Kemnade
2020-02-24 18:26 ` Andreas Kemnade
2020-02-18 6:17 ` Andreas Kemnade [this message]
2020-02-18 6:17 ` [PATCH RFC v3 4/4] mfd: rn5t618: add ADC subdevice for RN5T618 Andreas Kemnade
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=20200218061725.22420-4-andreas@kemnade.info \
--to=andreas@kemnade.info \
--cc=b.galvani@gmail.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=lee.jones@linaro.org \
--cc=letux-kernel@openphoenux.org \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=phh@phh.me \
--cc=pmeerw@pmeerw.net \
--cc=stefan@agner.ch \
/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).