X86 platform drivers
 help / color / mirror / Atom feed
From: Suma Hegde <suma.hegde@amd.com>
To: <platform-driver-x86@vger.kernel.org>
Cc: <ilpo.jarvinen@linux.intel.com>, <hdegoede@redhat.com>,
	<muthusamy.ramalingam@amd.com>, <NaveenKrishna.Chatradhi@amd.com>,
	Suma Hegde <Suma.Hegde@amd.com>,
	Muthusamy Ramalingam <Muthusamy.Ramalingam@amd.com>
Subject: [PATCH 00/11] platform/x86/amd/hsmp: Per-platform enabled-message bitmaps
Date: Thu, 8 Oct 2026 09:29:28 +0000	[thread overview]
Message-ID: <cover.1791446401.git.Suma.Hegde@amd.com> (raw)

From: Suma Hegde <Suma.Hegde@amd.com>

This series introduces per-socket read/write enabled-message bitmaps so
the HSMP driver rejects unsupported messages before they reach the SMU.
Prep patches fix sock_ind bounds checking, move proto_ver onto
hsmp_socket, and reorder helpers for the validation path. Later patches
populate the bitmaps statically and via HSMP_GET_ENABLED_HSMP_CMDS
(6th Gen AMD EPYC Server and future platforms), and update sysfs/hwmon
file modes from the bitmaps.

Client platforms skip bitmap init, populate, and validation until
dedicated client tables exist; shared smu_fw_version and
protocol_version sysfs attributes remain visible there.

Patch summary:
  01/11  platform/x86/amd/hsmp: Fix sock_ind bounds check in is_bin_visible
  02/11  platform/x86/amd/hsmp: Move proto_ver to hsmp_socket structure
  03/11  platform/x86/amd/hsmp: Null-check drvdata in hsmp_is_sock_attr_visible()
  04/11  platform/x86/amd/hsmp: Move is_get_msg() before validate_message()
  05/11  platform/x86/amd/hsmp: Use local sock pointer in init_acpi()
  06/11  platform/x86/amd/hsmp: Move the sock_ind bound check before validate_message()
  07/11  platform/x86/amd/hsmp: Add per-platform bitmap to validate HSMP messages
  08/11  platform/x86/amd/hsmp: Populate the bitmaps dynamically on 6th Gen AMD EPYC Server
  09/11  platform/x86/amd/hsmp: Populate the bitmaps dynamically for future platforms
  10/11  platform/x86/amd/hsmp: Relocate to_hsmp_sys_attr() macro
  11/11  platform/x86/amd/hsmp: Update sysfs and hwmon file modes based on platform capabilities

Signed-off-by: Suma Hegde <Suma.Hegde@amd.com>
Signed-off-by: Muthusamy Ramalingam <Muthusamy.Ramalingam@amd.com>

Suma Hegde (11):
  platform/x86/amd/hsmp: Fix sock_ind bounds check in is_bin_visible
  platform/x86/amd/hsmp: Move proto_ver to hsmp_socket structure
  platform/x86/amd/hsmp: Null-check drvdata in
    hsmp_is_sock_attr_visible()
  platform/x86/amd/hsmp: Move is_get_msg() before validate_message()
  platform/x86/amd/hsmp: Use local sock pointer in init_acpi()
  platform/x86/amd/hsmp: Move the sock_ind bound check before
    validate_message()
  platform/x86/amd/hsmp: Add per-platform bitmap to validate HSMP
    messages
  platform/x86/amd/hsmp: Populate the bitmaps dynamically on 6th Gen AMD
    EPYC Server
  platform/x86/amd/hsmp: Populate the bitmaps dynamically for future
    platforms
  platform/x86/amd/hsmp: Relocate to_hsmp_sys_attr() macro
  platform/x86/amd/hsmp: Update sysfs and hwmon file modes based on
    platform capabilities

 drivers/platform/x86/amd/hsmp/acpi.c  |  92 ++++++++++--
 drivers/platform/x86/amd/hsmp/hsmp.c  | 203 ++++++++++++++++++++++++--
 drivers/platform/x86/amd/hsmp/hsmp.h  |  29 +++-
 drivers/platform/x86/amd/hsmp/hwmon.c |  24 ++-
 drivers/platform/x86/amd/hsmp/plat.c  |  26 +++-
 5 files changed, 339 insertions(+), 35 deletions(-)

This is rebased on below patchset:
https://lore.kernel.org/platform-driver-x86/20260924154947.1706669-1-muralidhara.mk@amd.com/T/#t
[PATCH v7 0/4] platform/x86/amd/hsmp: Family 1Ah client support by Muralidhar M K

-- 
2.34.1


             reply	other threads:[~2026-10-08  9:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-08  9:29 Suma Hegde [this message]
2026-10-08  9:29 ` [PATCH 01/11] platform/x86/amd/hsmp: Fix sock_ind bounds check in is_bin_visible Suma Hegde
2026-10-08  9:29 ` [PATCH 02/11] platform/x86/amd/hsmp: Move proto_ver to hsmp_socket structure Suma Hegde
2026-10-08  9:29 ` [PATCH 03/11] platform/x86/amd/hsmp: Null-check drvdata in hsmp_is_sock_attr_visible() Suma Hegde
2026-10-21 11:07   ` Ilpo Järvinen
2026-10-08  9:29 ` [PATCH 04/11] platform/x86/amd/hsmp: Move is_get_msg() before validate_message() Suma Hegde
2026-10-08  9:29 ` [PATCH 05/11] platform/x86/amd/hsmp: Use local sock pointer in init_acpi() Suma Hegde
2026-10-08  9:29 ` [PATCH 06/11] platform/x86/amd/hsmp: Move the sock_ind bound check before validate_message() Suma Hegde
2026-10-08  9:29 ` [PATCH 07/11] platform/x86/amd/hsmp: Add per-platform bitmap to validate HSMP messages Suma Hegde
2026-10-21 11:25   ` Ilpo Järvinen
2026-10-21 11:28     ` Ilpo Järvinen
2026-10-08  9:29 ` [PATCH 08/11] platform/x86/amd/hsmp: Populate the bitmaps dynamically on 6th Gen AMD EPYC Server Suma Hegde
2026-10-08  9:29 ` [PATCH 09/11] platform/x86/amd/hsmp: Populate the bitmaps dynamically for future platforms Suma Hegde
2026-10-08  9:29 ` [PATCH 10/11] platform/x86/amd/hsmp: Relocate to_hsmp_sys_attr() macro Suma Hegde
2026-10-08  9:29 ` [PATCH 11/11] platform/x86/amd/hsmp: Update sysfs and hwmon file modes based on platform capabilities Suma Hegde

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=cover.1791446401.git.Suma.Hegde@amd.com \
    --to=suma.hegde@amd.com \
    --cc=NaveenKrishna.Chatradhi@amd.com \
    --cc=hdegoede@redhat.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=muthusamy.ramalingam@amd.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