From: Guenter Roeck <linux@roeck-us.net>
To: Emil Renner Berthing <kernel@esmil.dk>,
Jean Delvare <jdelvare@suse.com>,
Rob Herring <robh+dt@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Samin Guo <samin.guo@starfivetech.com>
Cc: linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] hwmon: Add StarFive JH7100 temperature sensor
Date: Wed, 28 Jul 2021 09:54:15 -0700 [thread overview]
Message-ID: <bcc9de67-f006-0a81-8c3f-2ae5188dca48@roeck-us.net> (raw)
In-Reply-To: <20210726171802.1052716-1-kernel@esmil.dk>
On 7/26/21 10:18 AM, Emil Renner Berthing wrote:
> This adds a driver for the temperature sensor on the JH7100, a RISC-V
> SoC by StarFive Technology Co. Ltd., and most likely also the upcoming
> JH7110 version.
>
> The SoC is used on the BeagleV Starlight board:
> https://github.com/beagleboard/beaglev-starlight
>
> Support for this SoC is not yet upstreamed, but is actively worked on,
> so it should only be a matter of time before that happens.
>
Hmm, makes me wonder if I should apply the series now or later,
when the chip is actually supported by the kernel. Comments/thoughts ?
Guenter
> v3:
> * Handle timeouts from wait_for_completion_interruptible_timeout
> properly.
>
> v2:
> * Fix checkpatch.pl --strict warnings
> - Add myself to MAINTAINERS
> - Fix multiline comments
> - Use proper case and whitespace for #defines
> - Add comment to sfctemp::lock mutex.
> * Remaining comments by Guenter Roeck
> - Add Documentation/hwmon/sfctemp.rst
> - Use devm_add_action() and devm_hwmon_device_register_with_info()
> instead of a driver .remove function.
> - Don't do test conversion at probe time.
> - #include <linux/io.h>
> - Remove unused #defines
> - Use int return variable in sfctemp_convert().
> * Add Samin's Signed-off-by to patch 2/2
>
> Emil Renner Berthing (2):
> dt-bindings: hwmon: add starfive,jh7100-temp bindings
> hwmon: (sfctemp) Add StarFive JH7100 temperature sensor
>
> .../bindings/hwmon/starfive,jh7100-temp.yaml | 43 +++
> Documentation/hwmon/index.rst | 1 +
> Documentation/hwmon/sfctemp.rst | 32 ++
> MAINTAINERS | 8 +
> drivers/hwmon/Kconfig | 10 +
> drivers/hwmon/Makefile | 1 +
> drivers/hwmon/sfctemp.c | 291 ++++++++++++++++++
> 7 files changed, 386 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/hwmon/starfive,jh7100-temp.yaml
> create mode 100644 Documentation/hwmon/sfctemp.rst
> create mode 100644 drivers/hwmon/sfctemp.c
>
next prev parent reply other threads:[~2021-07-28 16:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 17:18 [PATCH v3 0/2] hwmon: Add StarFive JH7100 temperature sensor Emil Renner Berthing
2021-07-26 17:18 ` [PATCH v3 1/2] dt-bindings: hwmon: add starfive,jh7100-temp bindings Emil Renner Berthing
2021-07-26 17:18 ` [PATCH v3 2/2] hwmon: (sfctemp) Add StarFive JH7100 temperature sensor Emil Renner Berthing
2021-07-28 16:54 ` Guenter Roeck [this message]
2021-07-28 17:05 ` [PATCH v3 0/2] hwmon: " Emil Renner Berthing
2021-08-01 20:19 ` Emil Renner Berthing
2021-08-01 20:29 ` 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=bcc9de67-f006-0a81-8c3f-2ae5188dca48@roeck-us.net \
--to=linux@roeck-us.net \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=kernel@esmil.dk \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=samin.guo@starfivetech.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).