public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matti Vaittinen <mazziesaccount@gmail.com>
To: Matti Vaittinen <mazziesaccount@gmail.com>,
	Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
Cc: Matti Vaittinen <mazziesaccount@gmail.com>,
	Lee Jones <lee@kernel.org>, Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] ROHM BD96801 Support ERRB IRQ
Date: Mon, 26 Aug 2024 11:14:21 +0300	[thread overview]
Message-ID: <cover.1724655894.git.mazziesaccount@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1992 bytes --]

Add ERRB IRQ support to ROHM BD96801 PMIC driver.

The BD96801 has two IRQ pins, ERRB and INTB. ERRB is used to notify
'fatal' events so handling it has not been mandatory. However, there
are use-cases where handling the ERRB interrupts may be beneficial.

---

Supporting more than one IRQ pin in one device, using the regmap-IRQ,
caused an IRQ domain naming collision in the debugFS when device-tree
was used.

In order to avoid the collision, support for adding a name suffix to
IRQ domain was merged in regmap tree at
commit c69bb91c47e8 ("regmap IRQ support for devices with multiple IRQs")
This is required for the MFD driver to compile. Hence this series is
based on the regmap/for-6.12.

Furthermore, there has been a few (trivial) fixes to the BD96801 driver
in the regulator tree, and thus merge conflicts are possible. I can
re-spin the regulator driver based on the regulator tree when there is
a branch with the required IRQ domain and regmap commits as well as the
MFD driver. The MFD driver with ERRB support is needed so that the
regulator probe won't break for the users with the "errb" in
device-tree.

The ERRB patches were originally part of this series:
https://lore.kernel.org/all/cover.1717486682.git.mazziesaccount@gmail.com/

Revision history in the patches refers to the old versions in that
series.

Matti Vaittinen (2):
  mfd: bd96801: Add ERRB IRQ
  regulator: bd96801: Add ERRB IRQ

 drivers/mfd/rohm-bd96801.c            | 276 ++++++++++++++++++++++----
 drivers/regulator/bd96801-regulator.c | 130 ++++++++++--
 2 files changed, 356 insertions(+), 50 deletions(-)

-- 
2.45.2


-- 
Matti Vaittinen, Linux device drivers
ROHM Semiconductors, Finland SWDC
Kiviharjunlenkki 1E
90220 OULU
FINLAND

~~~ "I don't think so," said Rene Descartes. Just then he vanished ~~~
Simon says - in Latin please.
~~~ "non cogito me" dixit Rene Descarte, deinde evanescavit ~~~
Thanks to Simon Glass for the translation =] 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2024-08-26  8:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-26  8:14 Matti Vaittinen [this message]
2024-08-26  8:14 ` [PATCH 1/2] mfd: bd96801: Add ERRB IRQ Matti Vaittinen
2024-08-30  7:28   ` Lee Jones
2024-08-30  8:54     ` Matti Vaittinen
2024-09-03 14:37       ` Lee Jones
2024-09-04  5:07         ` Matti Vaittinen
2024-08-26  8:15 ` [PATCH 2/2] regulator: " Matti Vaittinen

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=cover.1724655894.git.mazziesaccount@gmail.com \
    --to=mazziesaccount@gmail.com \
    --cc=broonie@kernel.org \
    --cc=lee@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matti.vaittinen@fi.rohmeurope.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