From: Aleksa Savic <savicaleksa83@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: savicaleksa83@gmail.com, linux-hwmon@vger.kernel.org,
Jack Doan <me@jackdoan.com>, Jean Delvare <jdelvare@suse.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] hwmon: (aquacomputer_d5next) Add selective 200ms delay after sending ctrl report
Date: Thu, 10 Aug 2023 20:15:30 +0200 [thread overview]
Message-ID: <e7bcf401-991c-808c-66df-65664940bf22@gmail.com> (raw)
In-Reply-To: <c151d464-da26-4c53-ba7a-d16bb8fca949@roeck-us.net>
On 2023-08-10 06:09:13 GMT+02:00, Guenter Roeck wrote:
> On Mon, Aug 07, 2023 at 07:20:03PM +0200, Aleksa Savic wrote:
>> Add a 200ms delay after sending a ctrl report to Quadro,
>> Octo, D5 Next and Aquaero to give them enough time to
>> process the request and save the data to memory. Otherwise,
>> under heavier userspace loads where multiple sysfs entries
>> are usually set in quick succession, a new ctrl report could
>> be requested from the device while it's still processing the
>> previous one and fail with -EPIPE. The delay is only applied
>> if two ctrl report operations are near each other in time.
>>
>> Reported by a user on Github [1] and tested by both of us.
>>
>> [1] https://github.com/aleksamagicka/aquacomputer_d5next-hwmon/issues/82
>>
>> Fixes: 752b927951ea ("hwmon: (aquacomputer_d5next) Add support for Aquacomputer Octo")
>> Signed-off-by: Aleksa Savic <savicaleksa83@gmail.com>
>
> I would have suggested to use fsleep() to avoid unnecessary
> sleep times if they are small, bt I guess it doesn't make much
> of a difference.
Will keep that in mind.
>
> Applied.
Will this patch perhaps be marked for stable?
Thanks,
Aleksa
>
> Thanks,
> Guenter
next prev parent reply other threads:[~2023-08-10 18:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 17:20 [PATCH v3] hwmon: (aquacomputer_d5next) Add selective 200ms delay after sending ctrl report Aleksa Savic
2023-08-10 4:09 ` Guenter Roeck
2023-08-10 18:15 ` Aleksa Savic [this message]
2023-08-11 23:05 ` Guenter Roeck
2023-08-12 18:49 ` Aleksa Savic
2023-08-14 13:42 ` Guenter Roeck
2023-08-15 15:22 ` Aleksa Savic
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=e7bcf401-991c-808c-66df-65664940bf22@gmail.com \
--to=savicaleksa83@gmail.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=me@jackdoan.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