linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Li Zetao <lizetao1@huawei.com>
To: Guenter Roeck <linux@roeck-us.net>, <jikos@kernel.org>,
	<bentiss@kernel.org>, <michael.zaidman@gmail.com>,
	<gupt21@gmail.com>, <djogorchock@gmail.com>,
	<rrameshbabu@nvidia.com>, <bonbons@linux-vserver.org>,
	<roderick.colenbrander@sony.com>, <david@readahead.eu>,
	<savicaleksa83@gmail.com>, <me@jackdoan.com>, <jdelvare@suse.com>,
	<mail@mariuszachmann.de>, <wilken.gottwalt@posteo.net>,
	<jonas@protocubo.io>, <mezin.alexander@gmail.com>
Cc: <linux-input@vger.kernel.org>, <linux-i2c@vger.kernel.org>,
	<linux-hwmon@vger.kernel.org>
Subject: Re: [PATCH -next 19/19] hwmon: (nzxt-smart2) Use devm_hid_hw_start_and_open in nzxt_smart2_hid_probe()
Date: Thu, 5 Sep 2024 23:39:58 +0800	[thread overview]
Message-ID: <0915517c-50ff-4867-9b6d-e55357d0ed0f@huawei.com> (raw)
In-Reply-To: <eb7ffcbb-1e6c-448b-a09f-e10fd187a1ef@roeck-us.net>

Hi,

