From: "Shengzhuo Wei" <me@cherr.cc>
To: "Tomasz Pakuła" <tomasz.pakula.oficjalny@gmail.com>
Cc: "Shengzhuo Wei" <me@cherr.cc>,
"Oleg Makarenko" <oleg@makarenk.ooo>,
"Jiri Kosina" <jikos@kernel.org>,
"Benjamin Tissoires" <bentiss@kernel.org>,
"Michał Kopeć" <michal@nozomi.space>,
"Paul Dino Jones" <paul@spacefreak18.xyz>,
linux-input@vger.kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] HID: pidff: bound the unit exponent rescaling loop
Date: Mon, 2 Nov 2026 22:40:48 +0800 [thread overview]
Message-ID: <auig8ARnvkEoAagA@kernel> (raw)
In-Reply-To: <bbd1ec87a9fff50b189f74cbd21e1d5bddf41136.camel@gmail.com>
Hi Tomasz,
Thanks for testing and reviewing the patch.
> Should we maybe add a warning to the driver that the time exponent might
> be out of a sane range? Sane range being, say, 10 to 0? This of course
> would have to happen during init stage not to spam dmesg.
For the initialization-time warning, would -8 to 0 be a reasonable
exponent range?
- -8 is the lowest exponent in the commonly used signed 4-bit HID
encoding.
- 0 allows a time unit of one second.
- Positive exponents 1 through 7 would give time units of ten seconds
or more, which seem unusually coarse for force-feedback effects.
This would only be a warning threshold: the driver would still accept
the device and leave the rescaling behavior unchanged.
Does that match what you had in mind, or would you prefer a different
range?
Thanks,
Shengzhuo
next prev parent reply other threads:[~2026-11-02 14:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 16:04 [PATCH] HID: pidff: bound the unit exponent rescaling loop Shengzhuo Wei
2026-10-28 16:06 ` sashiko-bot
2026-11-02 12:44 ` Tomasz Pakuła
2026-11-02 14:40 ` Shengzhuo Wei [this message]
2026-11-02 14:47 ` Tomasz Pakuła
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=auig8ARnvkEoAagA@kernel \
--to=me@cherr.cc \
--cc=bentiss@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=michal@nozomi.space \
--cc=oleg@makarenk.ooo \
--cc=paul@spacefreak18.xyz \
--cc=stable@vger.kernel.org \
--cc=tomasz.pakula.oficjalny@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