From: "Mårten Lindahl" <marten.lindahl@axis.com>
To: Guenter Roeck <linux@roeck-us.net>, Jean Delvare <jdelvare@suse.com>
Cc: linux-hwmon@vger.kernel.org, kernel@axis.com,
"Mårten Lindahl" <marten.lindahl@axis.com>
Subject: [PATCH v6 0/4] hwmon: (pmbus/ltc2978) Add regulator ops
Date: Tue, 3 May 2022 12:46:27 +0200 [thread overview]
Message-ID: <20220503104631.3515715-1-marten.lindahl@axis.com> (raw)
Hi!
The LTC2978 driver supports a wide range of power regulator chips, but it
has limited functionality for using it in a dynamic regulator framework.
Since standard functions for setting and getting voltage are missing as
pmbus core operations this patchset adds it.
These patches have been tested on an ARTPEC-8 developer board with a group
of LTC2977 power regulators.
Kind regards
Mårten Lindahl
Changes in v2:
- Add pmbus core _pmbus_write_byte_data to check for driver specific callback
- Change pmbus_update_byte_data to use _pmbus_read/write_byte_data
- Change pmbus_regulator_is_enabled to use _pmbus_read_byte_data
- Export pmbus core functions enable/disable/is_enabled
Changes in v3:
- Split patch "hwmon: (pmbus/ltc2978) Use driver specific ops if they exist"
into two patches: (1) pmbus core, (2) ltc2978.
- Move ltc2978_regulator_get/set_voltage functions to pmbus core.
Changes in v4:
- Split (and rename) patch "hwmon: (pmbus) Use driver specific ops if they exist"
into two patches where the first handle _pmbus_write_byte_data, and the
second handle _pmbus_read_byte_data.
- Use voltage conversion functions in pmbus_regulator_get/set_voltage.
Changes in v5:
- Remove PMBUS_VOUT_COMMAND voltage attribute added in v4 and use local
sensor object for conversion.
- Try to read MFR_VOUT_MIN and MFR_VOUT_MAX first, or else VOUT_MARGIN_LOW and
VOUT_MARGIN_HIGH, to get voltage window.
Changes in v6:
- Don't use camelcase.
- Keep convertion of uV to mV as integer.
- Convert limits to voltages before testing requested value.
Mårten Lindahl (4):
hwmon: (pmbus) Introduce and use write_byte_data callback
hwmon: (pmbus) Use _pmbus_read_byte_data with callback
hwmon: (pmbus/ltc2978) Add chip specific write_byte_data
hwmon: (pmbus) Add get_voltage/set_voltage ops
drivers/hwmon/pmbus/ltc2978.c | 12 +++
drivers/hwmon/pmbus/pmbus.h | 2 +
drivers/hwmon/pmbus/pmbus_core.c | 136 +++++++++++++++++++++++++------
3 files changed, 124 insertions(+), 26 deletions(-)
--
2.30.2
next reply other threads:[~2022-05-03 10:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 10:46 Mårten Lindahl [this message]
2022-05-03 10:46 ` [PATCH v6 1/4] hwmon: (pmbus) Introduce and use write_byte_data callback Mårten Lindahl
2022-05-03 10:46 ` [PATCH v6 2/4] hwmon: (pmbus) Use _pmbus_read_byte_data with callback Mårten Lindahl
2022-05-03 10:46 ` [PATCH v6 3/4] hwmon: (pmbus/ltc2978) Add chip specific write_byte_data Mårten Lindahl
2022-05-03 10:46 ` [PATCH v6 4/4] hwmon: (pmbus) Add get_voltage/set_voltage ops Mårten Lindahl
2022-05-03 13:40 ` Guenter Roeck
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=20220503104631.3515715-1-marten.lindahl@axis.com \
--to=marten.lindahl@axis.com \
--cc=jdelvare@suse.com \
--cc=kernel@axis.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux@roeck-us.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.