From: Werner Sembach <wse@tuxedocomputers.com>
To: hdegoede@redhat.com, ilpo.jarvinen@linux.intel.com, bentiss@kernel.org
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org,
Werner Sembach <wse@tuxedocomputers.com>
Subject: [PATCH v8 0/1] platform/x86/tuxedo: Add virtual LampArray for TUXEDO NB04 devices
Date: Wed, 23 Apr 2025 17:33:09 +0200 [thread overview]
Message-ID: <20250423153804.64395-1-wse@tuxedocomputers.com> (raw)
@Ilpos you can ignore my small question from my last e-mail. The spec file
of the firmware wants the struct to be zeroed (albeit it does also work if
not) so I implemented it like that.
v2: - Integrated Armins feedback and fixed kernel test robot warnings.
v3: - Fixed borked subject line of v2.
v4: - Remove unrequired WMI mutex.
- Move device checking from probe to init.
- Fix device checking working exactly reverse as it should.
- Fix null pointer dereference because,
hdev->driver_data != hdev->dev.driver_data.
v5: - Move everything to subfolder nb04 in preparation for the eventual
upstreaming of other tuxedo-driver parts.
- Integrated Ilpos coding style feedback.
- Use dev_set/get_drvdata() based on Armins feedback.
v6: - Integrated more of Ilpo coding style feedback from a different LKML
patch-thread (less files, local functions prefixed with a short
string).
v7: - Integrated more of Ilpos feedback e.g.:
- Use cleanup.h
- replace some if cases with a pointer in driver_data
- coding style oversights
v8: - Integrated more of Ilpos feedback
- Typo fix spotted by Alok
Werner Sembach (1):
platform/x86/tuxedo: Add virtual LampArray for TUXEDO NB04 devices
MAINTAINERS | 6 +
drivers/platform/x86/Kconfig | 2 +
drivers/platform/x86/Makefile | 3 +
drivers/platform/x86/tuxedo/Kconfig | 8 +
drivers/platform/x86/tuxedo/Makefile | 8 +
drivers/platform/x86/tuxedo/nb04/Kconfig | 15 +
drivers/platform/x86/tuxedo/nb04/Makefile | 10 +
drivers/platform/x86/tuxedo/nb04/wmi_ab.c | 916 ++++++++++++++++++++
drivers/platform/x86/tuxedo/nb04/wmi_util.c | 91 ++
drivers/platform/x86/tuxedo/nb04/wmi_util.h | 109 +++
10 files changed, 1168 insertions(+)
create mode 100644 drivers/platform/x86/tuxedo/Kconfig
create mode 100644 drivers/platform/x86/tuxedo/Makefile
create mode 100644 drivers/platform/x86/tuxedo/nb04/Kconfig
create mode 100644 drivers/platform/x86/tuxedo/nb04/Makefile
create mode 100644 drivers/platform/x86/tuxedo/nb04/wmi_ab.c
create mode 100644 drivers/platform/x86/tuxedo/nb04/wmi_util.c
create mode 100644 drivers/platform/x86/tuxedo/nb04/wmi_util.h
--
2.43.0
next reply other threads:[~2025-04-23 15:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 15:33 Werner Sembach [this message]
2025-04-23 15:33 ` [PATCH v8 1/1] platform/x86/tuxedo: Add virtual LampArray for TUXEDO NB04 devices Werner Sembach
2025-04-24 13:26 ` Ilpo Järvinen
2025-04-24 18:39 ` Werner Sembach
2025-04-25 11:32 ` Ilpo Järvinen
2025-04-25 16:30 ` Werner Sembach
2025-04-26 8:17 ` [PATCH v8 0/1] " Pavel Machek
2025-05-05 7:23 ` 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=20250423153804.64395-1-wse@tuxedocomputers.com \
--to=wse@tuxedocomputers.com \
--cc=bentiss@kernel.org \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-input@vger.kernel.org \
--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