mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alex Robinson <alex@ironrobin.net>
To: "Hans de Goede" <hansg@kernel.org>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Steev Klimaszewski <threeway@gmail.com>,
	platform-driver-x86@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH v6 0/3] Lenovo ThinkPad X13s embedded controller support
Date: Sat, 10 Oct 2026 14:55:36 +0000	[thread overview]
Message-ID: <20261010145519.8370-1-alex@ironrobin.net> (raw)

Add Device Tree support for the ThinkPad X13s embedded controller,
providing keyboard-backlight control and firmware-driven brightness
notifications. Its event, backlight and power-management interfaces
differ from the T14s EC and require a separate driver.

EC wakeup remains disabled by default because lid closure can trigger
an unwanted wakeup and no selective event mask is known. Other EC event
mappings remain outside the scope of this series.

This follows earlier X13s EC work by Konrad Dybcio and Steev Klimaszewski.
Development was assisted by an LLM, including analysis of the X13s ACPI
DSDT and review of the implementation.

Changes in v6:
- Retry failed low-power entry and exit writes once, matching the X13s
  DSDT's two-attempt ECWS(..., 3) loop without repeating GPIO transitions
  or changing ordinary EC writes.
- Include linux/irq.h explicitly for irq_get_trigger_type() and
  IRQ_TYPE_EDGE_FALLING, addressing the reported s390 build errors.
- Carry Krzysztof Kozlowski's Reviewed-by from v3; the binding is unchanged.

Changes in v5:
- Replace the private suspended/access-blocked flag and deferred-event
  handling with IRQ quiescing and LED class suspend/resume helpers.
- Flush pending LED brightness restoration before re-enabling the EC
  event IRQ, so pending lid events are handled afterwards.
- Preserve the EC lid-restore brightness during PM blanking/restoration.
- Update the LED brightness cache on lid-open restoration without a
  hardware-change notification, avoiding a spurious backlight OSD.
  Retain notifications for firmware-driven changes such as Fn+Space.
- Include dev_printk.h directly for device logging helpers.
- Leave the binding and DTS unchanged from v4.

Changes in v4:
- Set GPIO103 bias-pull-up explicitly, based on its firmware-inherited
  configuration measured at pinctrl probe before Linux claimed or
  configured the pin. CTL offset 0x67000 read 0x00000003 (pull field 3).
  The temporary measurement instrumentation is not included.
- Remove output-high from the GPIO176 pinctrl state. The driver already
  requests GPIOD_OUT_HIGH at probe and controls the line during sleep.
- Restore the suspend brightness snapshot only if it was successfully
  captured during that suspend, avoiding restoration of a stale value.
- Use FIELD_MODIFY(), validate brightness against the LED maximum, and
  simplify transfer error handling and selected mutex-protected paths.
- Include linux/ratelimit.h explicitly and adjust conditional formatting.
- Shorten commit messages to focus on rationale rather than the diff.

Changes in v3:
- Disable EC wakeup by default without disabling runtime IRQ handling.
- Retain wakeup-source as a description of hardware capability.
- Remove the Kconfig help text's claim of wake support.

Changes in v2:
- Make backlight snapshots and EC power-management operations best-effort.
- Save firmware- and software-selected brightness in the EC and restore
  the EC-saved brightness on lid open.
- Process deferred events after the normal resume brightness restore.
- Add QUP8 pin configuration verified on hardware and fix DT node ordering.

Build and software testing (revised v6):
- Rebuilt the revised power-state retry code as an ARM64 driver object
  with W=1 and GCC 16.2.1, without warnings.
- Passed 15 mocked tests using the actual write helper and PM function
  bodies, covering success, retry-success, retry-failure, and short writes.
  Verified attempt counts, error results, GPIO ordering, and requested
  10 ms delays with AddressSanitizer and UndefinedBehaviorSanitizer
  enabled. These tests verify software behavior, not physical timing.
- Applied all three patches to clean Linux v7.3-rc4, without the separate
  PCI workaround, using both git apply and patch -Np1 --fuzz=0. Both
  produced identical source files, with no offsets or fuzz.
- Checkpatch reported no errors; its only warnings were the generic
  MAINTAINERS reminders (the series includes an entry).

Earlier validation of unchanged DT content:
- Before the retry change, compiled the ARM64 driver object and X13s DTB
  with W=1 using GCC 16.2.1 and the package's config.aarch64 after
  olddefconfig. The driver compiled without warnings; the DTB build
  reported four avoid_unnecessary_addr_size warnings in sc8280xp.dtsi
  DSI nodes outside this series.
- Before the retry change, passed dt_binding_check for the unchanged
  lenovo,thinkpad-x13s-ec.yaml binding and its example, and targeted
  validation of the built X13s DTB against that binding.

Hardware testing on a Lenovo ThinkPad X13s booted with revised v6,
including the power-state retry helper:
- Passed manual s2idle suspend/resume.
- Passed lid-close s2idle suspend and lid-open wake.
- Keyboard-backlight level 2 was restored correctly after both cycles.
- Sysfs brightness reported 2 after manual resume.
- No unexpected keyboard-backlight OSD appeared.
- Kernel logs confirmed suspend/resume cycles at 09:29:19-09:29:36 and
  09:35:07-09:35:29.
- No EC, I2C, or GPIO errors appeared in the filtered logs.

Additional hardware testing before the power-state retry change verified
keyboard-backlight levels 0, 1, and 2, including physical brightness,
and Fn+Space firmware-driven changes with correct userspace OSD
notifications and brightness levels.

Earlier series:
https://lore.kernel.org/all/20260925215358.33417-1-alex@ironrobin.net/

Alex Robinson (3):
  dt-bindings: embedded-controller: Add Lenovo ThinkPad X13s EC
  platform: arm64: Add Lenovo ThinkPad X13s EC driver
  arm64: dts: qcom: sc8280xp-x13s: Add embedded controller

base-commit: 93f51579e7df248780214094418f205253383cc5


             reply	other threads:[~2026-10-10 14:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-10 14:55 Alex Robinson [this message]
2026-10-10 14:55 ` [PATCH v6 1/3] dt-bindings: embedded-controller: Add Lenovo ThinkPad X13s EC Alex Robinson
2026-10-10 14:55 ` [PATCH v6 2/3] platform: arm64: Add Lenovo ThinkPad X13s EC driver Alex Robinson
2026-10-10 14:55 ` [PATCH v6 3/3] arm64: dts: qcom: sc8280xp-x13s: Add embedded controller Alex Robinson

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=20261010145519.8370-1-alex@ironrobin.net \
    --to=alex@ironrobin.net \
    --cc=andersson@kernel.org \
    --cc=bryan.odonoghue@linaro.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=hansg@kernel.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=threeway@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

all inboxes | Powered by JetHome®