From: Aditya Dash <mradityadash@gmail.com>
To: "Derek J . Clark" <derekjohn.clark@gmail.com>
Cc: Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <bentiss@kernel.org>,
Mark Pearson <mpearson-lenovo@squebb.ca>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 5/7] HID: hid-lenovo-go: normalize calibration failure status
Date: Thu, 24 Sep 2026 02:44:58 +0530 [thread overview]
Message-ID: <20260923211458.32755-1-mradityadash@gmail.com> (raw)
In-Reply-To: <836F1B09-60CA-4A82-8293-0F9CF506E593@gmail.com>
Hi Derek,
According to my observations, data[1] seems to give the correct status
instead of data[0].
device_type in cmd_rep seems to indicate the left or right controller, and
data[0] the calibration device (gyro, joystick, or trigger).
To validate that, I ran the left gyro calibration on my Legion Go 1
and failed it on purpose.
Here is the raw data alongside cmd_rep, its contents, and data array
raw 04 00 a0 02 03 01 02 01 00
cmd_rep report_id 0x04
id 0x00
cmd 0xa0
sub_cmd 0x02
device_type 0x03 (left controller)
data[0] 0x01 (gyro)
data[1] 0x02 (failure)
data[2..3] 0x0001 (reason, little-endian)
Reading data[0] as the status would report this failure as success.
Therefore I lean towards keeping it as is.
Thanks,
Aditya
next prev parent reply other threads:[~2026-09-23 21:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 6:36 [PATCH v3 0/7] HID: hid-lenovo-go: fix controller configuration Aditya Dash
2026-09-01 6:36 ` [PATCH v3 1/7] HID: hid-lenovo-go: use the correct calibration commands Aditya Dash
2026-09-01 6:36 ` [PATCH v3 2/7] HID: hid-lenovo-go: use the right controller selectors Aditya Dash
2026-09-01 6:36 ` [PATCH v3 3/7] HID: hid-lenovo-go: initialize command completion before hardware Aditya Dash
2026-09-01 6:36 ` [PATCH v3 4/7] HID: hid-lenovo-go: return configuration request errors Aditya Dash
2026-09-01 6:36 ` [PATCH v3 5/7] HID: hid-lenovo-go: normalize calibration failure status Aditya Dash
2026-09-01 15:57 ` Derek John Clark
2026-09-01 17:06 ` Aditya
2026-09-02 12:40 ` Derek J. Clark
2026-09-05 6:10 ` Aditya Dash
2026-09-22 18:54 ` Jiri Kosina
2026-09-22 21:25 ` Derek J. Clark
2026-09-23 21:14 ` Aditya Dash [this message]
2026-09-23 22:45 ` Derek J. Clark
2026-09-01 6:36 ` [PATCH v3 6/7] HID: hid-lenovo-go: reject unknown calibration action Aditya Dash
2026-09-01 6:36 ` [PATCH v3 7/7] HID: hid-lenovo-go: clear calibration status on start Aditya Dash
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=20260923211458.32755-1-mradityadash@gmail.com \
--to=mradityadash@gmail.com \
--cc=bentiss@kernel.org \
--cc=derekjohn.clark@gmail.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpearson-lenovo@squebb.ca \
/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®