From: Matti Vaittinen <firstname.lastname@example.org>
To: Matti Vaittinen <email@example.com>,
Matti Vaittinen <firstname.lastname@example.org>
Cc: Mark Brown <email@example.com>,
Kees Cook <firstname.lastname@example.org>,
Andy Shevchenko <email@example.com>,
Zhang Rui <firstname.lastname@example.org>,
Guenter Roeck <email@example.com>,
Daniel Lezcano <firstname.lastname@example.org>,
Amit Kucheria <email@example.com>,
Matteo Croce <firstname.lastname@example.org>,
Andrew Morton <email@example.com>,
Petr Mladek <firstname.lastname@example.org>,
"Rafael J. Wysocki" <email@example.com>,
Mike Rapoport <firstname.lastname@example.org>,
Josef Bacik <email@example.com>,
Kai-Heng Feng <firstname.lastname@example.org>,
Subject: [PATCH v7 0/9] Extend regulator notification support
Date: Wed, 14 Apr 2021 08:51:30 +0300 [thread overview]
Message-ID: <email@example.com> (raw)
Extend regulator notification support
This series extends the regulator notification and error flag support.
Initial discussion on the topic can be found here:
This series is built on top of the BD9576MUF support patch series v9
which is currently in MFD tree at immutable branch ib-mfd-watchdog-5.13
(The series should apply without those patches but there is compile time
dependency to definitions brought in at the last patch of the BD9576
series. This should be Ok though as there is a Kconfig dependency in
BD9576 regulator driver)
In a nutshell - the series adds:
1. WARNING level events/error flags. (Patch 3)
Current regulator 'ERROR' event notifications for over/under
voltage, over current and over temperature are used to indicate
condition where monitored entity is so badly "off" that it actually
indicates a hardware error which can not be recovered. The most
typical hanling for that is believed to be a (graceful)
system-shutdown. Here we add set of 'WARNING' level flags to allow
sending notifications to consumers before things are 'that badly off'
so that consumer drivers can implement recovery-actions.
2. Device-tree properties for specifying limit values. (Patches 1, 5)
Add limits for above mentioned 'ERROR' and 'WARNING' levels (which
send notifications to consumers) and also for a 'PROTECTION' level
(which will be used to immediately shut-down the regulator(s) W/O
informing consumer drivers. Typically implemented by hardware).
Property parsing is implemented in regulator core which then calls
callback operations for limit setting from the IC drivers. A
warning is emitted if protection is requested by device tree but the
underlying IC does not support configuring requested protection.
3. Helpers which can be registered by IC. (Patch 4)
Target is to avoid implementing IRQ handling and IRQ storm protection
in each IC driver. (Many of the ICs implementin these IRQs do not allow
masking or acking the IRQ but keep the IRQ asserted for the whole
duration of problem keeping the processor in IRQ handling loop).
4. Emergency poweroff function (refactored out of the thermal_core to
kernel/reboot.c) which is called if IC fires error IRQs but IC reading
fails and given retry-count is exceeded. (Patches 2, 4)
Please note that the mutex in the emergency shutdown was replaced by a
spinlock to allow calls from any context.
The helper was attempted to be done so it could be used to implement
roughly same logic as is used in qcom-labibb regulator. This means
amongst other things a safety shut-down if IC registers are not readable.
Using these shut-down retry counters are optional. The idea is that the
helper could be also used by simpler ICs which do not provide status
register(s) which can be used to check if error is still active.
ICs which do not have such status register can simply omit the 'renable'
callback (and retry-counts etc) - and helper assumes the situation is Ok
and re-enables IRQ after given time period. If problem persists the
handler is ran again and another notification is sent - but at least the
delay allows processor to avoid IRQ loop.
Patch 7 takes this notification support in use at BD9576MUF.
Patch 8 is related to MFD change which is not really related to the RFC
here. It was added to this series in order to avoid potential conflicts.
Patch 9 adds a maintainers entry.
- rebased on v5.12-rc7
- new patch for refactoring the hw-failure reboot logic out of
thermal_core.c for others to use.
- fix regulator error_flags query
- do not BUG() but attempt to shut-down the system
- use BITS_PER_TYPE()
Add MAINTAINERS entry
Changes to IRQ notifiers
- move devm functions to drivers/regulator/devres.c
- drop irq validity check
- use devm_add_action_or_reset()
- fix styling issues
- fix kerneldocs
- Fix the badly formatted pr_emerg() call.
- rebased on v5.12-rc6
- dropped RFC
- fix external FET DT-binding.
- improve prints for cases when expecting HW failure.
- styling and typos
- Fix dangling pointer access at regulator_irq_helper()
- fix function prototype (compile error)
- Update over current limits to what was given in new data-sheet
- Allow over-current monitoring without external FET. Set limits to
values given in data-sheet (REV00K).
- rebase on v5.12-rc2 + BD9576 series
- Split devm variant of delayed wq to own series
- Provide non devm variant of IRQ notification helpers
- shorten dt-property names as suggested by Rob
- unconditionally call map_event in IRQ handling and require it to be
- change the FET resistance property to micro-ohms
- fix voltage computation in OC limit setting
Matti Vaittinen (9):
dt_bindings: Add protection limit properties
reboot: thermal: Export hardware protection shutdown
regulator: add warning flags
regulator: IRQ based event/error notification helpers
regulator: add property parsing and callbacks to set protection limits
dt-bindings: regulator: bd9576 add FET ON-resistance for OCW
regulator: bd9576: Support error reporting
regulator: bd9576: Fix the driver name in id table
MAINTAINERS: Add reviewer for regulator irq_helpers
.../bindings/regulator/regulator.yaml | 82 ++
.../regulator/rohm,bd9576-regulator.yaml | 6 +
MAINTAINERS | 4 +
drivers/regulator/Makefile | 2 +-
drivers/regulator/bd9576-regulator.c | 1060 +++++++++++++++--
drivers/regulator/core.c | 151 ++-
drivers/regulator/devres.c | 52 +
drivers/regulator/irq_helpers.c | 394 ++++++
drivers/regulator/of_regulator.c | 58 +
drivers/regulator/qcom-labibb-regulator.c | 10 +-
drivers/regulator/qcom_spmi-regulator.c | 6 +-
drivers/regulator/stpmic1_regulator.c | 20 +-
drivers/thermal/thermal_core.c | 63 +-
include/linux/reboot.h | 1 +
include/linux/regulator/consumer.h | 14 +
include/linux/regulator/driver.h | 176 ++-
include/linux/regulator/machine.h | 26 +
kernel/reboot.c | 86 ++
18 files changed, 2006 insertions(+), 205 deletions(-)
create mode 100644 drivers/regulator/irq_helpers.c
Matti Vaittinen, Linux device drivers
ROHM Semiconductors, Finland SWDC
~~~ "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 =]
next reply other threads:[~2021-04-14 5:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 5:51 Matti Vaittinen [this message]
2021-04-14 5:51 ` [PATCH v7 1/9] dt_bindings: Add protection limit properties Matti Vaittinen
2021-04-14 5:52 ` [PATCH v7 2/9] reboot: thermal: Export hardware protection shutdown Matti Vaittinen
2021-04-17 4:57 ` Daniel Lezcano
2021-04-17 8:49 ` Vaittinen, Matti
2021-04-17 5:32 ` Daniel Lezcano
2021-04-17 8:49 ` Matti Vaittinen
2021-04-14 5:52 ` [PATCH v7 3/9] regulator: add warning flags Matti Vaittinen
2021-04-14 5:58 ` [PATCH v7 4/9] regulator: IRQ based event/error notification helpers Matti Vaittinen
2021-04-14 5:58 ` [PATCH v7 5/9] regulator: add property parsing and callbacks to set protection limits Matti Vaittinen
2021-04-14 5:59 ` [PATCH v7 6/9] dt-bindings: regulator: bd9576 add FET ON-resistance for OCW Matti Vaittinen
2021-04-14 5:59 ` [PATCH v7 7/9] regulator: bd9576: Support error reporting Matti Vaittinen
2021-04-14 5:59 ` [PATCH v7 8/9] regulator: bd9576: Fix the driver name in id table Matti Vaittinen
2021-04-14 6:00 ` [PATCH v7 9/9] MAINTAINERS: Add reviewer for regulator irq_helpers Matti Vaittinen
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).