From: Darren Hart <dvhart@infradead.org>
To: Azael Avalos <coproscefalo@gmail.com>
Cc: platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] toshiba_acpi: Add Hotkey Event Type function and definitions
Date: Fri, 6 Mar 2015 10:21:02 -0800 [thread overview]
Message-ID: <20150306182102.GG19001@vmdeb7> (raw)
In-Reply-To: <1424973434-3032-2-git-send-email-coproscefalo@gmail.com>
On Thu, Feb 26, 2015 at 10:57:12AM -0700, Azael Avalos wrote:
Hi Azael,
I'm pretty behind on this one, apologies.
> This patch adds support to query the "Hotkey Event Type" the system
> supports.
>
> There are two main event types (so far), 0x10 and 0x11, with the
> first beign all those laptops that have the old keyboard layout, and
being
> the latter all those new laptops with the new keyboard layout.
>
Some concern about this binary "new" and "old". What happens in 2 years when
they decide to break^W change our keyboards again?
> Signed-off-by: Azael Avalos <coproscefalo@gmail.com>
> ---
> drivers/platform/x86/toshiba_acpi.c | 26 ++++++++++++++++++++++++++
> 1 file changed, 26 insertions(+)
>
> diff --git a/drivers/platform/x86/toshiba_acpi.c b/drivers/platform/x86/toshiba_acpi.c
> index dbcb7a8..e6aa8f9 100644
> --- a/drivers/platform/x86/toshiba_acpi.c
> +++ b/drivers/platform/x86/toshiba_acpi.c
> @@ -116,6 +116,7 @@ MODULE_LICENSE("GPL");
> #define HCI_KBD_ILLUMINATION 0x0095
> #define HCI_ECO_MODE 0x0097
> #define HCI_ACCELEROMETER2 0x00a6
> +#define HCI_HOTKEY_EVENT_TYPE 0xc000
> #define SCI_PANEL_POWER_ON 0x010d
> #define SCI_ILLUMINATION 0x014e
> #define SCI_USB_SLEEP_CHARGE 0x0150
> @@ -127,8 +128,11 @@ MODULE_LICENSE("GPL");
>
> /* field definitions */
> #define HCI_ACCEL_MASK 0x7fff
> +#define HCI_HOTKEY_EVENT_NORMAL 0x10
> +#define HCI_HOTKEY_EVENT_SPECIAL 0x11
NORMAL and SPECIAL? Hrm... what comes after special? EXTRASPECIAL? ;-)
Or am I not looking at this right? Is there reason to expect these two to be
sufficient?
> #define HCI_HOTKEY_DISABLE 0x0b
> #define HCI_HOTKEY_ENABLE 0x09
> +#define HCI_HOTKEY_ENABLE_SPECIAL 0x10
> #define HCI_LCD_BRIGHTNESS_BITS 3
> #define HCI_LCD_BRIGHTNESS_SHIFT (16-HCI_LCD_BRIGHTNESS_BITS)
> #define HCI_LCD_BRIGHTNESS_LEVELS (1 << HCI_LCD_BRIGHTNESS_BITS)
> @@ -1149,6 +1153,28 @@ static int toshiba_usb_three_set(struct toshiba_acpi_dev *dev, u32 state)
> return 0;
> }
>
> +/* Hotkey event type */
> +static int toshiba_hotkey_event_type_get(struct toshiba_acpi_dev *dev,
> + u32 *hotkey_event_type)
> +{
> + u32 val1 = 0x03;
> + u32 val2 = 0;
> + u32 result;
> +
> + result = hci_read2(dev, HCI_HOTKEY_EVENT_TYPE, &val1, &val2);
> + if (result == TOS_FAILURE) {
> + pr_err("ACPI callto get Hotkey Event type failed\n");
call to
Thanks,
--
Darren Hart
Intel Open Source Technology Center
next prev parent reply other threads:[~2015-03-06 18:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 17:57 [PATCH 0/3] toshiba_acpi: Hotkey handling and keymap updates Azael Avalos
2015-02-26 17:57 ` [PATCH 1/3] toshiba_acpi: Add Hotkey Event Type function and definitions Azael Avalos
2015-03-06 18:21 ` Darren Hart [this message]
2015-03-06 18:42 ` Azael Avalos
2015-03-19 3:56 ` Darren Hart
2015-02-26 17:57 ` [PATCH 2/3] toshiba_acpi: Use the Hotkey Event Type function for keymap choosing Azael Avalos
2015-03-06 18:22 ` Darren Hart
2015-02-26 17:57 ` [PATCH 3/3] toshiba_acpi: Fix the enabling of the Special Functions Azael Avalos
2015-03-06 18:28 ` Darren Hart
2015-03-06 18:52 ` Azael Avalos
2015-03-19 3:58 ` Darren Hart
2015-03-06 18:34 ` [PATCH 0/3] toshiba_acpi: Hotkey handling and keymap updates Darren Hart
2015-03-06 18:58 ` Azael Avalos
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=20150306182102.GG19001@vmdeb7 \
--to=dvhart@infradead.org \
--cc=coproscefalo@gmail.com \
--cc=linux-kernel@vger.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