linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 1/6] Input: Add variable to track maximum concurrent playbacks
Date: Tue, 17 Sep 2024 22:14:07 +0000	[thread overview]
Message-ID: <20240917221412.1003718-2-jogletre@opensource.cirrus.com> (raw)
In-Reply-To: <20240917221412.1003718-1-jogletre@opensource.cirrus.com>

Add max_concurrent_playbacks to ff_device which contains
the maximum number of concurrent playbacks allowed by the
device.

Signed-off-by: James Ogletree <jogletre@opensource.cirrus.com>
---
 drivers/input/evdev.c | 2 +-
 include/linux/input.h | 2 ++
 2 files changed, 3 insertions(+), 1 deletion(-)

diff --git a/drivers/input/evdev.c b/drivers/input/evdev.c
index a8ce3d140722..42b55e03696b 100644
--- a/drivers/input/evdev.c
+++ b/drivers/input/evdev.c
@@ -1069,7 +1069,7 @@ static long evdev_do_ioctl(struct file *file, unsigned int cmd,
 
 	case EVIOCGEFFECTS:
 		i = test_bit(EV_FF, dev->evbit) ?
-				dev->ff->max_effects : 0;
+				dev->ff->max_concurrent_playbacks : 0;
 		if (put_user(i, ip))
 			return -EFAULT;
 		return 0;
diff --git a/include/linux/input.h b/include/linux/input.h
index 89a0be6ee0e2..6d6e450e2231 100644
--- a/include/linux/input.h
+++ b/include/linux/input.h
@@ -531,6 +531,7 @@ extern const struct class input_class;
  *	device (not emulated like ones in input_dev->ffbit)
  * @mutex: mutex for serializing access to the device
  * @max_effects: maximum number of effects supported by device
+ * @max_concurrent_playbacks: maximum number of concurrent playbacks
  * @effects: pointer to an array of effects currently loaded into device
  * @effect_owners: array of effect owners; when file handle owning
  *	an effect gets closed the effect is automatically erased
@@ -562,6 +563,7 @@ struct ff_device {
 	struct mutex mutex;
 
 	int max_effects;
+	int max_concurrent_playbacks;
 	struct ff_effect *effects;
 	struct file *effect_owners[] __counted_by(max_effects);
 };
-- 
2.43.0


  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 [RFC PATCH 0/6] Separate notions of max concurrent playbacks and James Ogletree
2024-09-17 22:14 ` James Ogletree [this message]
2024-09-17 22:14 ` [RFC PATCH 2/6] HID: logitech-hidpp: Assign max concurrent playbacks 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
2024-10-09 15:40 ` [RFC PATCH 1/6] Input: Add variable to track maximum concurrent playbacks 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-2-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).