From: Naresh Solanki <naresh.solanki@9elements.com>
To: Patrick Rudolph <patrick.rudolph@9elements.com>,
linux-kernel@vger.kernel.org
Cc: Naresh Solanki <Naresh.Solanki@9elements.com>
Subject: [PATCH 0/3] regulator: Add max597x support
Date: Sun, 29 May 2022 10:53:36 +0200 [thread overview]
Message-ID: <20220529085340.411018-1-Naresh.Solanki@9elements.com> (raw)
The MAX597x is a smart switch with fault protection and sensor readings.
The MAX597X provides two programmable levels of overcurrent circuit-breaker
protection: a fast-trip threshold for a fast turn-off, and a lower slow-trip
threshold for a delayed turn-off.
The MAX597x monitors voltages and current for fault protection. Allow to read
the measured values using the IIO framework.
MAX5978 has single channel & MAX5970 has dual channel.
Every channel has it's own regulator supply nammed 'vss1-supply' and
'vss2-supply'. The regulator supply is used to determine the output
voltage, as the smart switch provides no output regulation.
The driver requires the 'shunt-resistor-micro-ohms' to be present in
the devicetree to properly calculate current related values.
Marcello Sylvester Bauer (1):
dt-bindings: regulator: Add bindings for MAX5970 and MAX5978
Patrick Rudolph (2):
regulator: max597x: Add support for MAX5970 and MAX5978
regulator: max597x: Add IIO support
.../bindings/regulator/max5970.yaml | 144 +++++
MAINTAINERS | 7 +
drivers/regulator/Kconfig | 18 +
drivers/regulator/Makefile | 2 +
drivers/regulator/max597x.c | 575 ++++++++++++++++++
drivers/regulator/max597x.h | 116 ++++
drivers/regulator/max597x_iio.c | 139 +++++
7 files changed, 1001 insertions(+)
create mode 100644 Documentation/devicetree/bindings/regulator/max5970.yaml
create mode 100644 drivers/regulator/max597x.c
create mode 100644 drivers/regulator/max597x.h
create mode 100644 drivers/regulator/max597x_iio.c
base-commit: 664a393a2663a0f62fc1b18157ccae33dcdbb8c8
--
2.35.3
reply other threads:[~2022-05-29 8:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220529085340.411018-1-Naresh.Solanki@9elements.com \
--to=naresh.solanki@9elements.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patrick.rudolph@9elements.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®