From: Guenter Roeck <linux@roeck-us.net>
To: "Joaquín Ignacio Aramendía" <samsagax@gmail.com>
Cc: Jerrod Frost <jcfrosty@proton.me>,
derekjohn.clark@gmail.com, jdelvare@suse.com,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hwmon: (oxp-sensors) Add support for AOKZOE A1 PRO
Date: Sat, 24 Jun 2023 16:49:59 -0700 [thread overview]
Message-ID: <4d1d5fac-4ad1-2ea7-a349-1b174be694d3@roeck-us.net> (raw)
In-Reply-To: <20230624231637.14941-2-samsagax@gmail.com>
On 6/24/23 16:16, Joaquín Ignacio Aramendía wrote:
> From: Jerrod Frost <jcfrosty@proton.me>
>
> This device is an iteration over the AOKZOE A1 with the same EC mapping
> and features. It also has support for tt_toggle.
>
> Thanks to Jerrod for authoring and testing.
>
> Signed-off-by: Joaquín Ignacio Aramendía <samsagax@gmail.com>
From: and the first Signed-off-by: have to match. You would need
Jerrod's Signed-off-by: tag to keep his authorship.
Guenter
> ---
> Documentation/hwmon/oxp-sensors.rst | 2 ++
> drivers/hwmon/oxp-sensors.c | 7 +++++++
> 2 files changed, 9 insertions(+)
>
> diff --git a/Documentation/hwmon/oxp-sensors.rst b/Documentation/hwmon/oxp-sensors.rst
> index 0ca1f7728c34..3adeb7406243 100644
> --- a/Documentation/hwmon/oxp-sensors.rst
> +++ b/Documentation/hwmon/oxp-sensors.rst
> @@ -30,6 +30,7 @@ Supported devices
> Currently the driver supports the following handhelds:
>
> - AOK ZOE A1
> + - AOK ZOE A1 PRO
> - Aya Neo 2
> - Aya Neo AIR
> - Aya Neo AIR Pro
> @@ -40,6 +41,7 @@ Currently the driver supports the following handhelds:
>
> "Turbo/Silent" button behaviour toggle is only supported on:
> - AOK ZOE A1
> + - AOK ZOE A1 PRO
> - OneXPlayer mini AMD (only with updated alpha BIOS)
> - OneXPlayer mini AMD PRO
>
> diff --git a/drivers/hwmon/oxp-sensors.c b/drivers/hwmon/oxp-sensors.c
> index 1e59d97219c4..e1a907cae820 100644
> --- a/drivers/hwmon/oxp-sensors.c
> +++ b/drivers/hwmon/oxp-sensors.c
> @@ -77,6 +77,13 @@ static const struct dmi_system_id dmi_table[] = {
> },
> .driver_data = (void *)aok_zoe_a1,
> },
> + {
> + .matches = {
> + DMI_MATCH(DMI_BOARD_VENDOR, "AOKZOE"),
> + DMI_EXACT_MATCH(DMI_BOARD_NAME, "AOKZOE A1 Pro"),
> + },
> + .driver_data = (void *)aok_zoe_a1,
> + },
> {
> .matches = {
> DMI_MATCH(DMI_BOARD_VENDOR, "AYANEO"),
prev parent reply other threads:[~2023-06-24 23:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-24 23:16 Joaquín Ignacio Aramendía
2023-06-24 23:49 ` Guenter Roeck [this message]
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=4d1d5fac-4ad1-2ea7-a349-1b174be694d3@roeck-us.net \
--to=linux@roeck-us.net \
--cc=derekjohn.clark@gmail.com \
--cc=jcfrosty@proton.me \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=samsagax@gmail.com \
/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
all inboxes | Powered by JetHome®