mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Max Staudt <max@enpas.org>
To: Roderick Colenbrander <roderick.colenbrander@sony.com>,
	Jiri Kosina <jikos@kernel.org>,
	Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org, max@enpas.org
Subject: [PATCH v1 3/7] HID: playstation: DS4: Don't fail on FW/HW version request
Date: Mon, 15 Jan 2024 23:45:34 +0900	[thread overview]
Message-ID: <20240115144538.12018-4-max@enpas.org> (raw)
In-Reply-To: <20240115144538.12018-1-max@enpas.org>

Some third-party controllers can't report firmware/hardware version.

Unlike for the DualSense, the driver does not use these values for
anything in the DualShock 4 case, but merely exposes them via sysfs.
They will simply be 0x0.

Signed-off-by: Max Staudt <max@enpas.org>
---
 drivers/hid/hid-playstation.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/hid/hid-playstation.c b/drivers/hid/hid-playstation.c
index 0a3c442af305..12321cae4416 100644
--- a/drivers/hid/hid-playstation.c
+++ b/drivers/hid/hid-playstation.c
@@ -2561,7 +2561,7 @@ static struct ps_device *dualshock4_create(struct hid_device *hdev)
 	ret = dualshock4_get_firmware_info(ds4);
 	if (ret) {
 		hid_err(hdev, "Failed to get firmware info from DualShock4\n");
-		return ERR_PTR(ret);
+		hid_err(hdev, "HW/FW version data in sysfs will be invalid.\n");
 	}
 
 	ret = ps_devices_list_add(ps_dev);
-- 
2.39.2


  parent reply	other threads:[~2024-01-15 14:48 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-15 14:45 [PATCH v1 0/7] HID: playstation: DS4: LED bugfix, third-party gamepad support Max Staudt
2024-01-15 14:45 ` [PATCH v1 1/7] HID: playstation: DS4: Fix LED blinking Max Staudt
2024-01-15 14:45 ` [PATCH v1 2/7] HID: playstation: DS4: Don't fail on MAC address request Max Staudt
2024-01-25  0:39   ` Roderick Colenbrander
2024-01-27  8:51     ` Max Staudt
2024-01-30 20:59       ` Roderick Colenbrander
2024-01-31 15:05         ` Max Staudt
2024-01-15 14:45 ` Max Staudt [this message]
2024-01-25  0:43   ` [PATCH v1 3/7] HID: playstation: DS4: Don't fail on FW/HW version request Roderick Colenbrander
2024-01-27  8:56     ` Max Staudt
2024-01-15 14:45 ` [PATCH v1 4/7] HID: playstation: DS4: Don't fail on calibration data request Max Staudt
2024-01-15 14:45 ` [PATCH v1 5/7] HID: playstation: DS4: Parse minimal report 0x01 Max Staudt
2024-01-25  0:54   ` Roderick Colenbrander
2024-01-27  9:00     ` Max Staudt
2024-01-15 14:45 ` [PATCH v1 6/7] HID: playstation: Simplify device type ID Max Staudt
2024-01-25  1:01   ` Roderick Colenbrander
2024-01-15 14:45 ` [PATCH v1 7/7] HID: playstation: DS4: Add VID/PID for SZ-MYPOWER controllers Max Staudt
2024-01-25  1:03   ` Roderick Colenbrander
2024-01-27 11:16     ` Max Staudt
2024-01-30 21:07       ` Roderick Colenbrander
2024-01-31 14:48         ` Max Staudt
2024-01-31 16:34           ` Roderick Colenbrander
2024-02-01 15:56             ` Max Staudt
2024-01-23  9:47 ` [PATCH v1 0/7] HID: playstation: DS4: LED bugfix, third-party gamepad support Jiri Kosina
2024-01-24 22:24   ` Roderick Colenbrander
2024-01-27 11:52     ` 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=20240115144538.12018-4-max@enpas.org \
    --to=max@enpas.org \
    --cc=benjamin.tissoires@redhat.com \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roderick.colenbrander@sony.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

Powered by JetHome