public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Bomar <dbdaniel42@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Jiri Kosina <jikos@kernel.org>,
	Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	Daniel Bomar <dbdaniel42@gmail.com>
Subject: [PATCH 1/4] input: uapi: Add trigger_left and trigger_right to ff_rumble_effect struct
Date: Sun, 10 Apr 2022 17:06:33 -0500	[thread overview]
Message-ID: <20220410220633.5235-1-dbdaniel42@gmail.com> (raw)

Add 2 variables to the control the trigger motors into the struct that
gets passed in from userspace.

ff_rumble_effect is part of a union in ff_effect. This does not grow the
total size of the union so should be ABI compatible.

Signed-off-by: Daniel Bomar <dbdaniel42@gmail.com>
---
 include/uapi/linux/input.h | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/include/uapi/linux/input.h b/include/uapi/linux/input.h
index ee3127461ee0..d187e00d91a1 100644
--- a/include/uapi/linux/input.h
+++ b/include/uapi/linux/input.h
@@ -415,6 +415,8 @@ struct ff_periodic_effect {
  * struct ff_rumble_effect - defines parameters of a periodic force-feedback effect
  * @strong_magnitude: magnitude of the heavy motor
  * @weak_magnitude: magnitude of the light one
+ * @trigger_left: magnitude of the motor behind the left trigger
+ * @trigger_right: magnitude of the motor behind the right trigger
  *
  * Some rumble pads have two motors of different weight. Strong_magnitude
  * represents the magnitude of the vibration generated by the heavy one.
@@ -422,6 +424,8 @@ struct ff_periodic_effect {
 struct ff_rumble_effect {
 	__u16 strong_magnitude;
 	__u16 weak_magnitude;
+	__u16 trigger_left;
+	__u16 trigger_right;
 };
 
 /**
-- 
2.35.1


                 reply	other threads:[~2022-04-10 22:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220410220633.5235-1-dbdaniel42@gmail.com \
    --to=dbdaniel42@gmail.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@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