<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/platform/x86/lenovo, branch linux-rolling-stable</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-rolling-stable</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-rolling-stable'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2026-03-12T11:09:41Z</updated>
<entry>
<title>platform/x86: thinkpad_acpi: Fix errors reading battery thresholds</title>
<updated>2026-03-12T11:09:41Z</updated>
<author>
<name>Jonathan Teh</name>
</author>
<published>2026-02-16T01:01:29Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=72051b64f2e132948e9177c14f373da95cb2f73e'/>
<id>urn:sha1:72051b64f2e132948e9177c14f373da95cb2f73e</id>
<content type='text'>
[ Upstream commit 53e977b1d50c46f2c4ec3865cd13a822f58ad3cd ]

Check whether the battery supports the relevant charge threshold before
reading the value to silence these errors:

thinkpad_acpi: acpi_evalf(BCTG, dd, ...) failed: AE_NOT_FOUND
ACPI: \_SB_.PCI0.LPC_.EC__.HKEY: BCTG: evaluate failed
thinkpad_acpi: acpi_evalf(BCSG, dd, ...) failed: AE_NOT_FOUND
ACPI: \_SB_.PCI0.LPC_.EC__.HKEY: BCSG: evaluate failed

when reading the charge thresholds via sysfs on platforms that do not
support them such as the ThinkPad T400.

Fixes: 2801b9683f74 ("thinkpad_acpi: Add support for battery thresholds")
Closes: https://bugzilla.kernel.org/show_bug.cgi?id=202619
Signed-off-by: Jonathan Teh &lt;jonathan.teh@outlook.com&gt;
Reviewed-by: Mark Pearson &lt;mpearson-lenovo@squebb.ca&gt;
Link: https://patch.msgid.link/MI0P293MB01967B206E1CA6F337EBFB12926CA@MI0P293MB0196.ITAP293.PROD.OUTLOOK.COM
Reviewed-by: Ilpo Järvinen &lt;ilpo.jarvinen@linux.intel.com&gt;
Signed-off-by: Ilpo Järvinen &lt;ilpo.jarvinen@linux.intel.com&gt;
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</content>
</entry>
<entry>
<title>platform/x86: ideapad-laptop: Reassign KEY_CUT to KEY_SELECTIVE_SCREENSHOT</title>
<updated>2025-12-29T11:56:14Z</updated>
<author>
<name>Tomáš Hnyk</name>
</author>
<published>2025-12-26T20:34:54Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=cbf3dc32609b9703b87fbd444c271821664478c6'/>
<id>urn:sha1:cbf3dc32609b9703b87fbd444c271821664478c6</id>
<content type='text'>
As per Lenovo documentation, Fn+Print-Screen should "Open the Snipping
tool" which corresponds to KEY_SELECTIVE_SCREENSHOT (keycode 0x27a). It
is currently assigned to KEY_CUT because keycodes under 248 were
preferred due to X11 limitations.

Reassign Fn+Print-Screen from KEY_CUT to KEY_SELECTIVE_SCREENSHOT.

Closes: https://bugzilla.kernel.org/show_bug.cgi?id=220566
Signed-off-by: Tomáš Hnyk &lt;tomashnyk@gmail.com&gt;
Link: https://patch.msgid.link/20251226203454.405520-1-tomashnyk@gmail.com
Reviewed-by: Ilpo Järvinen &lt;ilpo.jarvinen@linux.intel.com&gt;
Signed-off-by: Ilpo Järvinen &lt;ilpo.jarvinen@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>platform/x86: think-lmi: Add WMI certificate thumbprint support for ThinkCenter</title>
<updated>2025-12-22T14:12:41Z</updated>
<author>
<name>Mark Pearson</name>
</author>
<published>2025-11-27T20:29:48Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=05126063605f26f9228c69b1ff232ac6e78f72ab'/>
<id>urn:sha1:05126063605f26f9228c69b1ff232ac6e78f72ab</id>
<content type='text'>
The ThinkCenter team are adding WMI certificate thumbprint support.

Updating the driver to enable it. They are using the same GUID as
Thinkpad/ThinkStation.
Tested on M75q Gen 5.

