From: Tero Kristo <tero.kristo@linux.intel.com>
To: Angela Czubak <acz@semihalf.com>
Cc: linux-input@vger.kernel.org, benjamin.tissoires@redhat.com,
jikos@kernel.org, linux-kernel@vger.kernel.org,
dmitry.torokhov@gmail.com
Subject: Re: [PATCH] HID: i2c-hid: fix the report-id passed in via set_or_send_report
Date: Thu, 18 Aug 2022 16:33:53 +0300 [thread overview]
Message-ID: <8b71b3a0-28ed-6894-5566-139d7fc03223@linux.intel.com> (raw)
In-Reply-To: <CAB4aORWWL7w1rVCrFw-Q2aof6WeQZR5iYRFg2UrvQQwHZzy7hA@mail.gmail.com>
Hello,
Yes, I think this is a problem. Maybe we need to introduce some sort of
quirk for the devices that are broken and expect the 0xf device id to be
passed to them?
-Tero
On 18/08/2022 13:27, Angela Czubak wrote:
> Hi Tero,
>
> I believe this is not the right solution. To my mind the spec does not
> mention anything that the ID in the payload of SET_REPORT command
> should be altered; you have a full byte to us, so why not?
> Other than that this will result into problems with sending reports
> via output register: for any report with report ID >=0xF we will get
> the same report ID in the payload, so how could the device know which
> one we have in mind?
> Dmitry's rework was intended to actually solve problems with large
> report IDs being incorrectly overwritten with 0xF.
>
> Regards,
> Angela
>
> On Tue, Jul 26, 2022 at 10:05 AM Tero Kristo
> <tero.kristo@linux.intel.com> wrote:
>> The formatting of the data passed to the i2c HID data register was
>> changed with the re-work of the i2c-hid-core. Previously the report ID
>> passed in was encoded as 0xF if the report-id was greater than 0xF
>> (similar to what is done with the command portion.) Now with the rework,
>> a full report-id is passed in always, and this causes the messages to be
>> rejected by the i2c controller. Fix this by encoding the report-id
>> field in the same manner as previously was done.
>>
>> Fixes: dbe0dd5fd2e0 ("HID: i2c-hid: explicitly code setting and sending
>> reports")
>> Signed-off-by: Tero Kristo <tero.kristo@linux.intel.com>
>> ---
>> drivers/hid/i2c-hid/i2c-hid-core.c | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/drivers/hid/i2c-hid/i2c-hid-core.c b/drivers/hid/i2c-hid/i2c-hid-core.c
>> index c078f09a2318..156b12f840c4 100644
>> --- a/drivers/hid/i2c-hid/i2c-hid-core.c
>> +++ b/drivers/hid/i2c-hid/i2c-hid-core.c
>> @@ -296,6 +296,9 @@ static size_t i2c_hid_format_report(u8 *buf, int report_id,
>> {
>> size_t length = sizeof(__le16); /* reserve space to store size */
>>
>> + if (report_id > 0xF)
>> + report_id = 0xF;
>> +
>> if (report_id)
>> buf[length++] = report_id;
>>
>> --
>> 2.25.1
>>
prev parent reply other threads:[~2022-08-18 13:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 8:05 [PATCH] HID: i2c-hid: fix the report-id passed in via set_or_send_report Tero Kristo
2022-08-18 10:27 ` Angela Czubak
2022-08-18 13:33 ` Tero Kristo [this message]
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=8b71b3a0-28ed-6894-5566-139d7fc03223@linux.intel.com \
--to=tero.kristo@linux.intel.com \
--cc=acz@semihalf.com \
--cc=benjamin.tissoires@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jikos@kernel.org \
--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