From: Darren Hart <dvhart@infradead.org>
To: Azael Avalos <coproscefalo@gmail.com>
Cc: Matthew Garrett <matthew.garrett@nebula.com>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/5] toshiba_acpi: Fix illumination not available on certain models
Date: Fri, 5 Sep 2014 19:35:37 -0700 [thread overview]
Message-ID: <20140906023537.GA11389@vmdeb7> (raw)
In-Reply-To: <1409937247-2525-3-git-send-email-coproscefalo@gmail.com>
On Fri, Sep 05, 2014 at 11:14:04AM -0600, Azael Avalos wrote:
> Some Toshiba models with illumination support set a different
> value on the returned codes, thus not allowing the illumination
> LED to be registered, where it should be.
>
> This patch removes a check from toshiba_illumination_available
> function to allow such models to register the illumination LED.
>
> Signed-off-by: Azael Avalos <coproscefalo@gmail.com>
> ---
> drivers/platform/x86/toshiba_acpi.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/platform/x86/toshiba_acpi.c b/drivers/platform/x86/toshiba_acpi.c
> index a149bc6..4803e7b 100644
> --- a/drivers/platform/x86/toshiba_acpi.c
> +++ b/drivers/platform/x86/toshiba_acpi.c
> @@ -436,7 +436,7 @@ static int toshiba_illumination_available(struct toshiba_acpi_dev *dev)
> if (ACPI_FAILURE(status) || out[0] == HCI_FAILURE) {
> pr_err("ACPI call to query Illumination support failed\n");
> return 0;
> - } else if (out[0] == HCI_NOT_SUPPORTED || out[1] != 1) {
> + } else if (out[0] == HCI_NOT_SUPPORTED) {
OK, but by eliminating the check, supposedly certain models which do not support
illumination but do not report it via out[0], but instead via out[1], will now
attempt to use illumination - correct?
The end result being user calls to an ACPI function which at best doesn't exist
and at worst.... does, but does something entirely different.
I admit the potential for a problem is slight, but is it possible to check
something explicit for support on the newer models rather than removing an
existing check?
--
Darren Hart
Intel Open Source Technology Center
next prev parent reply other threads:[~2014-09-06 2:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 17:14 [PATCH 0/5] toshiba_acpi: Various changes plus fixes Azael Avalos
2014-09-05 17:14 ` [PATCH 1/5] toshiba_acpi: Additional hotkey scancodes Azael Avalos
2014-09-09 0:12 ` Darren Hart
2014-09-05 17:14 ` [PATCH 2/5] toshiba_acpi: Fix illumination not available on certain models Azael Avalos
2014-09-06 2:35 ` Darren Hart [this message]
2014-09-06 4:49 ` Azael Avalos
2014-09-09 0:09 ` Darren Hart
2014-09-05 17:14 ` [PATCH 3/5] toshiba_acpi: Add accelerometer input polled device Azael Avalos
2014-09-06 2:42 ` Darren Hart
2014-09-06 5:04 ` Azael Avalos
2014-09-09 0:04 ` Darren Hart
2014-09-09 1:35 ` Greg Kroah-Hartman
2014-09-10 3:35 ` Darren Hart
2014-09-10 15:28 ` Azael Avalos
2014-09-10 16:08 ` Greg Kroah-Hartman
2014-09-17 16:36 ` Jonathan Cameron
2014-09-17 18:38 ` Darren Hart
2014-09-05 17:14 ` [PATCH 4/5] toshiba_acpi: Support new keyboard backlight type Azael Avalos
2014-09-10 4:11 ` Darren Hart
2014-09-10 16:52 ` Azael Avalos
2014-09-10 18:34 ` Darren Hart
2014-09-05 17:14 ` [PATCH 5/5] toshiba_acpi: Change touchpad store to check for invalid values Azael Avalos
2014-09-10 4:17 ` Darren Hart
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=20140906023537.GA11389@vmdeb7 \
--to=dvhart@infradead.org \
--cc=coproscefalo@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.garrett@nebula.com \
--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).