From: James Ogletree <jogletre@opensource.cirrus.com>
To: <jikos@kernel.org>, <bentiss@kernel.org>, <dmitry.torokhov@gmail.com>
Cc: <linux-input@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-usb@vger.kernel.org>, <patches@opensource.cirrus.com>,
James Ogletree <jogletre@opensource.cirrus.com>
Subject: [RFC PATCH 0/6] Separate notions of max concurrent playbacks and
Date: Tue, 17 Sep 2024 22:14:06 +0000 [thread overview]
Message-ID: <20240917221412.1003718-1-jogletre@opensource.cirrus.com> (raw)
Currently the notion of maximum number of effects a device can
keep in its memory is tied to the number of effects a device
can play at the same time. The same value that EVIOCGEFFECTS
ioctl reports also acts as a ceiling on the number of effects
that can be uploaded.
In order to support devices with the ability to store a
different number of effects than can be simultaneously played,
it appears necessary to separate these notions.
James Ogletree (6):
Input: Add variable to track maximum concurrent playbacks
HID: logitech-hidpp: Assign max concurrent playbacks
HID: pidff: Assign max concurrent playbacks
Input: cs40l50 - Assign max concurrent playbacks
Input: da7280 - Assign max concurrent playbacks
Input: uinput - Assign max concurrent playbacks
drivers/hid/hid-logitech-hidpp.c | 1 +
drivers/hid/usbhid/hid-pidff.c | 1 +
drivers/input/evdev.c | 2 +-
drivers/input/misc/cs40l50-vibra.c | 3 ++-
drivers/input/misc/da7280.c | 1 +
drivers/input/misc/uinput.c | 1 +
include/linux/input.h | 2 ++
7 files changed, 9 insertions(+), 2 deletions(-)
--
2.43.0
next reply other threads:[~2024-09-17 22:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 22:14 James Ogletree [this message]
2024-09-17 22:14 ` [RFC PATCH 1/6] Input: Add variable to track maximum concurrent playbacks James Ogletree
2024-09-17 22:14 ` [RFC PATCH 2/6] HID: logitech-hidpp: Assign max " James Ogletree
2024-09-17 22:14 ` [RFC PATCH 3/6] HID: pidff: " James Ogletree
2024-09-17 22:14 ` [RFC PATCH 4/6] Input: cs40l50 - " James Ogletree
2024-09-17 22:14 ` [RFC PATCH 5/6] Input: da7280 " James Ogletree
2024-09-17 22:14 ` [RFC PATCH 6/6] Input: uinput " James Ogletree
-- strict thread matches above, loose matches on Subject: below --
2024-10-09 15:40 [RFC PATCH 0/6] Separate notions of max concurrent playbacks and James Ogletree
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=20240917221412.1003718-1-jogletre@opensource.cirrus.com \
--to=jogletre@opensource.cirrus.com \
--cc=bentiss@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=patches@opensource.cirrus.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;
as well as URLs for NNTP newsgroup(s).