From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Cedric Encarnacion <cedricjustine.encarnacion@analog.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-i2c@vger.kernel.org, linux-doc@vger.kernel.org,
linux-hwmon@vger.kernel.org, "Guenter Roeck" <linux@roeck-us.net>,
"Jean Delvare" <jdelvare@suse.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Delphine CC Chiu" <Delphine_CC_Chiu@wiwynn.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Radu Sabau" <radu.sabau@analog.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Alexis Czezar Torreno" <alexisczezar.torreno@analog.com>
Subject: Re: [PATCH 2/2] hwmon: (pmbus/adp1050): add support for adp1051, adp1055 and ltp8800
Date: Wed, 20 Nov 2024 15:52:21 +0200 [thread overview]
Message-ID: <Zz3plZOyMcxn54_h@smile.fi.intel.com> (raw)
In-Reply-To: <20241120035826.3920-3-cedricjustine.encarnacion@analog.com>
On Wed, Nov 20, 2024 at 11:58:26AM +0800, Cedric Encarnacion wrote:
I would start the commit message with the plain English sentence that describes
the list given below. E.g., "Introduce support for the following components:".
> ADP1051: 6 PWM for I/O Voltage, I/O Current, Temperature
> ADP1055: 6 PWM for I/O Voltage, I/O Current, Power, Temperature
> LTP8800-1A/-2/-4A: 150A/135A/200A DC/DC µModule Regulator
>
> The LTP8800 is a family of step-down μModule regulators that provides
> microprocessor core voltage from 54V power distribution architecture.
> LTP8800 features telemetry monitoring of input/output voltage, input
> current, output power, and temperature over PMBus.
...
> - Radu Sabau <radu.sabau@analog.com>
>
> -
> Description
> -----------
Stray change.
...
> -This driver supprts hardware monitoring for Analog Devices ADP1050 Digital
> -Controller for Isolated Power Supply with PMBus interface.
> +This driver supports hardware monitoring for Analog Devices ADP1050, ADP1051, and
> +ADP1055 Digital Controller for Isolated Power Supply with PMBus interface.
>
> -The ADP1050 is an advanced digital controller with a PMBus™
> +The ADP105X is an advanced digital controller with a PMBus™
Can we use small x to make it more visible that it's _not_ the part of the
name, but a glob-like placeholder?
> interface targeting high density, high efficiency dc-to-dc power
> conversion used to monitor system temperatures, voltages and currents.
...
> +#if IS_ENABLED(CONFIG_SENSORS_ADP1050_REGULATOR)
Why? Is the data type undefined without this?
> +static const struct regulator_desc adp1050_reg_desc[] = {
> + PMBUS_REGULATOR_ONE("vout"),
> +};
> +#endif /* CONFIG_SENSORS_ADP1050_REGULATOR */
Note, this can be dropped anyway in order to use PTR_IF() below, if required.
...
> +#if IS_ENABLED(CONFIG_SENSORS_ADP1050_REGULATOR)
> + .num_regulators = 1,
> + .reg_desc = adp1050_reg_desc,
> +#endif
Ditto, are the fields not defined without the symbol?
...
> static int adp1050_probe(struct i2c_client *client)
> {
> - return pmbus_do_probe(client, &adp1050_info);
> + const struct pmbus_driver_info *info;
> +
> + info = device_get_match_data(&client->dev);
Why not i2c_get_match_data()?
> + if (!info)
> + return -ENODEV;
> +
> + return pmbus_do_probe(client, info);
> }
...
> static const struct i2c_device_id adp1050_id[] = {
> - {"adp1050"},
> + { .name = "adp1050", .driver_data = (kernel_ulong_t)&adp1050_info},
Please, split this patch to at least two:
1) Introduce chip_info;
2) add new devices.
> + { .name = "adp1051", .driver_data = (kernel_ulong_t)&adp1051_info},
> + { .name = "adp1055", .driver_data = (kernel_ulong_t)&adp1055_info},
> + { .name = "ltp8800", .driver_data = (kernel_ulong_t)<p8800_info},
> {}
> };
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-11-20 13:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-20 3:58 [PATCH 0/2] Add support for ADP1051/ADP1055 and LTP8800-1A/-2/-4A Cedric Encarnacion
2024-11-20 3:58 ` [PATCH 1/2] dt-bindings: hwmon: (pmbus/adp1050): Add bindings for adp1051, adp1055 and ltp8800 Cedric Encarnacion
2024-11-20 17:11 ` Conor Dooley
2024-11-20 17:35 ` Krzysztof Kozlowski
2024-11-20 18:07 ` Guenter Roeck
2024-11-20 18:39 ` Krzysztof Kozlowski
2024-11-25 2:44 ` Encarnacion, Cedric justine
2024-11-29 9:12 ` Nuno Sá
2024-11-20 18:00 ` Guenter Roeck
2024-11-23 19:56 ` Conor Dooley
2024-11-23 19:58 ` Conor Dooley
2024-11-25 2:44 ` Encarnacion, Cedric justine
2024-11-25 18:48 ` Conor Dooley
2024-11-20 3:58 ` [PATCH 2/2] hwmon: (pmbus/adp1050): add support " Cedric Encarnacion
2024-11-20 5:00 ` Randy Dunlap
2024-11-20 13:45 ` Andy Shevchenko
2024-11-20 13:52 ` Andy Shevchenko [this message]
2024-11-20 14:53 ` Guenter Roeck
2024-11-20 16:29 ` Andy Shevchenko
2024-11-25 3:07 ` Encarnacion, Cedric justine
2024-11-20 14:39 ` Guenter Roeck
2024-11-21 21:54 ` kernel test robot
2024-11-22 13:46 ` kernel test robot
2024-11-23 3:11 ` kernel test robot
2024-11-27 0:56 ` kernel test robot
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=Zz3plZOyMcxn54_h@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=Delphine_CC_Chiu@wiwynn.com \
--cc=alexisczezar.torreno@analog.com \
--cc=cedricjustine.encarnacion@analog.com \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=krzk+dt@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=radu.sabau@analog.com \
--cc=robh@kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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