From: Guenter Roeck <linux@roeck-us.net>
To: Naresh Solanki <naresh.solanki@9elements.com>
Cc: devicetree@vger.kernel.org, Jean Delvare <jdelvare@suse.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
linux-kernel@vger.kernel.org, linux-hwmon@vger.kernel.org,
Patrick Rudolph <patrick.rudolph@9elements.com>
Subject: Re: [PATCH v5 1/5] hwmon: (pmbus/core): Add rdev in pmbus_data struct
Date: Thu, 1 Dec 2022 12:04:19 -0800 [thread overview]
Message-ID: <20221201200419.GA2110128@roeck-us.net> (raw)
In-Reply-To: <20221201193025.1584365-1-Naresh.Solanki@9elements.com>
On Thu, Dec 01, 2022 at 08:30:20PM +0100, Naresh Solanki wrote:
> Add regulator device in pmbus_data & initialize the same during PMBus
> regulator register.
>
This needs an explanation why this change is needed.
Guenter
> Signed-off-by: Naresh Solanki <Naresh.Solanki@9elements.com>
>
> ---
> Change in V5:
> - Fix error check for rdev
> ---
> drivers/hwmon/pmbus/pmbus_core.c | 13 +++++++++----
> 1 file changed, 9 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/hwmon/pmbus/pmbus_core.c b/drivers/hwmon/pmbus/pmbus_core.c
> index 95e95783972a..a95f998ca247 100644
> --- a/drivers/hwmon/pmbus/pmbus_core.c
> +++ b/drivers/hwmon/pmbus/pmbus_core.c
> @@ -81,6 +81,7 @@ struct pmbus_label {
> struct pmbus_data {
> struct device *dev;
> struct device *hwmon_dev;
> + struct regulator_dev **rdevs;
>
> u32 flags; /* from platform data */
>
> @@ -3050,9 +3051,13 @@ static int pmbus_regulator_register(struct pmbus_data *data)
> struct device *dev = data->dev;
> const struct pmbus_driver_info *info = data->info;
> const struct pmbus_platform_data *pdata = dev_get_platdata(dev);
> - struct regulator_dev *rdev;
> int i;
>
> + data->rdevs = devm_kzalloc(dev, sizeof(struct regulator_dev *) * info->num_regulators,
> + GFP_KERNEL);
> + if (!data->rdevs)
> + return -ENOMEM;
> +
> for (i = 0; i < info->num_regulators; i++) {
> struct regulator_config config = { };
>
> @@ -3062,10 +3067,10 @@ static int pmbus_regulator_register(struct pmbus_data *data)
> if (pdata && pdata->reg_init_data)
> config.init_data = &pdata->reg_init_data[i];
>
> - rdev = devm_regulator_register(dev, &info->reg_desc[i],
> + data->rdevs[i] = devm_regulator_register(dev, &info->reg_desc[i],
> &config);
> - if (IS_ERR(rdev))
> - return dev_err_probe(dev, PTR_ERR(rdev),
> + if (IS_ERR(data->rdevs[i]))
> + return dev_err_probe(dev, PTR_ERR(data->rdevs[i]),
> "Failed to register %s regulator\n",
> info->reg_desc[i].name);
> }
>
> base-commit: 9494c53e1389b120ba461899207ac8a3aab2632c
> --
> 2.37.3
>
prev parent reply other threads:[~2022-12-01 20:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 19:30 [PATCH v5 1/5] hwmon: (pmbus/core): Add rdev in pmbus_data struct Naresh Solanki
2022-12-01 19:30 ` [PATCH v5 2/5] hwmon: (pmbus/core): Add interrupt support Naresh Solanki
2022-12-01 20:13 ` Guenter Roeck
2022-12-01 19:30 ` [PATCH v5 3/5] hwmon: (pmbus/core): Notify hwmon events Naresh Solanki
2022-12-01 20:15 ` Guenter Roeck
2022-12-05 7:07 ` Naresh Solanki
2022-12-01 19:30 ` [PATCH v5 4/5] hwmon: (pmbus/core): Add regulator event support Naresh Solanki
2022-12-01 19:30 ` [PATCH v5 5/5] hwmon: (pmbus/core): Notify regulator events Naresh Solanki
2022-12-01 20:04 ` Guenter Roeck [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=20221201200419.GA2110128@roeck-us.net \
--to=linux@roeck-us.net \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=lgirdwood@gmail.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=naresh.solanki@9elements.com \
--cc=patrick.rudolph@9elements.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).