From: Bastien Nocera <hadess@hadess.net>
To: Andreas Bergmeier <abergmeier@gmx.net>,
lains@riseup.net, jikos@kernel.org,
benjamin.tissoires@redhat.com
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] HID: Send SwID in GetProtocolVersion
Date: Mon, 14 Nov 2022 15:19:09 +0100 [thread overview]
Message-ID: <9e77ba98322873ba8790d4fb7904c844db2d085d.camel@hadess.net> (raw)
In-Reply-To: <20221111194526.1375601-1-abergmeier@gmx.net>
On Fri, 2022-11-11 at 20:45 +0100, Andreas Bergmeier wrote:
> According to docs a SwID should be sent for GetProtocolVersion.
> > 0x10.DeviceIndex.0x00.0x1n
> where n is SwID
I would mention the value of CMD_ROOT_GET_PROTOCOL_VERSION (0x10) in
the commit message, but otherwise looks good to me.
Reviewed-by: Bastien Nocera <hadess@hadess.net>
>
> Signed-off-by: Andreas Bergmeier <abergmeier@gmx.net>
> ---
> drivers/hid/hid-logitech-hidpp.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/hid/hid-logitech-hidpp.c b/drivers/hid/hid-
> logitech-hidpp.c
> index a0c148a8df6c..964a523c3de7 100644
> --- a/drivers/hid/hid-logitech-hidpp.c
> +++ b/drivers/hid/hid-logitech-hidpp.c
> @@ -896,7 +896,7 @@ static int hidpp_root_get_protocol_version(struct
> hidpp_device *hidpp)
>
> ret = hidpp_send_rap_command_sync(hidpp,
> HIDPP_PAGE_ROOT_IDX,
> - CMD_ROOT_GET_PROTOCOL_VERSION,
> + CMD_ROOT_GET_PROTOCOL_VERSION |
> LINUX_KERNEL_SW_ID,
> ping_data, sizeof(ping_data), &response);
>
> if (ret == HIDPP_ERROR_INVALID_SUBID) {
> --
> 2.34.1
>
next prev parent reply other threads:[~2022-11-14 14:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 19:45 [PATCH 1/1] HID: Send SwID in GetProtocolVersion Andreas Bergmeier
2022-11-14 14:19 ` Bastien Nocera [this message]
2022-11-21 21:35 ` Jiri Kosina
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=9e77ba98322873ba8790d4fb7904c844db2d085d.camel@hadess.net \
--to=hadess@hadess.net \
--cc=abergmeier@gmx.net \
--cc=benjamin.tissoires@redhat.com \
--cc=jikos@kernel.org \
--cc=lains@riseup.net \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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