From: Chu Lin <linchuyuan@google.com>
To: linchuyuan@google.com, jdelvare@suse.com, linux@roeck-us.net,
robh+dt@kernel.org, linux-hwmon@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v4 0/2] hwmon: pmbus: max20730: adjust the vout base on
Date: Sun, 4 Oct 2020 03:14:43 +0000 [thread overview]
Message-ID: <20201004031445.2321090-1-linchuyuan@google.com> (raw)
The patchset includes:
Patch #1 - Implmentation of adjusting vout base on voltage divider
Patch #2 - device tree binding documentation
ChangeLog v1 -> v2
hwmon: pmbus: max20730:
- Don't do anything to the ret if an error is returned from pmbus_read_word
- avoid overflow when doing multiplication
ChangeLog v2 -> v3
dt-bindings: hwmon: max20730:
- Provide the binding documentation in yaml format
hwmon: pmbus: max20730:
- No change
ChangeLog v3 -> v4
dt-bindings: hwmon: max20730:
- Fix highefficiency to high efficiency in description
- Fix presents to present in vout-voltage-divider
- Add additionalProperties: false
hwmon: pmbus: max20730:
- No change
Chu Lin (2):
dt-bindings: hwmon: max20730: adding device tree doc for max20730
hwmon: pmbus: max20730: adjust the vout reading given voltage divider
.../bindings/hwmon/maxim,max20730.yaml | 65 +++++++++++++++++++
drivers/hwmon/pmbus/max20730.c | 18 +++++
2 files changed, 83 insertions(+)
create mode 100644 Documentation/devicetree/bindings/hwmon/maxim,max20730.yaml
--
2.28.0.806.g8561365e88-goog
next reply other threads:[~2020-10-04 3:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-04 3:14 Chu Lin [this message]
2020-10-04 3:14 ` [PATCH v4 1/2] dt-bindings: hwmon: max20730: adding device tree doc for max20730 Chu Lin
2020-10-06 21:17 ` Rob Herring
2020-10-06 21:55 ` Guenter Roeck
2020-10-04 3:14 ` [PATCH v4 2/2] hwmon: pmbus: max20730: adjust the vout reading given voltage divider Chu Lin
2020-10-04 15:43 ` Guenter Roeck
2020-10-05 3:07 ` Chu Lin
2020-10-05 5:24 ` Guenter Roeck
2020-10-05 15:03 ` Guenter Roeck
2020-10-06 21:55 ` 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=20201004031445.2321090-1-linchuyuan@google.com \
--to=linchuyuan@google.com \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh+dt@kernel.org \
/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.