devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: werneazc@gmail.com
Cc: jdelvare@suse.com, krzysztof.kozlowski+dt@linaro.org,
	conor+dt@kernel.org, robh+dt@kernel.org,
	linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Andre Werner <andre.werner@systec-electronic.com>
Subject: Re: [PATCH v6 2/2] hwmon: (hs3001) Add driver for Renesas HS3001
Date: Tue, 25 Jul 2023 22:25:30 -0700	[thread overview]
Message-ID: <a3406e39-8580-4ad7-b7ad-19e24eb33526@roeck-us.net> (raw)
In-Reply-To: <20230725042207.22310-2-andre.werner@systec-electronic.com>

On Tue, Jul 25, 2023 at 06:22:07AM +0200, werneazc@gmail.com wrote:
> From: Andre Werner <andre.werner@systec-electronic.com>
> 
> Add base support for Renesas HS3001 temperature
> and humidity sensors and its compatibles HS3002,
> HS3003 and HS3004.
> 
> The sensor has a fix I2C address 0x44. The resolution
> is fixed to 14bit (ref. Missing feature).
> 
> Missing feature:
> - Accessing non-volatile memory: Custom board has no
>   possibility to control voltage supply of sensor. Thus,
>   we cannot send the necessary control commands within
>   the first 10ms after power-on.
> 
> Signed-off-by: Andre Werner <andre.werner@systec-electronic.com>

Applied.

Thanks,
Guenter

  parent reply	other threads:[~2023-07-26  5:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-24  6:29 [PATCH v5 2/2] hwmon: (hs3001) Add driver for Renesas HS3001 werneazc
2023-07-24 14:15 ` Guenter Roeck
2023-07-25  4:22   ` [PATCH v6 " werneazc
2023-07-25 15:23     ` Guenter Roeck
2023-07-26  5:25     ` Guenter Roeck [this message]
2023-07-26  5:16   ` [PATCH v4 1/2] dt-bindings: hwmon: Add description for new hwmon sensor hs3001 werneazc
2023-07-26  5:24     ` 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=a3406e39-8580-4ad7-b7ad-19e24eb33526@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=andre.werner@systec-electronic.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jdelvare@suse.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=werneazc@gmail.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).