From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Vadim Pasternak <vadimp@nvidia.com>
Cc: hdegoede@redhat.com, platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH platform-next v3 16/16] Documentation/ABI: Add new attribute for mlxreg-io sysfs interfaces
Date: Tue, 22 Aug 2023 11:55:40 +0300 (EEST) [thread overview]
Message-ID: <61c08737-727-b190-5caa-26d172af5b2c@linux.intel.com> (raw)
In-Reply-To: <20230822081335.64344-17-vadimp@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 3938 bytes --]
On Tue, 22 Aug 2023, Vadim Pasternak wrote:
> Add documentation for the new attributes:
> - CPLD versioning: "cpld5_pn", "cpld5_version", "cpld5_version_min".
> - JTAG capability: "jtag_cap", indicating the available method of
> CPLD/FPGA devices field update.
> - System lid status: "lid_open".
> - Reset caused by long press of power button: "reset_long_pwr_pb".
> - Reset caused by switch board DC-DC converter device failure:
> "reset_swb_dc_dc_pwr_fail".
>
> Signed-off-by: Vadim Pasternak <vadimp@nvidia.com>
> Reviewed-by: Michael Shych <michaelsh@nvidia.com>
> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
> ---
> Comments provided by Hans:
> v2->v3:
> - Document new attribute "reset_swb_dc_dc_pwr_fail".
> ---
> .../ABI/stable/sysfs-driver-mlxreg-io | 52 +++++++++++++++++++
> 1 file changed, 52 insertions(+)
>
> diff --git a/Documentation/ABI/stable/sysfs-driver-mlxreg-io b/Documentation/ABI/stable/sysfs-driver-mlxreg-io
> index 60953903d007..7022c623075b 100644
> --- a/Documentation/ABI/stable/sysfs-driver-mlxreg-io
> +++ b/Documentation/ABI/stable/sysfs-driver-mlxreg-io
> @@ -662,3 +662,55 @@ Description: This file shows the system reset cause due to AC power failure.
> Value 1 in file means this is reset cause, 0 - otherwise.
>
> The file is read only.
> +
> +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/cpld5_pn
> +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/cpld5_version
> +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/cpld5_version_min
> +Date: August 2023
> +KernelVersion: 6.6
> +Contact: Vadim Pasternak <vadimp@nvidia.com>
> +Description: These files show with which CPLD part numbers, version and minor
> + versions have been burned the 5-th CPLD device equipped on a
> + system.
> +
> + The files are read only.
> +
> +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/jtag_cap
> +Date: August 2023
> +KernelVersion: 6.6
> +Contact: Vadim Pasternak <vadimp@nvidia.com>
> +Description: This file indicates the available method of CPLD/FPGA devices
> + field update through the JTAG chain:
> + b00 - field update through LPC bus register memory space.
> + b01 - Reserved.
> + b10 - Reserved.
> + b11 - field update through CPU GPIOs bit-banging.
> +
> + The file is read only.
> +
> +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lid_open
> +Date: August 2023
> +KernelVersion: 6.6
> +Contact: Vadim Pasternak <vadimp@nvidia.com>
> +Description: 1 - indicates that system lid is opened, otherwise 0.
> +
> + The file is read only.
> +
> +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_long_pwr_pb
> +Date: August 2023
> +KernelVersion: 6.6
> +Contact: Vadim Pasternak <vadimp@nvidia.com>
> +Description: This file if set 1 indicates that system has been reset by
> + long press of power button.
> +
> + The file is read only.
> +
> +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_swb_dc_dc_pwr_fail
> +Date: August 2023
> +KernelVersion: 6.6
> +Contact: Vadim Pasternak <vadimp@nvidia.com>
> +Description: This file shows the system reset cause due to the failure of
> + DC-DC power converter devices, equipped on the switch board.
> + Value 1 in file means this is reset cause, 0 - otherwise.
What "this" on the last line refers to. I'm unable to figure it out from
the text.
In general, the meaning here is quite unclear. I think the "cause due to"
put together is the main source of confusion (it's like saying "cause
cause" or "due to due to"). Do you mean the cause for the system reset is
the failure of the DC-DC power converter devices if this file shows 1?
For the other patches 1-15:
Reviewed-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
One additional thing you want to address is the missing '\n' chars from
the dev_*() prints but it can be handled after these patches.
> +
> + The file is read only.
>
--
i.
prev parent reply other threads:[~2023-08-22 8:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 8:13 [PATCH platform-next v3 00/16] Add new features and amendments for Nvidia systems Vadim Pasternak
2023-08-22 8:13 ` [PATCH platform-next v3 01/16] platform: mellanox: Add new attributes Vadim Pasternak
2023-08-22 8:13 ` [PATCH platform-next v3 02/16] platform: mellanox: Add field upgrade capability register Vadim Pasternak
2023-08-22 8:13 ` [PATCH platform-next v3 03/16] platform: mellanox: Modify reset causes description Vadim Pasternak
2023-08-22 8:13 ` [PATCH platform-next v3 04/16] platform: mellanox: mlx-platform: Modify health and power hotplug action Vadim Pasternak
2023-08-22 8:13 ` [PATCH platform-next v3 05/16] platform: mellanox: mlx-platform: Add reset cause attribute Vadim Pasternak
2023-08-22 8:13 ` [PATCH platform-next v3 06/16] platform: mellanox: mlx-platform: add support for additional CPLD Vadim Pasternak
2023-08-22 8:13 ` [PATCH platform-next v3 07/16] platform: mellanox: mlx-platform: Modify power off callback Vadim Pasternak
2023-08-22 8:13 ` [PATCH platform-next v3 08/16] platform: mellanox: Cosmetic changes Vadim Pasternak
2023-08-22 8:13 ` [PATCH platform-next v3 09/16] platform: mellanox: mlx-platform: Add reset callback Vadim Pasternak
2023-08-22 8:13 ` [PATCH platform-next v3 10/16] platform: mellanox: mlx-platform: Prepare driver to allow probing through ACPI infrastructure Vadim Pasternak
2023-08-22 8:13 ` [PATCH platform-next v3 11/16] platform: mellanox: mlx-platform: Introduce ACPI init flow Vadim Pasternak
2023-08-22 8:13 ` [PATCH platform-next v3 12/16] platform: mellanox: mlx-platform: Get interrupt line through ACPI Vadim Pasternak
2023-08-22 8:13 ` [PATCH platform-next v3 13/16] platform: mellanox: Add initial support for PCIe based programming logic device Vadim Pasternak
2023-08-22 8:13 ` [PATCH platform-next v3 14/16] platform/mellanox: mlxreg-hotplug: Extend condition for notification callback processing Vadim Pasternak
2023-08-22 8:13 ` [PATCH platform-next v3 15/16] platform: mellanox: nvsw-sn2201: change fans i2c busses Vadim Pasternak
2023-08-22 8:13 ` [PATCH platform-next v3 16/16] Documentation/ABI: Add new attribute for mlxreg-io sysfs interfaces Vadim Pasternak
2023-08-22 8:55 ` Ilpo Järvinen [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=61c08737-727-b190-5caa-26d172af5b2c@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=vadimp@nvidia.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