linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 v2 07/13] HID: playstation: add DualSense Bluetooth support.
Date: Thu, 07 Jan 2021 20:18:58 +0000	[thread overview]
Message-ID: <gzUzvibAvaIyvKhvSZUEHSfjBnwtAdxVGnOGuAOyFkoI5mWp1VqqVeNhSD5M0M2NYxhUU5zjy4DitGclUhZkudSfmsSr7JaNv_cN8HZ3JK8=@protonmail.com> (raw)
In-Reply-To: <20210102223109.996781-8-roderick@gaikai.com>

Hi


2021. január 2., szombat 23:31 keltezéssel, Roderick Colenbrander írta:

> From: Roderick Colenbrander <roderick.colenbrander@sony.com>
>
> This patch adds support for the DualSense when operating in Bluetooth mode.
> The device has the same behavior as the DualShock 4 in that by default it
> sends a limited input report (0x1), but after requesting calibration data,
> it switches to an extended input report (report 49), which adds data for
> touchpad, motion sensors, battery and more.
>
> Signed-off-by: Roderick Colenbrander <roderick.colenbrander@sony.com>
> [...]
>  static struct input_dev *ps_gamepad_create(struct hid_device *hdev)
>  {
>  	struct input_dev *gamepad;
> @@ -406,6 +418,18 @@  static int dualsense_get_calibration_data(struct dualsense *ds)
>  		goto err_free;
>  	}
>
> +	if (ds->base.hdev->bus == BUS_BLUETOOTH) {
> +		/* Last 4 bytes contains crc32 */

Most other comments have a period at the end. I know this is a minor thing,
but I believe being consistent is better than not.

And shouldn't this CRC be checked in `dualsense_get_mac_address()`?
If so, maybe a helper function could be created that wraps the `hid_hw_raw_request()`
call?


> +		uint8_t crc_offset = DS_FEATURE_REPORT_CALIBRATION_SIZE - 4;
> +		uint32_t report_crc = get_unaligned_le32(&buf[crc_offset]);
> +
> +		if (!ps_check_crc32(0xa3, buf, crc_offset, report_crc)) {

Maybe that 0xa3 could be named?


> +			hid_err(ds->base.hdev, "DualSense calibration report CRC's check failed\n");
> +			ret = -EILSEQ;
> +			goto err_free;
> +		}
> +	}
> +
>  	gyro_pitch_bias  = get_unaligned_le16(&buf[1]);
>  	gyro_yaw_bias    = get_unaligned_le16(&buf[3]);
>  	gyro_roll_bias   = get_unaligned_le16(&buf[5]);
> @@ -515,6 +539,16 @@  static int dualsense_parse_report(struct ps_device *ps_dev, struct hid_report *r
>  	 */
>  	if (report->id == DS_INPUT_REPORT_USB && hdev->bus == BUS_USB) {
>  		ds_report = (struct dualsense_input_report *)&data[1];
> +	} else if (report->id == DS_INPUT_REPORT_BT && hdev->bus == BUS_BLUETOOTH) {
> +		/* Last 4 bytes of input report contain crc32 */
> +		uint32_t report_crc = get_unaligned_le32(&data[size - 4]);
> +
> +		if (!ps_check_crc32(0xa1, data, size - 4, report_crc)) {

And this 0xa1 as well?


> +			hid_err(hdev, "DualSense input CRC's check failed, size=%d\n", size);
> +			return -EILSEQ;
> +		}
> +
> +		ds_report = (struct dualsense_input_report *)&data[2];
>  	} else {
>  		hid_err(hdev, "Unhandled reportID=%d\n", report->id);
>  		return -1;
> [...]


Regards,
Barnabás Pőcze


  reply	other threads:[~2021-01-07 20:19 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-02 22:30 [PATCH v2 00/13] HID: new driver for PS5 'DualSense' controller Roderick Colenbrander
2021-01-02 22:30 ` [PATCH v2 01/13] HID: playstation: initial DualSense USB support Roderick Colenbrander
2021-01-04 12:20   ` Jiri Kosina
2021-01-05  8:20   ` Benjamin Tissoires
2021-01-07 17:14   ` Barnabás Pőcze
2021-01-08  7:12     ` Roderick Colenbrander
2021-01-08 11:53       ` Barnabás Pőcze
2021-01-02 22:30 ` [PATCH v2 02/13] HID: playstation: use DualSense MAC address as unique identifier Roderick Colenbrander
2021-01-07 17:22   ` Barnabás Pőcze
2021-01-02 22:30 ` [PATCH v2 03/13] HID: playstation: add DualSense battery support Roderick Colenbrander
2021-01-07 17:50   ` Barnabás Pőcze
2021-01-02 22:31 ` [PATCH v2 04/13] HID: playstation: add DualSense touchpad support Roderick Colenbrander
2021-01-07 17:55   ` Barnabás Pőcze
2021-01-02 22:31 ` [PATCH v2 05/13] HID: playstation: add DualSense accelerometer and gyroscope support Roderick Colenbrander
2021-01-07 13:34   ` Florian Märkl
2021-01-08  5:51     ` Roderick Colenbrander
2021-01-07 18:51   ` Barnabás Pőcze
2021-01-08  6:06     ` Roderick Colenbrander
2021-01-08 12:01       ` Barnabás Pőcze
2021-01-08 17:15         ` Siarhei Vishniakou
2021-01-08 19:54           ` Roderick Colenbrander
2021-01-09  0:11             ` Siarhei Vishniakou
2021-01-11  0:06               ` Roderick Colenbrander
2021-01-02 22:31 ` [PATCH v2 06/13] HID: playstation: track devices in list Roderick Colenbrander
2021-01-07 20:13   ` Barnabás Pőcze
2021-01-02 22:31 ` [PATCH v2 07/13] HID: playstation: add DualSense Bluetooth support Roderick Colenbrander
2021-01-07 20:18   ` Barnabás Pőcze [this message]
2021-01-02 22:31 ` [PATCH v2 08/13] HID: playstation: add DualSense classic rumble support Roderick Colenbrander
2021-01-07 20:41   ` Barnabás Pőcze
2021-01-07 20:48     ` Barnabás Pőcze
2021-01-08 17:01     ` Roderick Colenbrander
2021-01-02 22:31 ` [PATCH v2 09/13] HID: playstation: add DualSense lightbar support Roderick Colenbrander
2021-01-07 21:01   ` Barnabás Pőcze
2021-01-02 22:31 ` [PATCH v2 10/13] HID: playstation: add microphone mute support for DualSense Roderick Colenbrander
2021-01-07 21:57   ` Barnabás Pőcze
2021-01-02 22:31 ` [PATCH v2 11/13] HID: playstation: add DualSense player LEDs support Roderick Colenbrander
2021-01-07 22:17   ` Barnabás Pőcze
2021-01-02 22:31 ` [PATCH v2 12/13] HID: playstation: DualSense set LEDs to default player id Roderick Colenbrander
2021-01-07 22:25   ` Barnabás Pőcze
2021-01-02 22:31 ` [PATCH v2 13/13] HID: playstation: report DualSense hardware and firmware version Roderick Colenbrander
2021-01-07 22:26   ` Barnabás Pőcze
2021-01-09  1:35     ` 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='gzUzvibAvaIyvKhvSZUEHSfjBnwtAdxVGnOGuAOyFkoI5mWp1VqqVeNhSD5M0M2NYxhUU5zjy4DitGclUhZkudSfmsSr7JaNv_cN8HZ3JK8=@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).