From: Max Staudt <max@enpas.org>
To: Rahul Rameshbabu <sergeantsagara@protonmail.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Vicki Pfau <vi@endrift.com>, Pavel Rojtberg <rojtberg@gmail.com>,
Roderick Colenbrander <roderick@gaikai.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] xpad: XTYPE_XBOX: Report analog buttons
Date: Mon, 28 Aug 2023 00:07:39 +0900 [thread overview]
Message-ID: <84c7f090-b84e-fbea-4e2e-9730a39e2db8@enpas.org> (raw)
In-Reply-To: <87fs45u4o2.fsf@protonmail.com>
On 8/27/23 01:52, Rahul Rameshbabu wrote:
> You will want to update the commit message subject to use the prefix
> "Input: xpad -" instead of "xpad:".
Thanks, will do!
>> +/* used for analog face buttons mapped to axes */
>> +static const signed short xpad_abs_analog_face_buttons[] = {
>> + ABS_MISC + 0, ABS_MISC + 1, /* A, B */
>> + ABS_MISC + 3, ABS_MISC + 4, /* X, Y */
>> + ABS_MISC + 2, ABS_MISC + 5, /* C, Z */
>> + -1
>> +};
>
> Would it make more sense to use an enum for this?
> Something like the below enum.
>
> enum xpad_abs_analog_face_btn {
> XPAD_ABS_ANALOG_FACE_BTN_A = ABS_MISC,
> XPAD_ABS_ANALOG_FACE_BTN_B,
> XPAD_ABS_ANALOG_FACE_BTN_C,
> XPAD_ABS_ANALOG_FACE_BTN_X,
> XPAD_ABS_ANALOG_FACE_BTN_Y,
> XPAD_ABS_ANALOG_FACE_BTN_Z,
> XPAD_ABS_ANALOG_FACE_BTN_END, /* Must remain as the last element */
> };
>
> This would clean up both xpad_process_packet and xpad_set_up_abs a bit
> in my opinion. Your loop for xpad_set_up_abs would look like the
> following.
>
> enum xpad_abs_analog_face_btn btn;
>
> ...
>
> for (btn = XPAD_ABS_ANALOG_FACE_BTN_A; btn != XPAD_ABS_ANALOG_FACE_BTN_END; ++btn)
> xpad_set_up_abs(input_dev, btn);
I agree, that looks cleaner.
Since it's a step closer to standardising a mapping for those analog buttons, I'd like to wait and see whether there is a consensus across drivers and maintainers. Maybe we can include something like this enum in input-event-codes.h and have a really clean solution.
Thanks!
Max
next prev parent reply other threads:[~2023-08-27 15:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-26 15:21 [PATCH 0/2] xpad, hid-sony: " Max Staudt
2023-08-26 15:21 ` [PATCH 1/2] xpad: XTYPE_XBOX: " Max Staudt
2023-08-26 16:52 ` Rahul Rameshbabu
2023-08-27 15:07 ` Max Staudt [this message]
2023-08-26 15:21 ` [PATCH 2/2] hid-sony: DS3: Report analog buttons for Sixaxis Max Staudt
2023-08-29 15:53 ` Max Staudt
2023-09-06 15:45 ` Roderick Colenbrander
2023-09-11 16:51 ` Max Staudt
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=84c7f090-b84e-fbea-4e2e-9730a39e2db8@enpas.org \
--to=max@enpas.org \
--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 \
--cc=roderick@gaikai.com \
--cc=rojtberg@gmail.com \
--cc=sergeantsagara@protonmail.com \
--cc=vi@endrift.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®