From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Perry Yuan <Perry.Yuan@dell.com>
Cc: hdegoede@redhat.com, mgross@linux.intel.com, pali@kernel.org,
linux-kernel@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, 4 Nov 2020 01:49:15 +0000 [thread overview]
Message-ID: <20201104014915.45tbmnrqvccbrd2k@srcf.ucam.org> (raw)
In-Reply-To: <20201103125542.8572-1-Perry_Yuan@Dell.com>
On Tue, Nov 03, 2020 at 04:55:42AM -0800, Perry Yuan wrote:
> +#define PRIVACY_PlATFORM_NAME "dell-privacy-acpi"
> +#define ACPI_PRIVACY_DEVICE "\\_SB.PC00.LPCB.ECDV"
This looks like the EC rather than a privacy device? If so, you probably
want to collaborate with the EC driver to obtain the handle rather than
depending on the path, unless it's guaranteed that this path will never
change.
> +static int micmute_led_set(struct led_classdev *led_cdev,
> + enum led_brightness brightness)
> +{
> + acpi_status status;
> +
> + 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.
> +static const struct acpi_device_id privacy_acpi_device_ids[] = {
> + {"PNP0C09", 0},
Oooh no please don't do this - you'll trigger autoloading on everything
that exposes a PNP0C09 device.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2020-11-04 2:08 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 [this message]
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
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=20201104014915.45tbmnrqvccbrd2k@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).