Signed-off-by: Mark Pearson &lt;mpearson-lenovo@squebb.ca&gt;
Link: https://patch.msgid.link/20251127202959.399040-1-mpearson-lenovo@squebb.ca
Reviewed-by: Ilpo Järvinen &lt;ilpo.jarvinen@linux.intel.com&gt;
Signed-off-by: Ilpo Järvinen &lt;ilpo.jarvinen@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>platform/x86: wmi-gamezone: Add Legion Go 2 Quirks</title>
<updated>2025-11-28T10:03:27Z</updated>
<author>
<name>Derek J. Clark</name>
</author>
<published>2025-11-27T15:16:05Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=55715d7ad5e772d621c3201da3895f250591bce8'/>
<id>urn:sha1:55715d7ad5e772d621c3201da3895f250591bce8</id>
<content type='text'>
Add Legion Go 2 SKU's to the Extreme Mode quirks table.

Signed-off-by: Derek J. Clark &lt;derekjohn.clark@gmail.com&gt;
Reviewed-by: Armin Wolf &lt;W_Armin@gmx.de&gt;
Reviewed-by: Mark Pearson &lt;mpearson-lenovo@squebb.ca&gt;
Link: https://patch.msgid.link/20251127151605.1018026-4-derekjohn.clark@gmail.com
Reviewed-by: Ilpo Järvinen &lt;ilpo.jarvinen@linux.intel.com&gt;
Signed-off-by: Ilpo Järvinen &lt;ilpo.jarvinen@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>platform/x86: lenovo-wmi-gamezone Use max-power rather than balanced-performance</title>
<updated>2025-11-28T10:03:25Z</updated>
<author>
<name>Derek J. Clark</name>
</author>
<published>2025-11-27T15:16:04Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=8d0aef2b3a17e5ed3afc8c9a2e71f22ac41a799f'/>
<id>urn:sha1:8d0aef2b3a17e5ed3afc8c9a2e71f22ac41a799f</id>
<content type='text'>
When developing the gamezone WMI drivers, "extreme mode" was matched to
the performance platform profile and "performance" was matched to the
balanced-performance platform profile, but only if extreme mode was
fully supported; otherwise performance was matched to the "performance"
platform profile. This has led to quite a bit of confusion with users
not understanding why the LED color indicating the platform profile
doesn't match their expectations.

To solve this, replace the confusing convention by using the new
max-power profile to represent "extreme mode". While add it, update the
documentation to reflect the expected LED colors in each operating mode.

Signed-off-by: Derek J. Clark &lt;derekjohn.clark@gmail.com&gt;
Reviewed-by: Armin Wolf &lt;W_Armin@gmx.de&gt;
Reviewed-by: Mark Pearson &lt;mpearson-lenovo@squebb.ca&gt;
Link: https://patch.msgid.link/20251127151605.1018026-3-derekjohn.clark@gmail.com
Reviewed-by: Ilpo Järvinen &lt;ilpo.jarvinen@linux.intel.com&gt;
Signed-off-by: Ilpo Järvinen &lt;ilpo.jarvinen@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>platform/x86: ideapad-laptop: Add charge_types:Fast (Rapid Charge)</title>
<updated>2025-11-10T09:55:43Z</updated>
<author>
<name>Rong Zhang</name>
</author>
<published>2025-11-05T18:28:27Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=90430ea98f5585270bc185cee548154d239af8d7'/>
<id>urn:sha1:90430ea98f5585270bc185cee548154d239af8d7</id>
<content type='text'>
The GBMD/SBMC interface on recent devices supports Rapid Charge mode
(charge_types: Fast) in addition to Conservation Mode (charge_types:
Long_Life).

Query the GBMD interface on probe to determine if a device supports
Rapid Charge. If so, expose these two modes while carefully maintaining
their mutually exclusive state, which aligns with the behavior of
manufacturer utilities on Windows.

Signed-off-by: Rong Zhang &lt;i@rong.moe&gt;
Acked-by: Ike Panhc &lt;ikepanhc@gmail.com&gt;
Reviewed-by: Mark Pearson &lt;mpearson-lenovo@squebb.ca&gt;
Tested-By: Jelle van der Waa &lt;jelle@vdwaa.nl&gt;
Link: https://patch.msgid.link/20251105182832.104946-5-i@rong.moe
Reviewed-by: Ilpo Järvinen &lt;ilpo.jarvinen@linux.intel.com&gt;
Signed-off-by: Ilpo Järvinen &lt;ilpo.jarvinen@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>platform/x86: ideapad-laptop: Support multiple power_supply_ext definitions</title>
<updated>2025-11-10T09:55:41Z</updated>
<author>
<name>Rong Zhang</name>
</author>
<published>2025-11-05T18:28:26Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=5c54ece0476638f7c5fc655c655e721286a26bf1'/>
<id>urn:sha1:5c54ece0476638f7c5fc655c655e721286a26bf1</id>
<content type='text'>
Some recent devices supports more charge_types. To properly support
these device without breaking the existing ones, we need to define
multiple power_supply_ext for different GBMD/SBMC interface revisions.

