From: Vadym Tytan <titanv3585@gmail.com>
To: Roderick Colenbrander <thunderbird2k@gmail.com>
Cc: Roderick Colenbrander <roderick.colenbrander@sony.com>,
Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <bentiss@kernel.org>,
linux-kernel@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [PATCH] HID: playstation: DS4: Add BT poll interval adjustment
Date: Mon, 9 Jun 2025 14:25:34 +0200 [thread overview]
Message-ID: <7a6083df-9060-4d07-8293-304a3f5f6cdd@gmail.com> (raw)
In-Reply-To: <CAEc3jaCEENSMbWFcQyjWLP+4UPv3_2inARZLJsmXYF7zVbhkug@mail.gmail.com>
> Do you have a strong use case or reason to add it back?
I wouldn't say *strong* per se, but if something:
- Can be adjustable
- I think if hardware is capable of such thing it's better to have
adjustment of it available to user.
- It's better to have an option then no option at all, let the user
decide.
- Doesn't break the hardware nor software
- When decreasing polling interval
- Battery impact is just faster discharging, it doesn't "breaks" it
- Bluetooth stack won't break, it could be just "overwhelmed"
- When increasing polling interval
- No negative impact at all (if we wouldn't count the user who can
set polling interval to like 63, and have choppy controls, that's why
defaults exists)
- Have benefits
- PI can be decreased for smoother controls in cost of battery life
- PI can be also increased to save battery in cost of smooth controls
- Doesn't impact anything nor anybody on defaults.
> The not adjustable referred to USB, which is not adjustable. So keep
> that one the way it is.
Oh, OK, I understood this in another way, but that make sense too.
prev parent reply other threads:[~2025-06-09 12:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250508210148.799578-1-titanv3585@gmail.com>
2025-05-08 21:41 ` Vadym Tytan
2025-05-09 22:06 ` kernel test robot
2025-05-13 8:44 ` Vadym Tytan
2025-06-30 3:41 ` Terry Junge
2025-06-30 14:59 ` Vadym Tytan
2025-06-08 18:08 ` Roderick Colenbrander
2025-06-09 12:25 ` Vadym Tytan [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=7a6083df-9060-4d07-8293-304a3f5f6cdd@gmail.com \
--to=titanv3585@gmail.com \
--cc=bentiss@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roderick.colenbrander@sony.com \
--cc=thunderbird2k@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®