From: Vadim Pasternak <vadimp@nvidia.com>
To: andy.shevchenko@gmail.com, dvhart@infradead.org
Cc: platform-driver-x86@vger.kernel.org, Vadim Pasternak <vadimp@nvidia.com>
Subject: [PATCH platform-next 5/5] platform/x86: mlx-platform: Add capability field to platform FAN description
Date: Wed, 23 Sep 2020 20:20:53 +0300 [thread overview]
Message-ID: <20200923172053.26296-6-vadimp@nvidia.com> (raw)
In-Reply-To: <20200923172053.26296-1-vadimp@nvidia.com>
Set 'capability' field to FAN core platform data..
The content of 'capability' register allows to set the mapping between
the drawers and tachometers.
The motivation is to avoid adding a new code in the future in order to
distinct between the systems types supporting a different kinds of the
FAN drawers.
Signed-off-by: Vadim Pasternak <vadimp@nvidia.com>
---
drivers/platform/x86/mlx-platform.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/platform/x86/mlx-platform.c b/drivers/platform/x86/mlx-platform.c
index 04a745095c37..986ad3dda1c1 100644
--- a/drivers/platform/x86/mlx-platform.c
+++ b/drivers/platform/x86/mlx-platform.c
@@ -1939,6 +1939,7 @@ static struct mlxreg_core_data mlxplat_mlxcpld_default_fan_data[] = {
static struct mlxreg_core_platform_data mlxplat_default_fan_data = {
.data = mlxplat_mlxcpld_default_fan_data,
.counter = ARRAY_SIZE(mlxplat_mlxcpld_default_fan_data),
+ .capability = MLXPLAT_CPLD_LPC_REG_FAN_DRW_CAP_OFFSET,
};
/* Watchdog type1: hardware implementation version1
--
2.11.0
next prev parent reply other threads:[~2020-09-23 17:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 17:20 [PATCH platform-next 0/5] platform/x86: mlx-platform: Topology fixes and configuration updates Vadim Pasternak
2020-09-23 17:20 ` [PATCH platform-next 1/5] platform/x86: mlx-platform: Remove PSU EEPROM configuration Vadim Pasternak
2020-09-24 8:33 ` Hans de Goede
2020-09-23 17:20 ` [PATCH platform-next 2/5] platform/x86: mlx-platform: Fix extended topology configuration for power supply units Vadim Pasternak
2020-09-24 8:33 ` Hans de Goede
2020-09-23 17:20 ` [PATCH platform-next 3/5] platform_data/mlxreg: Update module license Vadim Pasternak
2020-09-24 8:33 ` Hans de Goede
2020-09-23 17:20 ` [PATCH platform-next 4/5] platform_data/mlxreg: Extend core platform structure Vadim Pasternak
2020-09-24 8:36 ` Hans de Goede
2020-09-23 17:20 ` Vadim Pasternak [this message]
2020-09-24 8:36 ` [PATCH platform-next 5/5] platform/x86: mlx-platform: Add capability field to platform FAN description Hans de Goede
2020-10-07 21:24 ` [PATCH platform-next 0/5] platform/x86: mlx-platform: Topology fixes and configuration updates Hans de Goede
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=20200923172053.26296-6-vadimp@nvidia.com \
--to=vadimp@nvidia.com \
--cc=andy.shevchenko@gmail.com \
--cc=dvhart@infradead.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