From: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
To: "Limonciello, Mario" <Mario.Limonciello@dell.com>,
Matthew Garrett <mjg59@srcf.ucam.org>,
"Yuan, Perry" <Perry.Yuan@dell.com>
Cc: "hdegoede@redhat.com" <hdegoede@redhat.com>,
"mgross@linux.intel.com" <mgross@linux.intel.com>,
"pali@kernel.org" <pali@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>
Subject: Re: [PATCH] platform/x86: dell-privacy: Add support for new privacy driver
Date: Thu, 12 Nov 2020 16:06:13 +0100 [thread overview]
Message-ID: <e8e06aca-c3f1-d833-c766-01f05dfa0f37@metux.net> (raw)
In-Reply-To: <DM6PR19MB2636956DB58B0E4ECAD43549FAE80@DM6PR19MB2636.namprd19.prod.outlook.com>
On 11.11.20 15:30, Limonciello, Mario wrote:
Hi,
> Pressing the mute key activates a time delayed circuit to physically cut
> off the mute. The LED is in the same circuit, so it reflects the true
> state of the HW mute. The reason for the EC "ack" is so that software
> can first invoke a SW mute before the HW circuit is cut off. Without SW
> cutting this off first does not affect the time delayed muting or status
> of the LED but there is a possibility of a "popping" noise leading to a
> poor user experience.
how long is that timeout ?
> Exposing as an LED device allows the codec drivers notification path to
> EC ACK to work.
Which driver exactly ? Who's gonna access this LED ?
--mtx
--
---
Hinweis: unverschlüsselte E-Mails können leicht abgehört und manipuliert
werden ! Für eine vertrauliche Kommunikation senden Sie bitte ihren
GPG/PGP-Schlüssel zu.
---
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@metux.net -- +49-151-27565287
next prev parent reply other threads:[~2020-11-12 15:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 12:55 [PATCH] platform/x86: dell-privacy: Add support for new privacy driver Perry Yuan
2020-11-03 16:22 ` kernel test robot
2020-11-03 16:50 ` kernel test robot
2020-11-03 19:14 ` Barnabás Pőcze
2020-11-04 1:49 ` Matthew Garrett
2020-11-11 7:21 ` Yuan, Perry
2020-11-11 7:24 ` Matthew Garrett
2020-11-11 14:30 ` Limonciello, Mario
2020-11-12 15:06 ` Enrico Weigelt, metux IT consult [this message]
2020-11-12 15:31 ` Limonciello, Mario
2020-11-12 15:55 ` Hans de Goede
2020-11-12 15:57 ` Limonciello, Mario
2020-11-04 6:43 ` kernel test robot
2020-11-09 11:16 ` Hans de Goede
2020-11-11 7:24 ` Yuan, Perry
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=e8e06aca-c3f1-d833-c766-01f05dfa0f37@metux.net \
--to=lkml@metux.net \
--cc=Mario.Limonciello@dell.com \
--cc=Perry.Yuan@dell.com \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgross@linux.intel.com \
--cc=mjg59@srcf.ucam.org \
--cc=pali@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;
as well as URLs for NNTP newsgroup(s).