From: "Barnabás Pőcze" <pobrn@protonmail.com>
To: Roderick Colenbrander <roderick@gaikai.com>
Cc: Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
Chris Ye <lzye@google.com>,
Roderick Colenbrander <roderick.colenbrander@sony.com>
Subject: Re: [PATCH 01/13] HID: playstation: initial DualSense USB support.
Date: Tue, 29 Dec 2020 19:12:49 +0000 [thread overview]
Message-ID: <8rsKxzY-iTczahhdGPIJKVLelQDsVzynWy9njvI9ZaOE-1qQbbE3yXMhLztiPzkkgvMPSwwb_B_rDX-YYKxir9lXR1h1CyPAIdtGABmzaco=@protonmail.com> (raw)
In-Reply-To: <CANndSKkV5HNtR=CkDekmt8xeNjSdS0Kvws5d0MQcdHV1Bf8diw@mail.gmail.com>
2020. december 28., hétfő 0:04 keltezéssel, Roderick Colenbrander írta:
> [...]
> > > + struct dualsense_input_report *ds_report;
> > > + uint8_t value;
> > > +
> > > + /* DualSense in USB uses the full HID report for reportID 1, but
> > > + * Bluetooth uses a minimal HID report for reportID 1 and reports
> > > + * the full report using reportID 49.
> > > + */
> > > + if (report->id == DS_INPUT_REPORT_USB && hdev->bus == BUS_USB) {
> > > + ds_report = (struct dualsense_input_report *)&data[1];
> > > + } else {
> > > + hid_err(hdev, "Unhandled reportID=%d\n", report->id);
> > > + return -1;
> > > + }
> > > +
> > > + input_report_abs(ds->gamepad, ABS_X, ds_report->x);
> > > + input_report_abs(ds->gamepad, ABS_Y, ds_report->y);
> > > + input_report_abs(ds->gamepad, ABS_RX, ds_report->rx);
> > > + input_report_abs(ds->gamepad, ABS_RY, ds_report->ry);
> > > + input_report_abs(ds->gamepad, ABS_Z, ds_report->z);
> > > + input_report_abs(ds->gamepad, ABS_RZ, ds_report->rz);
> > > +
> > > + value = ds_report->buttons[0] & DS_BUTTONS0_HAT_SWITCH;
> > > + if (value > 7)
> > > + value = 8; /* center */
> > > + input_report_abs(ds->gamepad, ABS_HAT0X, ps_gamepad_hat_mapping[value].x);
> > > + input_report_abs(ds->gamepad, ABS_HAT0Y, ps_gamepad_hat_mapping[value].y);
> > > +
> > > + input_report_key(ds->gamepad, BTN_WEST, ds_report->buttons[0] & DS_BUTTONS0_SQUARE);
> > > + input_report_key(ds->gamepad, BTN_SOUTH, ds_report->buttons[0] & DS_BUTTONS0_CROSS);
> > > + input_report_key(ds->gamepad, BTN_EAST, ds_report->buttons[0] & DS_BUTTONS0_CIRCLE);
> > > + input_report_key(ds->gamepad, BTN_NORTH, ds_report->buttons[0] & DS_BUTTONS0_TRIANGLE);
> > > + input_report_key(ds->gamepad, BTN_TL, ds_report->buttons[1] & DS_BUTTONS1_L1);
> > > + input_report_key(ds->gamepad, BTN_TR, ds_report->buttons[1] & DS_BUTTONS1_R1);
> > > + input_report_key(ds->gamepad, BTN_TL2, ds_report->buttons[1] & DS_BUTTONS1_L2);
> > > + input_report_key(ds->gamepad, BTN_TR2, ds_report->buttons[1] & DS_BUTTONS1_R2);
> > > + input_report_key(ds->gamepad, BTN_SELECT, ds_report->buttons[1] & DS_BUTTONS1_CREATE);
> > > + input_report_key(ds->gamepad, BTN_START, ds_report->buttons[1] & DS_BUTTONS1_OPTIONS);
> > > + input_report_key(ds->gamepad, BTN_THUMBL, ds_report->buttons[1] & DS_BUTTONS1_L3);
> > > + input_report_key(ds->gamepad, BTN_THUMBR, ds_report->buttons[1] & DS_BUTTONS1_R3);
> > > + input_report_key(ds->gamepad, BTN_MODE, ds_report->buttons[2] & DS_BUTTONS2_PS_HOME);
> >
> > Possibly this could be replaced with a loop? I have something like this in mind:
> >
> > ```
> > struct ps_gamepad_button {
> > unsigned int code;
> > uint8_t button_idx;
> > uint8_t mask;
> > } ps_gamepad_buttons[] = {...};
> >
> > for (...) {
> > struct ps_gamepad_button *b = ...;
> > input_report_key(...);
> > }
> > ```
> >
> > Or is there any reason why the unrolled version is preffered that I'm missing?
>
> It can be done from a loop. Main reason for unrolled was that it is
> actually less code and potentially a tiny bit faster, but I bet a
> compiler would have unrolled it anyway. I don't know what I want to do
> here. Being explicit feels nice (other drivers do something similar).
> [...]
I agree that the compiler would've probably unrolled it. I'd personally consider
the loop version to be shorter as I'd not consider the static array "code" -
it's really just data initialization. Anyways, may I suggest then to align the
parameters so that the given parameter of each call starts in the same column?
I think it helps readability a good deal.
next prev parent reply other threads:[~2020-12-29 19:13 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-19 6:23 [PATCH 00/13] HID: new driver for PS5 'DualSense' controller Roderick Colenbrander
2020-12-19 6:23 ` [PATCH 01/13] HID: playstation: initial DualSense USB support Roderick Colenbrander
2020-12-27 16:23 ` Barnabás Pőcze
2020-12-27 23:04 ` Roderick Colenbrander
2020-12-29 19:12 ` Barnabás Pőcze [this message]
2020-12-31 0:08 ` Barnabás Pőcze
2020-12-31 1:08 ` Roderick Colenbrander
2020-12-19 6:23 ` [PATCH 02/13] HID: playstation: use DualSense MAC address as unique identifier Roderick Colenbrander
2020-12-19 6:23 ` [PATCH 03/13] HID: playstation: add DualSense battery support Roderick Colenbrander
2020-12-19 6:23 ` [PATCH 04/13] HID: playstation: add DualSense touchpad support Roderick Colenbrander
2020-12-26 2:14 ` Samuel Čavoj
2020-12-26 22:27 ` Roderick Colenbrander
2020-12-29 19:49 ` Barnabás Pőcze
2020-12-29 21:44 ` Roderick Colenbrander
2020-12-19 6:23 ` [PATCH 05/13] HID: playstation: add DualSense accelerometer and gyroscope support Roderick Colenbrander
2020-12-19 6:23 ` [PATCH 06/13] HID: playstation: track devices in list Roderick Colenbrander
2020-12-19 6:23 ` [PATCH 07/13] HID: playstation: add DualSense Bluetooth support Roderick Colenbrander
2020-12-19 6:23 ` [PATCH 08/13] HID: playstation: add DualSense classic rumble support Roderick Colenbrander
2020-12-19 6:23 ` [PATCH 09/13] HID: playstation: add DualSense lightbar support Roderick Colenbrander
2020-12-27 14:41 ` Barnabás Pőcze
2020-12-28 21:26 ` Roderick Colenbrander
2020-12-29 18:59 ` Barnabás Pőcze
2020-12-29 19:54 ` Roderick Colenbrander
2020-12-29 20:22 ` Barnabás Pőcze
2020-12-19 6:23 ` [PATCH 10/13] HID: playstation: add microphone mute support for DualSense Roderick Colenbrander
2020-12-19 6:23 ` [PATCH 11/13] HID: playstation: add DualSense player LEDs support Roderick Colenbrander
2020-12-26 19:27 ` Samuel Čavoj
2020-12-26 23:07 ` Roderick Colenbrander
2020-12-27 14:27 ` Barnabás Pőcze
2020-12-28 22:02 ` Roderick Colenbrander
2020-12-29 18:49 ` Barnabás Pőcze
2020-12-19 6:23 ` [PATCH 12/13] HID: playstation: DualSense set LEDs to default player id Roderick Colenbrander
2020-12-27 0:08 ` Samuel Čavoj
2020-12-27 23:07 ` Roderick Colenbrander
2020-12-19 6:23 ` [PATCH 13/13] HID: playstation: report DualSense hardware and firmware version Roderick Colenbrander
2020-12-27 17:06 ` Barnabás Pőcze
2020-12-27 22:21 ` Roderick Colenbrander
2020-12-27 22:27 ` Roderick Colenbrander
2020-12-27 22:37 ` Barnabás Pőcze
2020-12-28 22:45 ` Roderick Colenbrander
2020-12-29 15:10 ` Barnabás Pőcze
2020-12-19 8:38 ` [PATCH 00/13] HID: new driver for PS5 'DualSense' controller Bastien Nocera
2020-12-19 22:39 ` Roderick.Colenbrander
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='8rsKxzY-iTczahhdGPIJKVLelQDsVzynWy9njvI9ZaOE-1qQbbE3yXMhLztiPzkkgvMPSwwb_B_rDX-YYKxir9lXR1h1CyPAIdtGABmzaco=@protonmail.com' \
--to=pobrn@protonmail.com \
--cc=benjamin.tissoires@redhat.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=lzye@google.com \
--cc=roderick.colenbrander@sony.com \
--cc=roderick@gaikai.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).