All of lore.kernel.org
 help / color / mirror / Atom feed
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 4/5] platform_data/mlxreg:  Extend core platform structure
Date: Wed, 23 Sep 2020 20:20:52 +0300	[thread overview]
Message-ID: <20200923172053.26296-5-vadimp@nvidia.com> (raw)
In-Reply-To: <20200923172053.26296-1-vadimp@nvidia.com>

Add 'capability' field to structure 'mlxreg_core_platform_data'.
The purpose of this filed to indicate  the actual number of the
components within the particular group. Such components could be,
for example the number of the FAN drawers. Some systems are equipped
with FAN drawers with one tachometer inside, others with FAN drawers
with several tachometers inside.

Signed-off-by: Vadim Pasternak <vadimp@nvidia.com>
---
 include/linux/platform_data/mlxreg.h | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/include/linux/platform_data/mlxreg.h b/include/linux/platform_data/mlxreg.h
index 0a727d405a7a..101333fe2b8d 100644
--- a/include/linux/platform_data/mlxreg.h
+++ b/include/linux/platform_data/mlxreg.h
@@ -109,6 +109,7 @@ struct mlxreg_core_item {
  * @features: supported features of device;
  * @version: implementation version;
  * @identity: device identity name;
+ * @capability: device capability register;
  */
 struct mlxreg_core_platform_data {
 	struct mlxreg_core_data *data;
@@ -117,6 +118,7 @@ struct mlxreg_core_platform_data {
 	u32 features;
 	u32 version;
 	char identity[MLXREG_CORE_LABEL_MAX_SIZE];
+	u32 capability;
 };
 
 /**
-- 
2.11.0


  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 ` Vadim Pasternak [this message]
2020-09-24  8:36   ` [PATCH platform-next 4/5] platform_data/mlxreg: Extend core platform structure Hans de Goede
2020-09-23 17:20 ` [PATCH platform-next 5/5] platform/x86: mlx-platform: Add capability field to platform FAN description Vadim Pasternak
2020-09-24  8:36   ` 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-5-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 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.