No functional change intended.

Signed-off-by: Rong Zhang &lt;i@rong.moe&gt;
Link: https://patch.msgid.link/20251105182832.104946-4-i@rong.moe
Reviewed-by: Ilpo Järvinen &lt;ilpo.jarvinen@linux.intel.com&gt;
Signed-off-by: Ilpo Järvinen &lt;ilpo.jarvinen@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>platform/x86: ideapad-laptop: Protect GBMD/SBMC calls with mutex</title>
<updated>2025-11-10T09:55:39Z</updated>
<author>
<name>Rong Zhang</name>
</author>
<published>2025-11-05T18:28:25Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=85901a0d8591ecd756078e57be077f12a0ee78be'/>
<id>urn:sha1:85901a0d8591ecd756078e57be077f12a0ee78be</id>
<content type='text'>
The upcoming changes for Rapid Charge support require two consecutive
SBMC calls to switch charge_types. Hence, a mutex is required.

No functional change intended.

Signed-off-by: Rong Zhang &lt;i@rong.moe&gt;
Acked-by: Ike Panhc &lt;ikepanhc@gmail.com&gt;
Link: https://patch.msgid.link/20251105182832.104946-3-i@rong.moe
Reviewed-by: Ilpo Järvinen &lt;ilpo.jarvinen@linux.intel.com&gt;
Signed-off-by: Ilpo Järvinen &lt;ilpo.jarvinen@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>platform/x86: ideapad-laptop: Use str_on_off() helper</title>
<updated>2025-11-10T09:55:36Z</updated>
<author>
<name>Rong Zhang</name>
</author>
<published>2025-11-05T18:28:24Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=06c129cac01be45e458d37534d1a6ba753cf6f13'/>
<id>urn:sha1:06c129cac01be45e458d37534d1a6ba753cf6f13</id>
<content type='text'>
Use the str_on_off() helper instead of open-coding the same operation.
This improves code readability.

No functional change intended.

Suggested-by: kernel test robot &lt;lkp@intel.com&gt;
Suggested-by: Julia Lawall &lt;julia.lawall@inria.fr&gt;
Link: https://lore.kernel.org/r/202510311551.xjWbHTrm-lkp@intel.com/
Suggested-by: Ilpo Järvinen &lt;ilpo.jarvinen@linux.intel.com&gt;
Link: https://lore.kernel.org/r/2bae2ea7-2ef9-0cfa-0c2c-39a7043b2aa5@linux.intel.com/
Signed-off-by: Rong Zhang &lt;i@rong.moe&gt;
Link: https://patch.msgid.link/20251105182832.104946-2-i@rong.moe
Reviewed-by: Ilpo Järvinen &lt;ilpo.jarvinen@linux.intel.com&gt;
Signed-off-by: Ilpo Järvinen &lt;ilpo.jarvinen@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>platform/x86: x86-android-tablets: convert Yoga Tab2 fast charger to GPIO references</title>
<updated>2025-09-26T11:26:25Z</updated>
<author>
<name>Dmitry Torokhov</name>
</author>
<published>2025-09-20T20:07:02Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=27d3e7351eea6fe2e967ea6028143e04f5914f0d'/>
<id>urn:sha1:27d3e7351eea6fe2e967ea6028143e04f5914f0d</id>
<content type='text'>
Now that gpiolib supports software nodes to describe GPIOs, switch the
driver away from using GPIO lookup tables for the fast charger device
to using PROPERTY_ENTRY_GPIO().

Signed-off-by: Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;
Tested-by: Hans de Goede &lt;hansg@kernel.org&gt;
Reviewed-by: Hans de Goede &lt;hansg@kernel.org&gt;
Reviewed-by: Andy Shevchenko &lt;andy@kernel.org&gt;
Signed-off-by: Hans de Goede &lt;hansg@kernel.org&gt;
Link: https://patch.msgid.link/20250920200713.20193-10-hansg@kernel.org
Reviewed-by: Ilpo Järvinen &lt;ilpo.jarvinen@linux.intel.com&gt;
Signed-off-by: Ilpo Järvinen &lt;ilpo.jarvinen@linux.intel.com&gt;
</content>
</entry>
</feed>
