From: Werner Sembach <wse@tuxedocomputers.com>
To: W_Armin@gmx.de, hansg@kernel.org, ilpo.jarvinen@linux.intel.com
Cc: platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org,
Werner Sembach <wse@tuxedocomputers.com>
Subject: [RFC PATCH 0/2] platform/x86: uniwill-laptop: Introduce device descriptor system
Date: Tue, 25 Nov 2025 14:49:10 +0100 [thread overview]
Message-ID: <20251125135729.487837-1-wse@tuxedocomputers.com> (raw)
The first patch of this RFC is based on a PoC by Armin and extended the be able
to modify feature bits based on readouts from the EC Memory.
The 2nd patch is a new feature that requires such a modification.
Armin what do you think? Is this a clean approach? Technically the feature bits
can be modified arbitrarily, but it should only ever be accessed by the slightly
modified getter method, so the risk should be very minimal.
I wonder if the static device_descriptor variable can somehow be skipped, but it
doesn't bother to have it there either IMHO.
Armin Wolf (1):
platform/x86: uniwill-laptop: Introduce device descriptor system
Werner Sembach (1):
platform/x86/uniwill: Implement cTGP setting
drivers/platform/x86/uniwill/uniwill-acpi.c | 269 +++++++++++++++++---
1 file changed, 240 insertions(+), 29 deletions(-)
--
2.43.0
next reply other threads:[~2025-11-25 13:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 13:49 Werner Sembach [this message]
2025-11-25 13:49 ` [RFC PATCH 1/2] " Werner Sembach
2025-11-25 20:18 ` Armin Wolf
2025-11-26 12:14 ` Werner Sembach
2025-11-25 13:49 ` [RFC PATCH 2/2] platform/x86/uniwill: Implement cTGP setting Werner Sembach
2025-11-25 20:31 ` Armin Wolf
2025-11-26 12:23 ` Werner Sembach
2025-11-26 19:33 ` Armin Wolf
2025-11-26 22:59 ` Werner Sembach
2025-12-04 13:40 [RFC PATCH 0/2] platform/x86: uniwill-laptop: Introduce device descriptor system Werner Sembach
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=20251125135729.487837-1-wse@tuxedocomputers.com \
--to=wse@tuxedocomputers.com \
--cc=W_Armin@gmx.de \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.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®