From: Ayman Bagabas <ayman.bagabas@gmail.com>
To: Darren Hart <dvhart@infradead.org>,
Andy Shevchenko <andy@infradead.org>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Kailang Yang <kailang@realtek.com>,
Jian-Hong Pan <jian-hong@endlessm.com>,
Daniel Drake <drake@endlessm.com>, Chris Chiu <chiu@endlessm.com>,
Hui Wang <hui.wang@canonical.com>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org
Cc: ayman.bagabas@gmail.com
Subject: [PATCH v1 0/2] Huawei WMI laptop extras driver
Date: Mon, 13 May 2019 16:30:04 -0400 [thread overview]
Message-ID: <20190513203009.28686-1-ayman.bagabas@gmail.com> (raw)
Using the WMI BIOS management interface found on Huawei laptops, extra features
such as micmute LED, charging thresholds, and fn-lock can be controlled.
A platform driver has been implemented along with the existing WMI driver. The
platform driver controls the LED, battery charging thresholds, and fn-lock.
We enable sound micmute hooks to platform driver on Huawei laptops to get the
LED to work.
Ayman Bagabas (2):
platform/x86: Huawei WMI laptop extras driver update
sound: Enable micmute led for Huawei laptops
drivers/platform/x86/Kconfig | 8 +-
drivers/platform/x86/huawei-wmi.c | 578 +++++++++++++++++++++++++-----
sound/pci/hda/patch_realtek.c | 9 +-
3 files changed, 504 insertions(+), 91 deletions(-)
--
2.20.1
next reply other threads:[~2019-05-13 20:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 20:30 Ayman Bagabas [this message]
2019-05-13 20:30 ` [PATCH v1 1/2] platform/x86: Huawei WMI laptop extras driver update Ayman Bagabas
2019-05-15 13:10 ` Takashi Iwai
2019-05-15 21:36 ` ayman.bagabas
2019-05-13 20:30 ` [PATCH v1 2/2] sound: Enable micmute led for Huawei laptops Ayman Bagabas
2019-05-15 13:11 ` Takashi Iwai
2019-05-15 20:54 ` ayman.bagabas
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=20190513203009.28686-1-ayman.bagabas@gmail.com \
--to=ayman.bagabas@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=andy@infradead.org \
--cc=chiu@endlessm.com \
--cc=drake@endlessm.com \
--cc=dvhart@infradead.org \
--cc=hui.wang@canonical.com \
--cc=jian-hong@endlessm.com \
--cc=kailang@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=platform-driver-x86@vger.kernel.org \
--cc=tiwai@suse.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;
as well as URLs for NNTP newsgroup(s).