From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: victor.duicu@microchip.com
Cc: matteomartelli3@gmail.com, jic23@kernel.org, lars@metafoo.de,
marius.cristea@microchip.com, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7] iio: adc: pac1921: Add ACPI support to Microchip pac1921
Date: Sat, 2 Nov 2024 22:01:58 +0200 [thread overview]
Message-ID: <ZyaFNsuWOOK1HHg0@surfacebook.localdomain> (raw)
In-Reply-To: <20241031065205.50154-1-victor.duicu@microchip.com>
Thu, Oct 31, 2024 at 08:52:05AM +0200, victor.duicu@microchip.com kirjoitti:
> From: Victor Duicu <victor.duicu@microchip.com>
>
> This patch implements ACPI support to Microchip pac1921.
> The driver can read shunt resistor value and label from ACPI table.
More comments below.
...
> +#define PAC1921_ACPI_GET_UOHMS_VALS 0
uOHM ?
#define PAC1921_ACPI_GET_uOHM_VALS 0
...
> +/* The maximum accepted value of shunt_resistor in UOHMS <= INT_MAX */
> +#define PAC1921_MAX_SHUNT_VALUE_OHMS 2147
Instead of the comment do it like this:
#define PAC1921_MAX_SHUNT_VALUE_OHM (INT_MAX / MICRO)
Need to include limits.h and units.h.
...
> +static inline bool pac1921_shunt_is_invalid(u32 shunt_val)
is_invalid is confusing name, make it rather is_valid
> +{
> + return shunt_val == 0 || shunt_val > INT_MAX;
> +}
...
> + /* This check is to ensure val * MICRO won't overflow */
> + if (val < 0 || val > PAC1921_MAX_SHUNT_VALUE_OHMS)
> + return -EINVAL;
> +
> rshunt_uohm = val * MICRO + val_fract;
> - if (rshunt_uohm == 0 || rshunt_uohm > INT_MAX)
> + if (pac1921_shunt_is_invalid(rshunt_uohm))
> return -EINVAL;
With the above check how this can't be a dead code?
...
> + rez = acpi_evaluate_dsm(handle, &guid, 1, PAC1921_ACPI_GET_UOHMS_VALS, NULL);
> + if (!rez)
Use status instead of rez for the variable name. This is kinda standard to keep
the return of ACPI APIs.
> + return dev_err_probe(dev, -EINVAL,
> + "Could not read shunt from ACPI table\n");
...
> + label = devm_kstrdup(dev, rez->package.elements->string.pointer, GFP_KERNEL);
> + if (!label)
> + return dev_err_probe(dev, -EINVAL, "Label is NULL\n");
We do not print an error for -ENOMEM, which should be here as the error code
(Jonathan already pointed out on this).
So, just
return -ENOMEM;
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2024-11-02 20:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 6:52 [PATCH v7] iio: adc: pac1921: Add ACPI support to Microchip pac1921 victor.duicu
2024-11-02 15:45 ` Jonathan Cameron
2024-11-03 11:01 ` Jonathan Cameron
2024-11-02 19:48 ` Andy Shevchenko
2024-11-03 11:10 ` Jonathan Cameron
2024-11-05 8:31 ` Victor.Duicu
2024-11-02 20:01 ` Andy Shevchenko [this message]
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=ZyaFNsuWOOK1HHg0@surfacebook.localdomain \
--to=andy.shevchenko@gmail.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marius.cristea@microchip.com \
--cc=matteomartelli3@gmail.com \
--cc=victor.duicu@microchip.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