From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Svyatoslav Ryhel <clamor95@gmail.com>
Cc: "Lee Jones" <lee@kernel.org>, "Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Pavel Machek" <pavel@kernel.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Sebastian Reichel" <sre@kernel.org>,
"Michał Mirosław" <mirq-linux@rere.qmqm.pl>,
"Ion Agorria" <ion@agorria.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-input@vger.kernel.org, linux-leds@vger.kernel.org,
linux-pm@vger.kernel.org
Subject: Re: [PATCH v1 6/9] input: keyboard: Add driver for Asus Transformer dock multimedia keys
Date: Tue, 3 Feb 2026 03:00:24 -0800 [thread overview]
Message-ID: <aYHU5g5iOVjrHrE_@google.com> (raw)
In-Reply-To: <20260201104343.79231-7-clamor95@gmail.com>
Hi Svyatoslav,
On Sun, Feb 01, 2026 at 12:43:40PM +0200, Svyatoslav Ryhel wrote:
> +static void asus_ec_input_event(struct input_handle *handle,
> + unsigned int event_type,
> + unsigned int event_code, int value)
> +{
> + struct asus_ec_keys_data *priv = handle->handler->private;
> +
> + /* Store special key state */
> + if (event_type == EV_KEY && event_code == KEY_RIGHTALT)
> + priv->special_key_pressed = !!value;
Is this functionality supposed to be triggered by any keyboard or only
the dock one?
Thanks.
--
Dmitry
next prev parent reply other threads:[~2026-02-03 11:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-01 10:43 [PATCH v1 0/9] mfd: Add support for Asus Transformer embedded controller Svyatoslav Ryhel
2026-02-01 10:43 ` [PATCH v1 1/9] dt-bindings: misc: document ASUS Transformers EC Dockram Svyatoslav Ryhel
2026-02-01 10:43 ` [PATCH v1 2/9] misc: Support Asus Transformer's EC access device Svyatoslav Ryhel
2026-02-03 11:41 ` Greg Kroah-Hartman
2026-02-03 11:54 ` Svyatoslav Ryhel
2026-02-03 12:00 ` Greg Kroah-Hartman
2026-02-03 12:01 ` Svyatoslav Ryhel
2026-02-03 16:28 ` Svyatoslav Ryhel
2026-02-03 16:45 ` Greg Kroah-Hartman
2026-02-03 16:50 ` Svyatoslav Ryhel
2026-02-03 16:58 ` Greg Kroah-Hartman
2026-02-04 12:40 ` Svyatoslav Ryhel
2026-02-01 10:43 ` [PATCH v1 3/9] dt-bindings: mfd: document ASUS Transformer EC Svyatoslav Ryhel
2026-02-01 10:43 ` [PATCH v1 4/9] mfd: Add driver for Asus Transformer embedded controller Svyatoslav Ryhel
2026-02-01 17:51 ` kernel test robot
2026-02-01 19:06 ` kernel test robot
2026-02-01 10:43 ` [PATCH v1 5/9] input: serio: Add driver for Asus Transformer dock keyboard and touchpad Svyatoslav Ryhel
2026-02-01 10:43 ` [PATCH v1 6/9] input: keyboard: Add driver for Asus Transformer dock multimedia keys Svyatoslav Ryhel
2026-02-03 11:00 ` Dmitry Torokhov [this message]
2026-02-03 11:18 ` Svyatoslav Ryhel
2026-02-01 10:43 ` [PATCH v1 7/9] leds: Add driver for Asus Transformer LEDs Svyatoslav Ryhel
2026-02-01 10:43 ` [PATCH v1 8/9] power: supply: Add driver for Asus Transformer battery Svyatoslav Ryhel
2026-02-01 10:43 ` [PATCH v1 9/9] power: supply: Add charger driver for Asus Transformers Svyatoslav Ryhel
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=aYHU5g5iOVjrHrE_@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=arnd@arndb.de \
--cc=clamor95@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=ion@agorria.com \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mirq-linux@rere.qmqm.pl \
--cc=pavel@kernel.org \
--cc=robh@kernel.org \
--cc=sre@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