From: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
To: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>,
Matti Vaittinen <mazziesaccount@gmail.com>
Cc: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/3] Provide event map helper for regulator drivers
Date: Wed, 24 Nov 2021 09:16:18 +0200 [thread overview]
Message-ID: <cover.1637736436.git.matti.vaittinen@fi.rohmeurope.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1607 bytes --]
This series provides an event map helper for regulator drivers and few
other minor things.
Regulators which provide trivial notification IRQs can use generic IRQ
mapper. Trivial in this context means the IRQ only informs one type of
event, for one regulator.
I did these changes for a new ROHM PMIC - which unfortunately requires
(hopefully only) one more HW revision before it is good to go. So there
is no rush with merging the first two patches - but I decided to send
them as they might lower the barrier of using the notifications with
some non ROHM ICs. Please use your best judgement whether to include
them at this phase or not.
The last patch is a fix for IRQ helper removing an unused struct member
and I think it should be merged no matter what is the fate of the
previous patches.
The series is based on regulator/for-next
---
Matti Vaittinen (3):
regulators: Add regulator_err2notif() helper
regulators: irq_helper: Provide helper for trivial IRQ notifications
regulator: Drop unnecessary struct member
drivers/regulator/irq_helpers.c | 41 +++++++++++++++++++++++++++++++-
include/linux/regulator/driver.h | 37 +++++++++++++++++++++++++++-
2 files changed, 76 insertions(+), 2 deletions(-)
--
2.31.1
--
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 --]
next reply other threads:[~2021-11-24 7:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 7:16 Matti Vaittinen [this message]
2021-11-24 7:16 ` [PATCH v2 1/3] regulators: Add regulator_err2notif() helper Matti Vaittinen
2021-11-24 12:54 ` Mark Brown
2021-11-24 7:17 ` [PATCH v2 2/3] regulators: irq_helper: Provide helper for trivial IRQ notifications Matti Vaittinen
2021-11-24 7:17 ` [PATCH v2 3/3] regulator: Drop unnecessary struct member Matti Vaittinen
2021-11-24 17:36 ` [PATCH v2 0/3] Provide event map helper for regulator drivers 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=cover.1637736436.git.matti.vaittinen@fi.rohmeurope.com \
--to=matti.vaittinen@fi.rohmeurope.com \
--cc=andy.shevchenko@gmail.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mazziesaccount@gmail.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
all inboxes | Powered by JetHome®