在 2024/9/4 22:14, Guenter Roeck 写道:
> On 9/4/24 05:36, Li Zetao wrote:
>> Currently, the nzxt-smart2 module needs to maintain hid resources
>> by itself. Consider using devm_hid_hw_start_and_open helper to ensure
> 
> For all patches:
> 
> s/Consider using/Use/
ok
> 
>> that hid resources are consistent with the device life cycle, and release
>> hid resources before device is released. At the same time, it can avoid
>> the goto-release encoding, drop the out_hw_close and out_hw_stop
>> lables, and directly return the error code when an error occurs.
>>
>> Signed-off-by: Li Zetao <lizetao1@huawei.com>
>> ---
>>   drivers/hwmon/nzxt-smart2.c | 22 +++-------------------
>>   1 file changed, 3 insertions(+), 19 deletions(-)
>>
>> diff --git a/drivers/hwmon/nzxt-smart2.c b/drivers/hwmon/nzxt-smart2.c
>> index df6fa72a6b59..b5721a42c0d3 100644
>> --- a/drivers/hwmon/nzxt-smart2.c
>> +++ b/drivers/hwmon/nzxt-smart2.c
>> @@ -750,14 +750,10 @@ static int nzxt_smart2_hid_probe(struct 
>> hid_device *hdev,
>>       if (ret)
>>           return ret;
>> -    ret = hid_hw_start(hdev, HID_CONNECT_HIDRAW);
>> +    ret = devm_hid_hw_start_and_open(hdev, HID_CONNECT_HIDRAW);
>>       if (ret)
>>           return ret;
>> -    ret = hid_hw_open(hdev);
>> -    if (ret)
>> -        goto out_hw_stop;
>> -
>>       hid_device_io_start(hdev);
>>       init_device(drvdata, UPDATE_INTERVAL_DEFAULT_MS);
>> @@ -765,19 +761,10 @@ static int nzxt_smart2_hid_probe(struct 
>> hid_device *hdev,
>>       drvdata->hwmon =
>>           hwmon_device_register_with_info(&hdev->dev, "nzxtsmart2", 
>> drvdata,
>>                           &nzxt_smart2_chip_info, NULL);
>> -    if (IS_ERR(drvdata->hwmon)) {
>> -        ret = PTR_ERR(drvdata->hwmon);
>> -        goto out_hw_close;
>> -    }
>> +    if (IS_ERR(drvdata->hwmon))
>> +        return PTR_ERR(drvdata->hwmon);
>>       return 0;
> 
>      return PTR_ERR_OR_ZERO(drvdata->hwmon);
> 
> Also, this can be optimized further.
> 
>      struct device *hwmon;    // and drop from struct drvdata
>      ...
>      hwmon = devm_hwmon_device_register_with_info(&hdev->dev, 
> "nzxtsmart2", drvdata,
>                               &nzxt_smart2_chip_info, NULL);
> 
>      return PTR_ERR_OR_ZERO(hwmon);
> 
> and drop the remove function entirely.
Benjamin mentioned that there are unsafe scenarios in 
hid_hw_close_and_stop, and it is necessary to ensure that the driver can 
not use manual kzalloc/kfree. So, to be extra safe, I would delete 
.remove in v2.
> 
> Thanks,
> Guenter
> 
>> -
>> -out_hw_close:
>> -    hid_hw_close(hdev);
>> -
>> -out_hw_stop:
>> -    hid_hw_stop(hdev);
>> -    return ret;
>>   }
>>   static void nzxt_smart2_hid_remove(struct hid_device *hdev)
>> @@ -785,9 +772,6 @@ static void nzxt_smart2_hid_remove(struct 
>> hid_device *hdev)
>>       struct drvdata *drvdata = hid_get_drvdata(hdev);
>>       hwmon_device_unregister(drvdata->hwmon);
>> -
>> -    hid_hw_close(hdev);
>> -    hid_hw_stop(hdev);
>>   }
>>   static const struct hid_device_id nzxt_smart2_hid_id_table[] = {
> 

      reply	other threads:[~2024-09-05 15:40 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-04 12:35 [PATCH -next 00/19] HID: convert to devm_hid_hw_start_and_open() Li Zetao
2024-09-04 12:35 ` [PATCH -next 01/19] HID: core: Use devm_add_action_or_reset helper to manage hid resources Li Zetao
2024-09-05 12:53   ` Benjamin Tissoires
2024-09-05 15:41     ` Li Zetao
2024-09-04 12:35 ` [PATCH -next 02/19] HID: cp2112: Use devm_hid_hw_start_and_open in cp2112_probe() Li Zetao
2024-09-04 12:35 ` [PATCH -next 03/19] HID: ft260: Use devm_hid_hw_start_and_open in ft260_probe() Li Zetao
2024-09-04 12:35 ` [PATCH -next 04/19] HID: mcp2200: Use devm_hid_hw_start_and_open in mcp2200_probe() Li Zetao
2024-09-04 12:35 ` [PATCH -next 05/19] HID: mcp2221: Use devm_hid_hw_start_and_open in mcp2221_probe() Li Zetao
2024-09-04 12:35 ` [PATCH -next 06/19] HID: nintendo: Use devm_hid_hw_start_and_open in nintendo_hid_probe() Li Zetao
2024-09-04 12:35 ` [PATCH -next 07/19] HID: shield: Use devm_hid_hw_start_and_open in shield_probe() Li Zetao
2024-09-05 12:57   ` Benjamin Tissoires
2024-09-04 12:35 ` [PATCH -next 08/19] HID: hid-picolcd: Use devm_hid_hw_start_and_open in picolcd_probe() Li Zetao
2024-09-05 12:59   ` Benjamin Tissoires
2024-09-04 12:35 ` [PATCH -next 09/19] HID: playstation: Use devm_hid_hw_start_and_open in ps_probe() Li Zetao
2024-09-04 12:35 ` [PATCH -next 10/19] HID: hid-steam: Use devm_hid_hw_start_and_open in steam_probe() Li Zetao
2024-09-05 13:00   ` Benjamin Tissoires
2024-09-04 12:35 ` [PATCH -next 11/19] HID: wiimote: Use devm_hid_hw_start_and_open in wiimote_hid_probe() Li Zetao
2024-09-05  6:35   ` David Rheinsberg
2024-09-05 13:05   ` Benjamin Tissoires
2024-09-04 12:36 ` [PATCH -next 12/19] hwmon: (aquacomputer_d5next) Use devm_hid_hw_start_and_open in aqc_probe() Li Zetao
2024-09-04 12:36 ` [PATCH -next 13/19] hwmon: Use devm_hid_hw_start_and_open in rog_ryujin_probe() Li Zetao
2024-09-04 14:20   ` Guenter Roeck
2024-09-04 12:36 ` [PATCH -next 14/19] hwmon: (corsair-cpro) Use devm_hid_hw_start_and_open in ccp_probe() Li Zetao
2024-09-04 12:36 ` [PATCH -next 15/19] hwmon: (corsair-psu) Use devm_hid_hw_start_and_open in corsairpsu_probe() Li Zetao
2024-09-06  4:03   ` Wilken Gottwalt
2024-09-04 12:36 ` [PATCH -next 16/19] hwmon: (gigabyte_waterforce) Use devm_hid_hw_start_and_open in waterforce_probe() Li Zetao
2024-09-04 12:36 ` [PATCH -next 17/19] hwmon: (nzxt-kraken2) Use devm_hid_hw_start_and_open in kraken2_probe() Li Zetao
2024-09-04 14:17   ` Guenter Roeck
2024-09-04 12:36 ` [PATCH -next 18/19] hwmon: (nzxt-kraken3) Use devm_hid_hw_start_and_open in kraken3_probe() Li Zetao
2024-09-04 12:36 ` [PATCH -next 19/19] hwmon: (nzxt-smart2) Use devm_hid_hw_start_and_open in nzxt_smart2_hid_probe() Li Zetao
2024-09-04 14:14   ` Guenter Roeck
2024-09-05 15:39     ` Li Zetao [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=0915517c-50ff-4867-9b6d-e55357d0ed0f@huawei.com \
    --to=lizetao1@huawei.com \
    --cc=bentiss@kernel.org \
    --cc=bonbons@linux-vserver.org \
    --cc=david@readahead.eu \
    --cc=djogorchock@gmail.com \
    --cc=gupt21@gmail.com \
    --cc=jdelvare@suse.com \
    --cc=jikos@kernel.org \
    --cc=jonas@protocubo.io \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=mail@mariuszachmann.de \
    --cc=me@jackdoan.com \
    --cc=mezin.alexander@gmail.com \
    --cc=michael.zaidman@gmail.com \
    --cc=roderick.colenbrander@sony.com \
    --cc=rrameshbabu@nvidia.com \
    --cc=savicaleksa83@gmail.com \
    --cc=wilken.gottwalt@posteo.net \
    /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).