From: Greg KH <gregkh@linuxfoundation.org>
To: "Joaquín Ignacio Aramendía" <samsagax@gmail.com>
Cc: linux@roeck-us.net, linux-hwmon@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] hwmon: (oxp-sensors) Refactor init() and remove probe()
Date: Mon, 17 Jul 2023 15:45:13 +0200 [thread overview]
Message-ID: <2023071739-remedy-sloping-64f6@gregkh> (raw)
In-Reply-To: <20230717124013.38796-5-samsagax@gmail.com>
On Mon, Jul 17, 2023 at 09:40:06AM -0300, Joaquín Ignacio Aramendía wrote:
> Since the driver is not hotpluggable the probe() funtion is not used
> more than once.
>
> Move all attribute registration logic to the init() function.
Again, as in patch 2/3, you forgot a signed-off-by line.
But this change isn't correct, just because a device is not
hotpluggable, does not mean it should not be using probe/release, in
fact just the opposite, it should be using that and NOT init.
But I understand why you changed the init call in patch 2/3, that is ok,
this isn't because:
> ---
> drivers/hwmon/oxp-sensors.c | 33 ++++++++++++++++-----------------
> 1 file changed, 16 insertions(+), 17 deletions(-)
>
> diff --git a/drivers/hwmon/oxp-sensors.c b/drivers/hwmon/oxp-sensors.c
> index c70d9355eeba..39de49c8a392 100644
> --- a/drivers/hwmon/oxp-sensors.c
> +++ b/drivers/hwmon/oxp-sensors.c
> @@ -431,32 +431,20 @@ static const struct hwmon_chip_info oxp_ec_chip_info = {
> .info = oxp_platform_sensors,
> };
>
> -/* Initialization logic */
> -static int oxp_platform_probe(struct platform_device *pdev)
> -{
> - const struct dmi_system_id *dmi_entry;
> - struct device *dev = &pdev->dev;
> - struct device *hwdev;
> -
> - hwdev = devm_hwmon_device_register_with_info(dev, "oxpec", NULL,
> - &oxp_ec_chip_info, NULL);
> -
> - return PTR_ERR_OR_ZERO(hwdev);
> -}
> -
> static struct platform_driver oxp_platform_driver = {
> .driver = {
> .name = "oxp-platform",
> .dev_groups = oxp_ec_groups,
> },
> - .probe = oxp_platform_probe,
> };
>
> static struct platform_device *oxp_platform_device;
>
> +/* Initialization logic */
> static int __init oxp_platform_init(void)
> {
> const struct dmi_system_id *dmi_entry;
> + struct device *hwdev;
>
> /*
> * Have to check for AMD processor here because DMI strings are the
> @@ -472,10 +460,21 @@ static int __init oxp_platform_init(void)
> board = (enum oxp_board)(unsigned long)dmi_entry->driver_data;
>
> oxp_platform_device =
> - platform_create_bundle(&oxp_platform_driver,
> - oxp_platform_probe, NULL, 0, NULL, 0);
> + platform_create_bundle(&oxp_platform_driver, NULL, NULL, 0,
> + NULL, 0);
> + if (IS_ERR(oxp_platform_device))
> + return PTR_ERR(oxp_platform_device);
>
> - return PTR_ERR_OR_ZERO(oxp_platform_device);
> + hwdev = devm_hwmon_device_register_with_info(&oxp_platform_device->dev,
> + "oxpec", NULL,
> + &oxp_ec_chip_info, NULL);
You are creating a fake platform device out of no where here, which is
tied to nothing, which isn't ok. Keep it in the proper device tree and
have it be passed to you by the driver core in the probe() function.
I think you will see that this changed where in /sys/devices/ your
device is now, right?
> + if (IS_ERR(hwdev)) {
> + platform_device_unregister(oxp_platform_device);
Making fake platform devices is generally never a good idea, please
don't do that.
thanks,
greg k-h
next prev parent reply other threads:[~2023-07-17 13:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 12:40 [PATCH 0/3] hwmon: (oxp-sensors) Refactor probe() and init() and remove devm_add_groups() Joaquín Ignacio Aramendía
2023-07-17 12:40 ` [PATCH 1/3] hwmon: (oxp-sensors) Move tt_toggle attribute to dev_groups Joaquín Ignacio Aramendía
2023-07-17 13:42 ` Greg KH
2023-07-17 16:29 ` Joaquin Aramendia
2023-07-17 12:40 ` [PATCH 2/3] hwmon: (oxp-sensors) Move board detection to the init function Joaquín Ignacio Aramendía
2023-07-17 12:40 ` [PATCH 3/3] hwmon: (oxp-sensors) Refactor init() and remove probe() Joaquín Ignacio Aramendía
2023-07-17 13:45 ` Greg KH [this message]
2023-07-17 15:02 ` Guenter Roeck
2023-07-17 16:40 ` Joaquin Aramendia
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=2023071739-remedy-sloping-64f6@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=samsagax@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®