From: Marc Dietrich <marvin24@gmx.de>
To: linux-staging@lists.linux.dev
Cc: linux-tegra@vger.kernel.org, gregkh@linuxfoundation.org,
thierry.reding@gmail.com, dan.carpenter@linaro.org,
Marc Dietrich <marvin24@gmx.de>
Subject: [PATCH V2 0/4] staging: nvec: improve robustnes during initialization
Date: Sat, 6 Apr 2024 14:31:18 +0200 [thread overview]
Message-ID: <20240406123123.37148-1-marvin24@gmx.de> (raw)
This series against 6.9-rc2 improves robustnes of the keyboard and
touchpad initialization with the goal to eliminate the ugly delay
in the I2C client controller ISR.
Changes since initial submission:
- address comments from Dan regarding commit messages and function
documentation
- address comments from Thierry by introducing responseless sync writes
Marc Dietrich (5):
staging: nvec: add ability to ignore EC responses in sync writes
staging: nvec: make keyboard init synchronous
staging: nvec: make touchpad init synchronous
staging: nvec: make i2c controller register writes robust
staging: nvec: update TODO
drivers/staging/nvec/TODO | 1 -
drivers/staging/nvec/nvec.c | 50 ++++++++++++++++++++-------------
drivers/staging/nvec/nvec_kbd.c | 9 +++---
drivers/staging/nvec/nvec_ps2.c | 31 +++++++++++++-------
4 files changed, 57 insertions(+), 34 deletions(-)
--
2.43.0
next reply other threads:[~2024-04-06 12:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-06 12:31 Marc Dietrich [this message]
2024-04-06 12:31 ` [PATCH 1/5] staging: nvec: add ability to ignore EC responses in sync writes Marc Dietrich
2024-04-06 12:31 ` [PATCH 2/5] staging: nvec: make keyboard init synchronous Marc Dietrich
2024-04-06 12:31 ` [PATCH 3/5] staging: nvec: make touchpad " Marc Dietrich
2024-04-06 12:31 ` [PATCH 4/5] staging: nvec: make i2c controller register writes robust Marc Dietrich
2024-04-11 12:00 ` Greg KH
2024-04-14 15:09 ` [PATCH V2 " Marc Dietrich
2024-04-15 6:07 ` Dan Carpenter
2024-04-06 12:31 ` [PATCH 5/5] staging: nvec: update TODO Marc Dietrich
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=20240406123123.37148-1-marvin24@gmx.de \
--to=marvin24@gmx.de \
--cc=dan.carpenter@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.com \
/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