From: Michael Zaidman <michael.zaidman@gmail.com>
To: jikos@kernel.org, benjamin.tissoires@redhat.com, wsa@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
linux-i2c@vger.kernel.org, champagne.guillaume.c@gmail.com,
mathieu.gallichand@sonatest.com,
Michael Zaidman <michael.zaidman@gmail.com>
Subject: [PATCH v1 0/5] HID: ft260: fixes and performance improvements
Date: Wed, 25 May 2022 10:47:52 +0300 [thread overview]
Message-ID: <20220525074757.7519-1-michael.zaidman@gmail.com> (raw)
This patchset contains fixes and performance improvements to the
hid-ft260 driver posted for review and feedback on the GitHub
https://github.com/MichaelZaidman/hid-ft260 about three months ago.
Michael Zaidman (5):
HID: ft260: ft260_xfer_status routine cleanup
HID: ft260: improve i2c write performance
HID: ft260: support i2c writes larger than HID report size
HID: ft260: support i2c reads greater than HID report size
HID: ft260: improve i2c large reads performance
drivers/hid/hid-ft260.c | 230 +++++++++++++++++++++-------------------
1 file changed, 120 insertions(+), 110 deletions(-)
--
2.25.1
next reply other threads:[~2022-05-25 7:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 7:47 Michael Zaidman [this message]
2022-05-25 7:47 ` [PATCH v1 1/5] HID: ft260: ft260_xfer_status routine cleanup Michael Zaidman
2022-05-25 7:47 ` [PATCH v1 2/5] HID: ft260: improve i2c write performance Michael Zaidman
2022-05-25 7:47 ` [PATCH v1 3/5] HID: ft260: support i2c writes larger than HID report size Michael Zaidman
2022-05-25 15:44 ` Guillaume Champagne
2022-05-25 19:42 ` Michael Zaidman
2022-05-25 20:33 ` Guillaume Champagne
2022-05-25 7:47 ` [PATCH v1 4/5] HID: ft260: support i2c reads greater " Michael Zaidman
2022-05-25 7:47 ` [PATCH v1 5/5] HID: ft260: improve i2c large reads performance Michael Zaidman
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=20220525074757.7519-1-michael.zaidman@gmail.com \
--to=michael.zaidman@gmail.com \
--cc=benjamin.tissoires@redhat.com \
--cc=champagne.guillaume.c@gmail.com \
--cc=jikos@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.gallichand@sonatest.com \
--cc=wsa@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.