From: Matthew Garrett <mjg59@srcf.ucam.org>
To: "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>,
"Limonciello, Mario" <Mario.Limonciello@dell.com>
Subject: Re: [PATCH] platform/x86: dell-privacy: Add support for new privacy driver
Date: Wed, 11 Nov 2020 07:24:56 +0000 [thread overview]
Message-ID: <20201111072456.tkwdzuq2wa7zvbod@srcf.ucam.org> (raw)
In-Reply-To: <SJ0PR19MB4528E93631DA5FD8BE1D6E8D84E80@SJ0PR19MB4528.namprd19.prod.outlook.com>
On Wed, Nov 11, 2020 at 07:21:07AM +0000, Yuan, Perry wrote:
> > > + status = acpi_evaluate_object(NULL, ACPI_PRIVACY_EC_ACK, NULL,
> > NULL);
> > > + if (ACPI_FAILURE(status)) {
> > > + dev_err(led_cdev->dev, "Error setting privacy audio EC ack
> > value: %d\n",status);
> > > + return -EIO;
> > > + }
> > > + return 0;
> > > +}
> >
> > What's actually being set here? You don't seem to be passing any arguments.
>
> Yes, it is a EC ack notification without any arguments needed.
I'm confused why it's being exposed as an LED device in that case -
there's an expectation that this is something that actually controls a
real LED, which means responding to state. Are you able to share the
acpidump of a machine with this device?
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2020-11-11 7:25 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 [this message]
2020-11-11 14:30 ` Limonciello, Mario
2020-11-12 15:06 ` Enrico Weigelt, metux IT consult
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=20201111072456.tkwdzuq2wa7zvbod@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--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=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).