From: Vadim Pasternak <vadimp@nvidia.com>
To: <hdegoede@redhat.com>
Cc: <ilpo.jarvinen@linux.intel.com>,
<platform-driver-x86@vger.kernel.org>,
Vadim Pasternak <vadimp@nvidia.com>
Subject: [PATCH platform-next 00/16] Add new features and amendments for Nvidia systems
Date: Mon, 14 Aug 2023 20:33:09 +0000 [thread overview]
Message-ID: <20230814203325.12314-1-vadimp@nvidia.com> (raw)
The patch set:
- Provides New system attributes for monitoring.
- Adds system reboot callback to perform system specific operations.
- Adds support for ACPI based initialization flow.
- Adds support for FPGA device connected through PCIe bus.
- Adds additional logic for hotplug events handling.
- Contains some amendments and cosmetic changes.
The patch set includes:
Patches #1 - #3, #5: add new attributes for monitoring.
Patch #4: sets hotplug event action for health and power signals.
Patch #6: adds CPLD versioning registers for systems equipped with five
CPLD devices.
Patch #7: modifies power off callback.
Patch #8: cosmetic changes - fixes misspelling.
Patch #9: provides system reboot callback through system reboot
notifier.
Patch #10: prepares driver to allow probing through ACPI hooks along
with probing through DMI hooks.
Patch #11: adds ACPI match hook for initialization flow.
Patch #12: adds support for getting system interrupt line from ACPI
table.
Patch #13: adds initial support for programming logic device connected
through PCIe.
Patch #14: Extends condition for notification callback processing.
Patch #15: defines the exact i2c bus of fans on the SN2201 system.
Patch #16: Documents new attributes.
Michael Shych (1):
platform: mellanox: nvsw-sn2201: change fans i2c busses.
Vadim Pasternak (15):
platform: mellanox: Add new attributes
platform: mellanox: Add field upgrade capability register
platform: mellanox: Modify reset causes description
platform: mellanox: mlx-platform: Modify health and power hotplug
action
platform: mellanox: mlx-platform: Add reset cause attribute
platform: mellanox: mlx-platform: add support for additional CPLD
platform: mellanox: mlx-platform: Modify power off callback
platform: mellanox: Cosmetic changes
platform: mellanox: mlx-platform: Add reset callback
platform: mellanox: mlx-platform: Prepare driver to allow probing
through ACPI infrastructure
platform: mellanox: mlx-platform: Introduce ACPI init flow
platform: mellanox: mlx-platform: Get interrupt line through ACPI
platform: mellanox: Add initial support for PCIe based programming
logic device
platform/mellanox: mlxreg-hotplug: Extend condition for notification
callback processing
Documentation/ABI: Add new attribute for mlxreg-io sysfs interfaces
.../ABI/stable/sysfs-driver-mlxreg-io | 42 ++
drivers/platform/mellanox/mlxreg-hotplug.c | 2 +-
drivers/platform/mellanox/nvsw-sn2201.c | 12 +-
drivers/platform/x86/mlx-platform.c | 375 ++++++++++++++++--
4 files changed, 382 insertions(+), 49 deletions(-)
--
2.20.1
next reply other threads:[~2023-08-14 20:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 20:33 Vadim Pasternak [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-14 8:58 [PATCH platform-next 00/16] Add new features and amendments for Nvidia systems Vadim Pasternak
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=20230814203325.12314-1-vadimp@nvidia.com \
--to=vadimp@nvidia.com \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--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