mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Tomasz Pakuła" <tomasz.pakula.oficjalny@gmail.com>
To: Shengzhuo Wei <me@cherr.cc>
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, 02 Nov 2026 15:47:31 +0100	[thread overview]
Message-ID: <bb43e80f92a82e1a27077a45606a9c7f2678ddcf.camel@gmail.com> (raw)
In-Reply-To: <auig8ARnvkEoAagA@kernel>

On Mon, 2026-11-02 at 22:40 +0800, Shengzhuo Wei wrote:
> 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?

Yes, I meant to say -10 (not positive 10 obviously) but -8 seems like a
better fit here.

> - -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?

Yup, that range is great.

> 
> Thanks,
> Shengzhuo

      reply	other threads:[~2026-11-02 14:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-28 16:04 Shengzhuo Wei
2026-11-02 12:44 ` Tomasz Pakuła
2026-11-02 14:40   ` Shengzhuo Wei
2026-11-02 14:47     ` Tomasz Pakuła [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=bb43e80f92a82e1a27077a45606a9c7f2678ddcf.camel@gmail.com \
    --to=tomasz.pakula.oficjalny@gmail.com \
    --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=me@cherr.cc \
    --cc=michal@nozomi.space \
    --cc=oleg@makarenk.ooo \
    --cc=paul@spacefreak18.xyz \
    --cc=stable@vger.kernel.org \
    /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®