From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/9] mfd: AXP20x: Add mfd driver for AXP20x PMIC
Date: Fri, 11 Apr 2014 13:25:03 +0200 [thread overview]
Message-ID: <235623053.nj0gFkxyW5@wuerfel> (raw)
In-Reply-To: <1397209093-10077-2-git-send-email-carlo@caione.org>
On Friday 11 April 2014 11:38:05 Carlo Caione wrote:
> +#define AXP20X_IRQ(_irq, _off, _mask) \
> + [AXP20X_IRQ_##_irq] = { .reg_offset = (_off), .mask = BIT(_mask) }
> +
> +static const struct regmap_irq axp20x_regmap_irqs[] = {
> + AXP20X_IRQ(ACIN_OVER_V, 0, 7),
> + AXP20X_IRQ(ACIN_PLUGIN, 0, 6),
> + AXP20X_IRQ(ACIN_REMOVAL, 0, 5),
> + AXP20X_IRQ(VBUS_OVER_V, 0, 4),
> + AXP20X_IRQ(VBUS_PLUGIN, 0, 3),
> + AXP20X_IRQ(VBUS_REMOVAL, 0, 2),
> + AXP20X_IRQ(VBUS_V_LOW, 0, 1),
> + AXP20X_IRQ(BATT_PLUGIN, 1, 7),
> + AXP20X_IRQ(BATT_REMOVAL, 1, 6),
> + AXP20X_IRQ(BATT_ENT_ACT_MODE, 1, 5),
> + AXP20X_IRQ(BATT_EXIT_ACT_MODE, 1, 4),
> + AXP20X_IRQ(CHARG, 1, 3),
> + AXP20X_IRQ(CHARG_DONE, 1, 2),
> + AXP20X_IRQ(BATT_TEMP_HIGH, 1, 1),
Why do you have to enumerate the interrupts here? Can't you just
put all the numbers into the DT nodes of the devices using them?
In general, I would say that the mfd driver should not care about
what is connected to it.
Arnd
next prev parent reply other threads:[~2014-04-11 11:25 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-11 9:38 [PATCH v4 0/9] mfd: AXP20x: Add support for AXP202 and AXP209 Carlo Caione
2014-04-11 9:38 ` [PATCH v4 1/9] mfd: AXP20x: Add mfd driver for AXP20x PMIC Carlo Caione
2014-04-11 11:25 ` Arnd Bergmann [this message]
2014-04-11 12:03 ` [linux-sunxi] " Carlo Caione
2014-04-11 12:09 ` Mark Brown
2014-04-11 13:16 ` Arnd Bergmann
2014-04-16 15:43 ` Lee Jones
2014-04-16 15:44 ` Lee Jones
2014-04-11 9:38 ` [PATCH v4 2/9] dt-bindings: add vendor-prefix for X-Powers Carlo Caione
2014-04-11 9:38 ` [PATCH v4 3/9] mfd: AXP20x: Add bindings documentation Carlo Caione
2014-04-11 9:38 ` [PATCH v4 4/9] input: misc: Add driver for AXP20x Power Enable Key Carlo Caione
2014-04-13 8:17 ` Dmitry Torokhov
2014-04-17 12:07 ` [linux-sunxi] " Carlo Caione
2014-04-11 9:38 ` [PATCH v4 5/9] input: misc: Add ABI docs for AXP20x PEK Carlo Caione
2014-04-11 9:38 ` [PATCH v4 6/9] regulator: AXP20x: Add support for regulators subsystem Carlo Caione
2014-04-11 12:23 ` Mark Brown
2014-04-11 12:29 ` [linux-sunxi] " Carlo Caione
2014-05-15 18:03 ` Boris BREZILLON
2014-05-15 18:18 ` Mark Brown
2014-05-16 7:40 ` [linux-sunxi] " Carlo Caione
2014-04-11 9:38 ` [PATCH v4 7/9] ARM: sun7i/sun4i: dt: Add AXP209 support to various boards Carlo Caione
2014-04-11 12:29 ` Mark Brown
2014-04-11 13:04 ` Carlo Caione
2014-04-11 16:18 ` Mark Brown
2014-04-17 10:06 ` Carlo Caione
2014-04-18 15:15 ` Mark Brown
2014-04-23 20:25 ` Carlo Caione
2014-04-24 13:30 ` Mark Brown
2014-04-24 16:35 ` Charles Keepax
2014-04-24 16:58 ` Charles Keepax
2014-04-24 17:12 ` Mark Brown
2014-04-14 9:52 ` Maxime Ripard
2014-04-14 10:02 ` [linux-sunxi] " Carlo Caione
2014-04-14 10:20 ` Hans de Goede
2014-04-14 11:16 ` Mark Brown
2014-04-11 9:38 ` [PATCH v4 8/9] ARM: sunxi: Add AXP20x support in defconfig Carlo Caione
2014-04-11 9:38 ` [PATCH v4 9/9] ARM: sunxi: Add AXP20x support multi_v7_defconfig Carlo Caione
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=235623053.nj0gFkxyW5@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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