From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Andre Werner <werneazc@gmail.com>,
jdelvare@suse.com, linux@roeck-us.net,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
robh+dt@kernel.org
Cc: linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Andre Werner <andre.werner@systec-electronic.com>
Subject: Re: [PATCH v2 2/2] hwmon: (hs3001) Add driver for Renesas HS3001
Date: Tue, 18 Jul 2023 09:25:30 +0200 [thread overview]
Message-ID: <fb19946c-b95c-cfd1-1034-7542d38e554e@linaro.org> (raw)
In-Reply-To: <20230718070114.3871-2-andre.werner@systec-electronic.com>
On 18/07/2023 09:01, Andre Werner wrote:
> 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>
>
> Changelog:
> v1: Initial version
> v2: Extensive refactoring following recommendations of reviewers:
> - Delete unused defines and device properties. These are added in
> the initial version because the device supports a programming mode,
> but I was not able to implement it, because the custom board was
> not able to control the power supply of the device and so I cannot
> enter the programming mode of the device.
> - Correct missunderstanding comments for defines.
> - Delete mutexes for data and I2C bus accesses.
> - Replace attributes with recommented chip-info structure. In the
> initial version I followed the sth3x.c implementation that uses
> files and attributes in sysfs. The show functions are replaced by
> is_visible and read callbacks from the HWMON ABI. I also delete pointless
> function argument checks.
> - Correct Yoda programming.
> - Refactor probe function and delete sleep and measurement of humidity
> and temperature in probe function. I kept an initial I2C
> communication to ensure that the device is accessible during probe.
> - Reduce the number of atteributes to humidity and temperature input.
Also wrong placement of SoB and changelog.
> ---
> Documentation/hwmon/hs3001.rst | 37 +++++
> MAINTAINERS | 6 +
> drivers/hwmon/Kconfig | 10 ++
> drivers/hwmon/Makefile | 1 +
> drivers/hwmon/hs3001.c | 261 +++++++++++++++++++++++++++++++++
> 5 files changed, 315 insertions(+)
> create mode 100644 Documentation/hwmon/hs3001.rst
> create mode 100644 drivers/hwmon/hs3001.c
...
> +/* Definitions for Status Bits of A/D Data */
> +#define HS3001_DATA_VALID 0x00 /* Valid Data */
> +#define HS3001_DATA_STALE 0x01 /* Stale Data */
> +
> +#define LIMIT_MAX 0
> +#define LIMIT_MIN 1
> +
> +enum hs3001_chips {
> + hs3001,
Drop, not effectively used.
> +};
...
> +
> +/* device ID table */
> +static const struct i2c_device_id hs3001_ids[] = {
> + { "hs3001", hs3001 },
Drop match data
> + { },
> +};
> +
> +MODULE_DEVICE_TABLE(i2c, hs3001_ids);
> +
> +static const struct of_device_id hs3001_of_match[] = {
> + {.compatible = "renesas,hs3001",
> + .data = (void *)hs3001
Drop
> + },
> + { },
> +};
> +
> +MODULE_DEVICE_TABLE(of, hs3001_of_match);
> +
> +static int hs3001_probe(struct i2c_client *client)
> +{
> + struct hs3001_data *data;
> + struct device *hwmon_dev;
> + struct device *dev = &client->dev;
> + int ret;
> +
> + if (!i2c_check_functionality(client->adapter, I2C_FUNC_I2C))
> + return -EOPNOTSUPP;
> +
> + data = devm_kzalloc(dev, sizeof(*data), GFP_KERNEL);
> + if (!data)
> + return -ENOMEM;
> +
> + data->client = client;
> +
> + if (client->dev.of_node)
> + data->type = (enum hs3001_chips)of_device_get_match_data(&client->dev);
> + else
> + data->type = i2c_match_id(hs3001_ids, client)->driver_data;
This is useless and dead code. You have only one type of device. Don't
over-complicate simple things.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-07-18 7:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 7:01 [PATCH v2 1/2] dt-bindings: hwmon: Add description for new hwmon driver hs3001 Andre Werner
2023-07-18 7:01 ` [PATCH v2 2/2] hwmon: (hs3001) Add driver for Renesas HS3001 Andre Werner
2023-07-18 7:25 ` Krzysztof Kozlowski [this message]
2023-07-18 7:21 ` [PATCH v2 1/2] dt-bindings: hwmon: Add description for new hwmon driver hs3001 Krzysztof Kozlowski
2023-07-18 7:23 ` Krzysztof Kozlowski
-- strict thread matches above, loose matches on Subject: below --
2023-07-16 15:05 Andre Werner
2023-07-16 15:05 ` [PATCH v2 2/2] hwmon: (hs3001) Add driver for Renesas HS3001 Andre Werner
2023-07-16 15:09 ` Guenter Roeck
2023-07-14 6:43 [PATCH v2 1/2] dt-bindings: hwmon: Add description for new hwmon driver hs3001 Andre Werner
2023-07-14 6:43 ` [PATCH v2 2/2] hwmon: (hs3001) Add driver for Renesas HS3001 Andre Werner
2023-07-14 22: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=fb19946c-b95c-cfd1-1034-7542d38e554e@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--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=linux@roeck-us.net \
--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).