From: Mark Brown <broonie@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Marco Felsch <m.felsch@pengutronix.de>,
Marc Zyngier <marc.zyngier@arm.com>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Rob Herring <robh+dt@kernel.org>,
Support Opensource <support.opensource@diasemi.com>,
Adam Thomson <Adam.Thomson.Opensource@diasemi.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Sascha Hauer <kernel@pengutronix.de>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH v2 2/3] mfd: da9062: add support for the DA9062 GPIOs in the core
Date: Wed, 27 Nov 2019 15:19:29 +0000 [thread overview]
Message-ID: <20191127151929.GC4879@sirena.org.uk> (raw)
In-Reply-To: <CACRpkdYLeSjsXaG6Bg4Y2-8PW41ALn4PN7QUvp3tA7XReWrKGg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 537 bytes --]
On Wed, Nov 27, 2019 at 02:35:33PM +0100, Linus Walleij wrote:
> I can clearly see that regmap's irqchip does not support
> hierarchical interrupt domains, so we should just make a
> mental note somewhere that "oh yeah and then one day
> we should make regmap irqchips play well with hierarchical
> interrupts".
Why, what do we need to do? We're just doing all the default stuff,
it's not something we've opted out of, and the whole point with using
the frameworks should be that we should get software features like this
for free :(
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-11-27 15:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-27 11:56 [PATCH v2 0/3] Add DA9062 GPIO support Marco Felsch
2019-11-27 11:56 ` [PATCH v2 1/3] dt-bindings: mfd: da9062: add gpio bindings Marco Felsch
2019-11-27 11:56 ` [PATCH v2 2/3] mfd: da9062: add support for the DA9062 GPIOs in the core Marco Felsch
2019-11-27 13:35 ` Linus Walleij
2019-11-27 14:03 ` Marco Felsch
2019-11-27 15:19 ` Mark Brown [this message]
2019-11-29 8:49 ` Linus Walleij
2019-11-29 18:08 ` Mark Brown
2019-11-27 11:56 ` [PATCH v2 3/3] pinctrl: da9062: add driver support Marco Felsch
2019-11-27 13:49 ` Linus Walleij
2019-11-27 15:01 ` Marco Felsch
2019-11-28 10:47 ` Bartosz Golaszewski
2019-11-29 9:07 ` Marco Felsch
2019-11-29 13:30 ` Bartosz Golaszewski
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=20191127151929.GC4879@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Adam.Thomson.Opensource@diasemi.com \
--cc=bgolaszewski@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=m.felsch@pengutronix.de \
--cc=marc.zyngier@arm.com \
--cc=robh+dt@kernel.org \
--cc=support.opensource@diasemi.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;
as well as URLs for NNTP newsgroup(s).