From: Guenter Roeck <linux@roeck-us.net>
To: Saravanan Sekar <saravanan@linumiz.com>,
sravanhome@gmail.com, lgirdwood@gmail.com, broonie@kernel.org,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, jdelvare@suse.com
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-hwmon@vger.kernel.org
Subject: Re: [PATCH 1/3] hwmon: (pmbus/mpq7932) Get page count based on chip info
Date: Sun, 10 Sep 2023 21:24:36 -0700 [thread overview]
Message-ID: <b6054cbd-ca4e-43d1-83a8-ad6bdf89c0cf@roeck-us.net> (raw)
In-Reply-To: <20230911034150.181880-2-saravanan@linumiz.com>
On 9/10/23 20:41, Saravanan Sekar wrote:
> Get page count using compatible match to support the series of chipsets
> which differs in number of regualator/page.
>
> Signed-off-by: Saravanan Sekar <saravanan@linumiz.com>
> ---
> drivers/hwmon/pmbus/mpq7932.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/hwmon/pmbus/mpq7932.c b/drivers/hwmon/pmbus/mpq7932.c
> index 865d42edda1a..af3e5e9590c8 100644
> --- a/drivers/hwmon/pmbus/mpq7932.c
> +++ b/drivers/hwmon/pmbus/mpq7932.c
> @@ -105,7 +105,7 @@ static int mpq7932_probe(struct i2c_client *client)
> return -ENOMEM;
>
> info = &data->info;
> - info->pages = MPQ7932_NUM_PAGES;
> + info->pages = (int)device_get_match_data(&client->dev);
I kind of doubt that this works without generating a compiler warning.
Also, does this work with CONFIG_OF=n ?
Guenter
> info->format[PSC_VOLTAGE_OUT] = direct;
> info->m[PSC_VOLTAGE_OUT] = 160;
> info->b[PSC_VOLTAGE_OUT] = -33;
> @@ -115,7 +115,7 @@ static int mpq7932_probe(struct i2c_client *client)
> }
>
> #if IS_ENABLED(CONFIG_SENSORS_MPQ7932_REGULATOR)
> - info->num_regulators = ARRAY_SIZE(mpq7932_regulators_desc);
> + info->num_regulators = info->pages;
> info->reg_desc = mpq7932_regulators_desc;
> #endif
>
> @@ -129,7 +129,7 @@ static int mpq7932_probe(struct i2c_client *client)
> }
>
> static const struct of_device_id mpq7932_of_match[] = {
> - { .compatible = "mps,mpq7932"},
> + { .compatible = "mps,mpq7932", .data = (void *)MPQ7932_NUM_PAGES },
> {},
> };
> MODULE_DEVICE_TABLE(of, mpq7932_of_match);
next prev parent reply other threads:[~2023-09-11 4:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 3:41 [PATCH 0/3] Add support for mpq2286 PMIC IC Saravanan Sekar
2023-09-11 3:41 ` [PATCH 1/3] hwmon: (pmbus/mpq7932) Get page count based on chip info Saravanan Sekar
2023-09-11 4:24 ` Guenter Roeck [this message]
2023-09-11 5:46 ` kernel test robot
2023-09-11 6:40 ` kernel test robot
2023-09-11 3:41 ` [PATCH 2/3] dt-bindings: regulator: Add mps,mpq2286 power-management IC Saravanan Sekar
2023-09-11 4:10 ` Rob Herring
2023-09-11 4:28 ` Guenter Roeck
2023-09-11 6:26 ` Krzysztof Kozlowski
2023-09-11 7:12 ` Saravanan Sekar
2023-09-11 7:41 ` Krzysztof Kozlowski
2023-09-11 3:41 ` [PATCH 3/3] hwmon: (pmbus/mpq2286) Add a support for mpq2286 Power Management IC Saravanan Sekar
2023-09-11 4:23 ` Guenter Roeck
2023-09-26 15:14 ` Saravanan Sekar
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=b6054cbd-ca4e-43d1-83a8-ad6bdf89c0cf@roeck-us.net \
--to=linux@roeck-us.net \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=saravanan@linumiz.com \
--cc=sravanhome@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
all inboxes | Powered by JetHome®