From: mail@richard-neumann.de
To: nehal-bakulchandra.shah@amd.com, sandeep.singh@amd.com,
mail@richard-neumann.de, jikos@kernel.org,
benjamin.tissoires@redhat.com, arnd@arndb.de,
linux-kernel@vger.kernel.org, linux-input@vger.kernel.org
Subject: [PATCH v2 0/3] Add quirks to AMD Sensor Fusion Hub driver
Date: Wed, 27 Jan 2021 17:25:57 +0100 [thread overview]
Message-ID: <20210127162600.35927-1-mail@richard-neumann.de> (raw)
From: Richard Neumann <mail@richard-neumann.de>
This patch adds quirks to the upstream (v8) version of the
AMD Sensor Fusion Hub driver.
The quirks provide a function to detect the sensor mask for systems
that do not have it stored in the AMD_P2C_MSG3 register.
The information about the systems IDs and available sensors was
taken from: https://bugzilla.kernel.org/show_bug.cgi?id=199715
Changes since v1:
* Added missing object amd_sfh_quirks.o to amd_sfh-objs
* changed type of "system" in "amd_sfh_quirks_get_sensor_mask"
- struct dmi_system_id -> const struct dmi_system_id
Richard Neumann (3):
Outsourced sensor masks to PCI driver header.
Added quirks to detect sensor masks.
Updated MAINTAINERS
MAINTAINERS | 1 +
drivers/hid/amd-sfh-hid/Makefile | 1 +
drivers/hid/amd-sfh-hid/amd_sfh_pcie.c | 16 +++----
drivers/hid/amd-sfh-hid/amd_sfh_pcie.h | 15 +++++++
drivers/hid/amd-sfh-hid/amd_sfh_quirks.c | 55 ++++++++++++++++++++++++
5 files changed, 79 insertions(+), 9 deletions(-)
create mode 100644 drivers/hid/amd-sfh-hid/amd_sfh_quirks.c
--
2.30.0
next reply other threads:[~2021-01-27 16:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 16:25 mail [this message]
2021-01-27 16:25 ` [PATCH v2 1/3] Outsourced sensor masks to PCI driver header mail
2021-01-27 16:25 ` [PATCH v2 2/3] Added quirks to detect sensor masks mail
2021-01-27 16:26 ` [PATCH v2 3/3] Updated MAINTAINERS mail
2021-02-09 9:39 ` [PATCH v2 0/3] Add quirks to AMD Sensor Fusion Hub driver Jiri Kosina
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=20210127162600.35927-1-mail@richard-neumann.de \
--to=mail@richard-neumann.de \
--cc=arnd@arndb.de \
--cc=benjamin.tissoires@redhat.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nehal-bakulchandra.shah@amd.com \
--cc=sandeep.singh@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.