From: Matti Vaittinen <mazziesaccount@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
Cc: Mark Brown <broonie@kernel.org>, Lee Jones <lee@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 07/10] irqdomain: Allow giving name suffix for domain
Date: Mon, 3 Jun 2024 16:40:07 +0300 [thread overview]
Message-ID: <8085c2b9-f824-4404-9adf-fb8be09e5a86@gmail.com> (raw)
In-Reply-To: <77c64d75-43fa-47bf-bb3a-e0e49d51189d@gmail.com>
On 6/3/24 15:19, Matti Vaittinen wrote:
> Here, when talking about 'parent IRQ', I was referring to ERRB or INTB
> as 'parent IRQ'. My thinking was that, the regmap IRQ instance uses INTB
> or ERRB as it's parent IRQ, which it splits (demuxes) to separate "child
> IRQs" for the rest of the PMIC drivers to use. I'd be grateful if better
> terms were suggested so that readers can stay on same page with me.
>
> After talking with Mark:
Sorry, I forgot the link:
https://lore.kernel.org/all/Zjzt8mOW6dO_7XNV@finisterre.sirena.org.uk/
>
> we both thought it'd be cleaner to have separate regmap IRQ instances
> for the ERRB and INTB lines. This makes sense (to me) because a lot of
> (almost all of?) the regmap IRQ internal data describe the IRQ line
> related things like registers related to the IRQ line, IRQ line polarity
> etc. Hence, making single regmap-IRQ instance to support more than one
> <please, add what is the correct term for INTB / ERRB like line> would
> require duplicating a plenty of the regmap data. This would make
> registering an regmap-IRQ entity much more complex and additionally it'd
> also complicate the internals of the regmap-IRQ. It'd be a bit like
> trying to fill and drink a six-pack of lemonade at once, instead of
> going a bottle by bottle :)
Yours,
-- Matti
--
Matti Vaittinen
Linux kernel developer at ROHM Semiconductors
Oulu Finland
~~ When things go utterly wrong vim users can always type :help! ~~
next prev parent reply other threads:[~2024-06-03 13:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-24 8:15 [PATCH v2 00/10] Support ROHM BD96801 Scalable PMIC Matti Vaittinen
2024-05-24 8:16 ` [PATCH v2 01/10] dt-bindings: ROHM BD96801 PMIC regulators Matti Vaittinen
2024-05-25 18:39 ` Krzysztof Kozlowski
2024-05-24 8:17 ` [PATCH v2 02/10] dt-bindings: mfd: bd96801 PMIC core Matti Vaittinen
2024-05-25 18:58 ` Krzysztof Kozlowski
2024-05-24 8:17 ` [PATCH v2 03/10] mfd: support ROHM BD96801 " Matti Vaittinen
2024-05-24 8:17 ` [PATCH v2 04/10] regulator: bd96801: ROHM BD96801 PMIC regulators Matti Vaittinen
2024-05-30 12:55 ` Mark Brown
2024-05-24 8:18 ` [PATCH v2 05/10] watchdog: ROHM BD96801 PMIC WDG driver Matti Vaittinen
2024-05-24 8:18 ` [PATCH v2 06/10] MAINTAINERS: Add ROHM BD96801 'scalable PMIC' entries Matti Vaittinen
2024-05-24 8:18 ` [PATCH v2 07/10] irqdomain: Allow giving name suffix for domain Matti Vaittinen
2024-06-03 10:20 ` Thomas Gleixner
2024-06-03 12:19 ` Matti Vaittinen
2024-06-03 13:40 ` Matti Vaittinen [this message]
2024-06-03 16:38 ` Thomas Gleixner
2024-06-03 17:38 ` Matti Vaittinen
2024-06-03 21:03 ` Thomas Gleixner
2024-05-24 8:19 ` [PATCH v2 08/10] regmap: Allow setting IRQ domain name suffix Matti Vaittinen
2024-05-24 8:19 ` [PATCH v2 09/10] mfd: bd96801: Add ERRB IRQ Matti Vaittinen
2024-05-24 8:19 ` [PATCH v2 10/10] regulator: " Matti Vaittinen
2024-05-30 12:56 ` Mark Brown
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=8085c2b9-f824-4404-9adf-fb8be09e5a86@gmail.com \
--to=mazziesaccount@gmail.com \
--cc=broonie@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.vaittinen@fi.rohmeurope.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®