From: Kun Yi <kunyi@google.com>
To: jdelvare@suse.com, linux@roeck-us.net, robh+dt@kernel.org,
mark.rutland@arm.com, supreeth.venkatesh@amd.com
Cc: Kun Yi <kunyi@google.com>,
openbmc@lists.ozlabs.org, linux-hwmon@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH linux hwmon-next v4 0/3] SB-TSI hwmon driver v4
Date: Wed, 2 Dec 2020 08:55:58 -0800 [thread overview]
Message-ID: <20201202165601.1532213-1-kunyi@google.com> (raw)
v4: addressed comments in v3; converted DT binding to required schema
v3: addressed comment in v2 and improved documentation
v2: rewrote using devm_hwmon_device_register_with_info() API and addressed
comments received in v1
v1: first version
Kun Yi (3):
hwmon: (sbtsi) Add basic support for SB-TSI sensors
hwmon: (sbtsi) Add documentation
dt-bindings: (hwmon/sbtsi_tmep) Add SB-TSI hwmon driver bindings
.../devicetree/bindings/hwmon/amd,sbtsi.yaml | 54 ++++
Documentation/hwmon/index.rst | 1 +
Documentation/hwmon/sbtsi_temp.rst | 40 +++
drivers/hwmon/Kconfig | 10 +
drivers/hwmon/Makefile | 1 +
drivers/hwmon/sbtsi_temp.c | 265 ++++++++++++++++++
6 files changed, 371 insertions(+)
create mode 100644 Documentation/devicetree/bindings/hwmon/amd,sbtsi.yaml
create mode 100644 Documentation/hwmon/sbtsi_temp.rst
create mode 100644 drivers/hwmon/sbtsi_temp.c
--
2.29.2.454.gaff20da3a2-goog
next reply other threads:[~2020-12-02 16:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 16:55 Kun Yi [this message]
2020-12-02 16:55 ` [PATCH linux hwmon-next v4 1/3] hwmon: (sbtsi) Add basic support for SB-TSI sensors Kun Yi
2020-12-09 20:13 ` Supreeth Venkatesh
[not found] ` <20201203013748.GA228752@roeck-us.net>
2020-12-03 18:06 ` Chatradhi, Naveen Krishna
2020-12-11 21:57 ` Kun Yi
2020-12-02 16:56 ` [PATCH linux hwmon-next v4 2/3] hwmon: (sbtsi) Add documentation Kun Yi
2020-12-02 16:56 ` [PATCH linux hwmon-next v4 3/3] dt-bindings: (hwmon/sbtsi_tmep) Add SB-TSI hwmon driver bindings Kun Yi
2020-12-09 20:06 ` Rob Herring
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=20201202165601.1532213-1-kunyi@google.com \
--to=kunyi@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=mark.rutland@arm.com \
--cc=openbmc@lists.ozlabs.org \
--cc=robh+dt@kernel.org \
--cc=supreeth.venkatesh@amd.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).