From: Even Xu <even.xu@intel.com>
To: bentiss@kernel.org, jikos@kernel.org
Cc: srinivas.pandruvada@linux.intel.com, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org, Even Xu <even.xu@intel.com>
Subject: [PATCH 0/2] HID: Intel-thc-hid: Support complete I2C bus configuration
Date: Mon, 27 Jul 2026 11:03:08 +0800 [thread overview]
Message-ID: <20260727030310.3850984-1-even.xu@intel.com> (raw)
The Intel THC QuickI2C driver currently configures only the target
address, bus speed, and SCL high and low periods. Additional timing
parameters supplied by firmware are not applied to the I2C sub-IP.
Introduce a common I2C configuration structure in the THC core and use
it to configure the target address, addressing mode, bus speed, SCL
timings, and SDA transmit and receive hold periods. Populate this
structure from the QuickI2C ACPI resources so that platform-specific
timings are restored during both initialization and resume.
Even Xu (2):
HID: Intel-thc-hid: Intel-thc: Refactor I2C bus configuration with
unified config structure
HID: Intel-thc-hid: Intel-quicki2c: Support full I2C BUS config
parameters
.../intel-quicki2c/pci-quicki2c.c | 46 +++++++------
.../intel-quicki2c/quicki2c-dev.h | 14 ++--
.../intel-thc-hid/intel-thc/intel-thc-dev.c | 69 ++++++++++++-------
.../intel-thc-hid/intel-thc/intel-thc-dev.h | 23 ++++++-
.../intel-thc-hid/intel-thc/intel-thc-hw.h | 3 +
5 files changed, 97 insertions(+), 58 deletions(-)
--
2.43.0
next reply other threads:[~2026-07-27 3:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 3:03 Even Xu [this message]
2026-07-27 3:03 ` [PATCH 1/2] HID: Intel-thc-hid: Intel-thc: Refactor I2C bus configuration with unified config structure Even Xu
2026-07-27 3:15 ` sashiko-bot
2026-07-27 3:03 ` [PATCH 2/2] HID: Intel-thc-hid: Intel-quicki2c: Support full I2C BUS config parameters Even Xu
2026-07-27 3:11 ` sashiko-bot
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=20260727030310.3850984-1-even.xu@intel.com \
--to=even.xu@intel.com \
--cc=bentiss@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivas.pandruvada@linux.intel.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