From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: "Sebastian Reichel" <sre@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Hans de Goede" <hansg@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Bryan O'Donoghue" <bryan.odonoghue@linaro.org>,
"Bjorn Andersson" <andersson@kernel.org>,
"Konrad Dybcio" <konradybcio@kernel.org>,
"Mark Pearson" <mpearson-lenovo@squebb.ca>
Cc: "Derek J. Clark" <derekjohn.clark@gmail.com>,
Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
Neil Armstrong <neil.armstrong@linaro.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v3 2/3] platform: arm64: thinkpad-t14s-ec: new driver
Date: Mon, 8 Sep 2025 09:28:12 +0200 [thread overview]
Message-ID: <f16a858d-fb41-4cc9-a138-7bfe5ee2800f@oss.qualcomm.com> (raw)
In-Reply-To: <20250906-thinkpad-t14s-ec-v3-2-3ce6ec21ae89@collabora.com>
On 9/6/25 3:12 AM, Sebastian Reichel wrote:
> Introduce EC driver for the ThinkPad T14s Gen6 Snapdragon, which is in
> theory compatible with ThinkPad ACPI. On Linux the system is booted with
> device tree, which is not supported by the ThinkPad ACPI driver
> (drivers/platform/x86/lenovo/thinkpad_acpi.c). Also most of the hardware
> compatibility is handled via ACPI tables, which are obviously not used
> when booting via device tree. Thus adding DT compatibility to the
> existing driver is not worth it as there is almost no code sharing.
[...]
couple nits, feel free to ignore
> +#define T14S_EC_EVT_NONE 0x00
> +#define T14S_EC_EVT_KEY_FN_4 0x13
> +#define T14S_EC_EVT_KEY_FN_F7 0x16
> +#define T14S_EC_EVT_KEY_FN_SPACE 0x1F
> +#define T14S_EC_EVT_KEY_TP_DOUBLE_TAP 0x20
> +#define T14S_EC_EVT_AC_CONNECTED 0x26
> +#define T14S_EC_EVT_AC_DISCONNECTED 0x27
> +#define T14S_EC_EVT_KEY_POWER 0x28
> +#define T14S_EC_EVT_LID_OPEN 0x2A
> +#define T14S_EC_EVT_LID_CLOSED 0x2B
> +#define T14S_EC_EVT_KEY_FN_F12 0x62
> +#define T14S_EC_EVT_KEY_FN_TAB 0x63
> +#define T14S_EC_EVT_KEY_FN_F8 0x64
> +#define T14S_EC_EVT_KEY_FN_F10 0x65
> +#define T14S_EC_EVT_KEY_FN_F4 0x6A
> +#define T14S_EC_EVT_KEY_FN_D 0x6B
> +#define T14S_EC_EVT_KEY_FN_T 0x6C
> +#define T14S_EC_EVT_KEY_FN_H 0x6D
> +#define T14S_EC_EVT_KEY_FN_M 0x6E
> +#define T14S_EC_EVT_KEY_FN_L 0x6F
> +#define T14S_EC_EVT_KEY_FN_RIGHT_SHIFT 0x71
> +#define T14S_EC_EVT_KEY_FN_ESC 0x74
> +#define T14S_EC_EVT_KEY_FN_N 0x79
> +#define T14S_EC_EVT_KEY_FN_F11 0x7A
> +#define T14S_EC_EVT_KEY_FN_G 0x7E
Please use lowercase hex consistently across the file
[...]
> +enum thinkpad_t14s_ec_led_status_t {
> + T14S_EC_LED_OFF = 0x00,
> + T14S_EC_LED_ON = 0x80,
> + T14S_EC_LED_BLINK = 0xc0,
These conveniently translate to: BIT(7) and BIT(6)|BIT(7), meaning
BIT(7) could mean "ON" and BIT(6) could mean "pulse" (can you pulse
a disabled LED? arcane secrets..)
[...]
> + if (brightness == LED_OFF)
> + new_state = T14S_EC_LED_OFF;
> + else if (led->cache != T14S_EC_LED_BLINK)
==s are easier to logically follow than !=, but this is totally
potayto/potahto
[...]
> +static int thinkpad_t14s_led_blink_set(struct led_classdev *led_cdev,
> + unsigned long *delay_on,
> + unsigned long *delay_off)
> +{
> + struct thinkpad_t14s_ec_led_classdev *led = container_of(led_cdev,
> + struct thinkpad_t14s_ec_led_classdev, led_classdev);
> +
> + if (*delay_on == 0 && *delay_off == 0) {
> + /* We can choose the blink rate */
"can't"?
Needless to say, amazing work on piecing all this together, Sebastian!
Konrad
next prev parent reply other threads:[~2025-09-08 7:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-06 1:12 [PATCH v3 0/3] " Sebastian Reichel
2025-09-06 1:12 ` [PATCH v3 1/3] dt-bindings: platform: Add Lenovo Thinkpad T14s EC Sebastian Reichel
2025-09-06 1:12 ` [PATCH v3 2/3] platform: arm64: thinkpad-t14s-ec: new driver Sebastian Reichel
2025-09-08 7:28 ` Konrad Dybcio [this message]
2025-09-08 21:59 ` Sebastian Reichel
2025-09-06 1:12 ` [PATCH v3 3/3] arm64: dts: qcom: x1e80100-t14s: add EC Sebastian Reichel
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=f16a858d-fb41-4cc9-a138-7bfe5ee2800f@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=derekjohn.clark@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=hansg@kernel.org \
--cc=hmh@hmh.eng.br \
--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=mpearson-lenovo@squebb.ca \
--cc=neil.armstrong@linaro.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sre@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 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®