From: Slawomir Stepien <sst@poczta.fm>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
jdelvare@suse.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, przemyslaw.cencner@nokia.com,
krzysztof.adamski@nokia.com, alexander.sverdlin@nokia.com,
Slawomir Stepien <slawomir.stepien@nokia.com>
Subject: Re: [PATCH 5/8] hwmon: (lm90) define maximum number of channels that are supported
Date: Sun, 22 May 2022 16:59:00 +0200 [thread overview]
Message-ID: <YopPtA631mX1UgpP@t480s.localdomain> (raw)
In-Reply-To: <20220521023642.GA2890194@roeck-us.net>
On maj 20, 2022 19:36, Guenter Roeck wrote:
> On Fri, May 20, 2022 at 11:32:41AM +0200, Slawomir Stepien wrote:
> > From: Slawomir Stepien <slawomir.stepien@nokia.com>
> >
> > Use this define in all the places where literal '3' was used in this
> > context.
>
> The literal '3' does not always reflect the number of channels.
You caught me.
But besides this problem with struct hwmon_chip_info the '3' was used in context of
max number of channels.
> >
> > Signed-off-by: Slawomir Stepien <slawomir.stepien@nokia.com>
> > ---
> > drivers/hwmon/lm90.c | 29 ++++++++++++++++-------------
> > 1 file changed, 16 insertions(+), 13 deletions(-)
> >
> > diff --git a/drivers/hwmon/lm90.c b/drivers/hwmon/lm90.c
> > index 00fd5734f217..f642c6fd1641 100644
> > --- a/drivers/hwmon/lm90.c
> > +++ b/drivers/hwmon/lm90.c
> > @@ -93,6 +93,9 @@
> > #include <linux/interrupt.h>
> > #include <linux/regulator/consumer.h>
> >
> > +/* The maximum number of channels currently supported */
> > +#define MAX_CHANNELS 3
>
> #define<space>NAME<tab>value
OK
> > +
> > /*
> > * Addresses to scan
> > * Address is fully defined internally and cannot be changed except for
> > @@ -521,9 +524,9 @@ enum lm90_temp11_reg_index {
> > struct lm90_data {
> > struct i2c_client *client;
> > struct device *hwmon_dev;
> > - u32 channel_config[4];
> > + u32 channel_config[MAX_CHANNELS + 1];
> > struct hwmon_channel_info temp_info;
> > - const struct hwmon_channel_info *info[3];
> > + const struct hwmon_channel_info *info[MAX_CHANNELS];
>
> This is wrong.
Yes, sorry for that. I have not checked struct hwmon_chip_info description.
--
Slawomir Stepien
next prev parent reply other threads:[~2022-05-22 14:59 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 9:32 [PATCH 0/8] Add support for ADT7481 in lm90 Slawomir Stepien
2022-05-20 9:32 ` [PATCH 1/8] dt-bindings: hwmon: " Slawomir Stepien
2022-05-20 10:08 ` Krzysztof Kozlowski
2022-05-20 9:32 ` [PATCH 2/8] dt-bindings: hwmon: Add 'extended-range-enable' property support " Slawomir Stepien
2022-05-20 10:09 ` Krzysztof Kozlowski
2022-05-20 10:57 ` Slawomir Stepien
2022-05-20 9:32 ` [PATCH 3/8] dt-bindings: hwmon: Allow specifying channels for lm90 Slawomir Stepien
2022-05-20 10:13 ` Krzysztof Kozlowski
2022-05-20 12:38 ` Slawomir Stepien
2022-05-20 12:47 ` Krzysztof Kozlowski
2022-05-20 13:23 ` Slawomir Stepien
2022-05-20 13:34 ` Krzysztof Kozlowski
2022-05-20 14:02 ` Guenter Roeck
2022-05-20 13:42 ` Guenter Roeck
2022-05-20 14:09 ` Krzysztof Kozlowski
2022-05-20 14:22 ` Guenter Roeck
2022-05-24 11:53 ` Slawomir Stepien
2022-05-24 12:17 ` Slawomir Stepien
2022-05-24 17:27 ` Slawomir Stepien
2022-05-24 17:59 ` Krzysztof Kozlowski
2022-05-25 7:07 ` Slawomir Stepien
2022-05-20 9:32 ` [PATCH 4/8] hwmon: (lm90) add support for ADT7481 Slawomir Stepien
2022-05-20 9:32 ` [PATCH 5/8] hwmon: (lm90) define maximum number of channels that are supported Slawomir Stepien
2022-05-21 2:36 ` Guenter Roeck
2022-05-22 14:59 ` Slawomir Stepien [this message]
2022-05-20 9:32 ` [PATCH 6/8] hwmon: (lm90) enable the extended temperature range Slawomir Stepien
2022-05-20 9:32 ` [PATCH 7/8] hwmon: (lm90) read the channel's label from device-tree Slawomir Stepien
2022-05-20 10:15 ` Krzysztof Kozlowski
2022-05-20 11:01 ` Slawomir Stepien
2022-05-20 11:41 ` Krzysztof Kozlowski
2022-05-20 9:32 ` [PATCH 8/8] hwmon: (lm90) read the channel's offset " Slawomir Stepien
2022-05-20 13:45 ` [PATCH 0/8] Add support for ADT7481 in lm90 Guenter Roeck
2022-05-20 16:01 ` Guenter Roeck
2022-05-22 14:52 ` Slawomir Stepien
2022-05-22 15:00 ` 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=YopPtA631mX1UgpP@t480s.localdomain \
--to=sst@poczta.fm \
--cc=alexander.sverdlin@nokia.com \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=krzysztof.adamski@nokia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=przemyslaw.cencner@nokia.com \
--cc=robh+dt@kernel.org \
--cc=slawomir.stepien@nokia.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