From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Leo Yang <leo.yang.sy0@gmail.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Guenter Roeck <linux@roeck-us.net>
Subject: [PATCH v1 1/1] hwmon: (ina233) Don't check for specific errors when parsing properties
Date: Thu, 19 Feb 2026 15:15:32 +0100 [thread overview]
Message-ID: <20260219141532.2259642-1-andriy.shevchenko@linux.intel.com> (raw)
Instead of checking for the specific error codes (that can be considered
a layering violation to some extent) check for the property existence first
and then either parse it, or apply a default value.
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
---
drivers/hwmon/pmbus/ina233.c | 28 +++++++++++++++-------------
1 file changed, 15 insertions(+), 13 deletions(-)
diff --git a/drivers/hwmon/pmbus/ina233.c b/drivers/hwmon/pmbus/ina233.c
index dde1e1678394..6ee1bce32755 100644
--- a/drivers/hwmon/pmbus/ina233.c
+++ b/drivers/hwmon/pmbus/ina233.c
@@ -82,6 +82,7 @@ static int ina233_read_word_data(struct i2c_client *client, int page,
static int ina233_probe(struct i2c_client *client)
{
struct device *dev = &client->dev;
+ const char *propname;
int ret, m, R;
u32 rshunt;
u32 max_current;
@@ -111,27 +112,28 @@ static int ina233_probe(struct i2c_client *client)
/* If INA233 skips current/power, shunt-resistor and current-lsb aren't needed. */
/* read rshunt value (uOhm) */
- ret = device_property_read_u32(dev, "shunt-resistor", &rshunt);
- if (ret) {
- if (ret != -EINVAL)
- return dev_err_probe(dev, ret, "Shunt resistor property read fail.\n");
+ propname = "shunt-resistor";
+ if (device_property_present(dev, propname)) {
+ ret = device_property_read_u32(dev, propname, &rshunt);
+ if (ret)
+ return dev_err_probe(dev, ret, "%s property read fail.\n", propname);
+ } else {
rshunt = INA233_RSHUNT_DEFAULT;
}
if (!rshunt)
- return dev_err_probe(dev, -EINVAL,
- "Shunt resistor cannot be zero.\n");
+ return dev_err_probe(dev, -EINVAL, "%s cannot be zero.\n", propname);
/* read Maximum expected current value (uA) */
- ret = device_property_read_u32(dev, "ti,maximum-expected-current-microamp", &max_current);
- if (ret) {
- if (ret != -EINVAL)
- return dev_err_probe(dev, ret,
- "Maximum expected current property read fail.\n");
+ propname = "ti,maximum-expected-current-microamp";
+ if (device_property_present(dev, propname)) {
+ ret = device_property_read_u32(dev, propname, &max_current);
+ if (ret)
+ return dev_err_probe(dev, ret, "%s property read fail.\n", propname);
+ } else {
max_current = INA233_MAX_CURRENT_DEFAULT;
}
if (max_current < 32768)
- return dev_err_probe(dev, -EINVAL,
- "Maximum expected current cannot less then 32768.\n");
+ return dev_err_probe(dev, -EINVAL, "%s cannot be less than 32768.\n", propname);
/* Calculate Current_LSB according to the spec formula */
current_lsb = max_current / 32768;
--
2.50.1
next reply other threads:[~2026-02-19 14:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 14:15 Andy Shevchenko [this message]
2026-04-12 14:26 ` [PATCH v1 1/1] hwmon: (ina233) Don't check for specific errors when parsing properties 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=20260219141532.2259642-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=leo.yang.sy0@gmail.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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