From: Marcello Sylvester Bauer <sylv@sylv.io>
To: linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Patrick Rudolph <patrick.rudolph@9elements.com>,
Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>
Subject: [PATCH v2 0/4] Add max6639 regulator and devicetree support
Date: Mon, 17 Jan 2022 11:40:22 +0100 [thread overview]
Message-ID: <cover.1642413668.git.sylv@sylv.io> (raw)
these patches add devicetree support for the Maxim MAX6639.
In addition, it includes optional regulator support for the fan-supply and
updates the URL to the datasheet.
Changes in v2:
- dt: Rename polarity to pwm-polarity
- Remove unused platform_data header.
- Remove regulator enable/disable calls in pwm_store due to imbalance of
calls.
- Move to strict per channel dt configuration without defaults.
Marcello Sylvester Bauer (4):
hwmon: (max6639) Update Datasheet URL
hwmon: (max6639) Add regulator support
dt-bindings: hwmon: Add binding for max6639
hwmon: (max6639) Change from pdata to dt configuration
.../bindings/hwmon/maxim,max6639.yaml | 112 +++++++++
Documentation/hwmon/max6639.rst | 2 +-
drivers/hwmon/max6639.c | 235 ++++++++++++++----
include/linux/platform_data/max6639.h | 15 --
4 files changed, 297 insertions(+), 67 deletions(-)
create mode 100644 Documentation/devicetree/bindings/hwmon/maxim,max6639.yaml
delete mode 100644 include/linux/platform_data/max6639.h
--
2.33.1
next reply other threads:[~2022-01-17 10:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 10:40 Marcello Sylvester Bauer [this message]
2022-01-17 10:40 ` [PATCH v2 1/4] hwmon: (max6639) Update Datasheet URL Marcello Sylvester Bauer
2022-01-17 10:40 ` [PATCH v2 2/4] hwmon: (max6639) Add regulator support Marcello Sylvester Bauer
2022-01-18 16:11 ` Guenter Roeck
2022-01-19 9:42 ` sylv
2022-01-17 10:40 ` [PATCH v2 3/4] dt-bindings: hwmon: Add binding for max6639 Marcello Sylvester Bauer
2022-01-17 10:40 ` [PATCH v2 4/4] hwmon: (max6639) Change from pdata to dt configuration Marcello Sylvester Bauer
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.1642413668.git.sylv@sylv.io \
--to=sylv@sylv.io \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--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;
as well as URLs for NNTP newsgroup(s).