From: Wolfram Sang <wsa@kernel.org>
To: Nikolai Kostrigin <nickel@basealt.ru>
Cc: linux-i2c@vger.kernel.org,
"open list:HID CORE LAYER" <linux-input@vger.kernel.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Colin Ian King <colin.king@canonical.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Need some help on "Input: elantech - add LEN2146 to SMBus blacklist for ThinkPad L13 Gen2"
Date: Thu, 25 Feb 2021 10:38:01 +0100 [thread overview]
Message-ID: <20210225093801.GA1008@ninjato> (raw)
In-Reply-To: <e1fd99ae-8e46-0b21-1011-db73cd75523b@basealt.ru>
[-- Attachment #1: Type: text/plain, Size: 1273 bytes --]
Hi,
> I had a preliminary discussion with Benjamin Tissoires and according to
> our agreement I repost it for wider audience.
> Blacklisting the device was decided to be a bad idea.
> But actually I managed to get touchpad totally operational via SMBus
> using a following hack:
>
> providing a parameter to i2c_i801 driver:
>
> modprobe i2c_i801 disable_features=0x2 (i.e. disable the block buffer).
So, from an I2C perspective, there are two things to mention here:
a) I am in the process of extending the I2C core to allow block
transfers > 32 byte. This is a slow process, though, because we need to
pay attention to not break userspace ABI. If this is done *and* the i801
driver supports length > 32 bytes, too, then it would work natively. If
the i801 can do this, this is a question for Jean Delvare.
b) I don't know Elantech HW but there are devices out there which allow
configuration for the block size. Something like a bit specifying if
block transfers > 32 are allowed. Or the SMBus version to support. Block
transfers > 32 are SMBus 3.0+ only. If your HW does not have that,
disabling SMBus is an option, too. Disabling it in the i801 driver is
too much of a hammer, I'd say.
Hope this helps! Happy hacking,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-02-25 9:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0d1eaadd-5350-63a4-fe6d-f8f357c49504@basealt.ru>
[not found] ` <CAO-hwJLmByHHULhJF60qOUAqprkqZpSvVh-GFXLZ_ndL0guvPQ@mail.gmail.com>
2021-02-25 9:13 ` Need some help on "Input: elantech - add LEN2146 to SMBus blacklist for ThinkPad L13 Gen2" Nikolai Kostrigin
2021-02-25 9:38 ` Wolfram Sang [this message]
2021-03-03 10:11 ` Nikolai Kostrigin
2021-03-03 10:34 ` Wolfram Sang
2021-03-03 12:48 ` Nikolai Kostrigin
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=20210225093801.GA1008@ninjato \
--to=wsa@kernel.org \
--cc=benjamin.tissoires@redhat.com \
--cc=colin.king@canonical.com \
--cc=dmitry.torokhov@gmail.com \
--cc=gustavoars@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nickel@basealt.ru \
/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).