mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: K Prateek Nayak <kprateek.nayak@amd.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
	Len Brown <lenb@kernel.org>, Borislav Petkov <bp@alien8.de>,
	Mario Limonciello <mario.limonciello@amd.com>,
	Yazen Ghannam <yazen.ghannam@amd.com>,
	<linux-kernel@vger.kernel.org>, <linux-acpi@vger.kernel.org>,
	<acpica-devel@lists.linux.dev>
Cc: Vilas Sridharan <Vilas.Sridharan@amd.com>,
	K Prateek Nayak <kprateek.nayak@amd.com>
Subject: [RFC PATCH 1/3] ACPICA: actbl2.h: ACPI 6.5: PHAT: Add more struct definitions
Date: Wed, 3 Jun 2026 06:33:14 +0000	[thread overview]
Message-ID: <20260603063317.13665-2-kprateek.nayak@amd.com> (raw)
In-Reply-To: <20260603063317.13665-1-kprateek.nayak@amd.com>

The ACPI Specification v6.5 [1] under Sec. 5.2.31 "Platform Health
Assessment Table (PHAT)" listed additional definition for
"Device-specific Data" and "Vendor Specific Reset Reason Entry" in
Table 5.168 "Reset Reason Health Record Structure" and
Table 5.169: "Reset Reason Health Record Vendor Data Entry".

Add these definitions as part actbl2.h. The struct definitions will be
used in the subsequent commit to implement a generic PHAT parser for
vendor entries.

Link: https://uefi.org/sites/default/files/resources/ACPI_Spec_6_5_Aug29.pdf [1]
Signed-off-by: K Prateek Nayak <kprateek.nayak@amd.com>
---
 include/acpi/actbl2.h | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/include/acpi/actbl2.h b/include/acpi/actbl2.h
index 5c0b55e7b3e4..bff0b92d0c82 100644
--- a/include/acpi/actbl2.h
+++ b/include/acpi/actbl2.h
@@ -2844,6 +2844,20 @@ struct acpi_phat_health_data {
 	u32 device_specific_offset;	/* Zero if no Device-specific data */
 };
 
+struct acpi_phat_device_data {
+	u8 supported_sources;
+	u8 source;
+	u8 sub_source;
+	u8 reason;
+	u16 vendor_count;		/* Zero if no Vendor specific data */
+};
+
+struct acpi_phat_vendor_element {
+	u8 vendor_guid[16];
+	u16 length;
+	u16 revision;
+};
+
 /* Values for Health field above */
 
 #define ACPI_PHAT_ERRORS_FOUND          0
-- 
2.34.1


  reply	other threads:[~2026-06-03  6:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-03  6:33 [RFC PATCH 0/3] ACPI, x86/cpu/amd: Parse S5_REST_STATUS from ACPI PHAT on supported AMD platforms K Prateek Nayak
2026-06-03  6:33 ` K Prateek Nayak [this message]
2026-06-03  6:33 ` [RFC PATCH 2/3] ACPI: PHAT: Add generic helper to parse PHAT records K Prateek Nayak
2026-06-03 14:25   ` Mario Limonciello
2026-06-05  4:06     ` K Prateek Nayak
2026-06-03  6:33 ` [RFC PATCH 3/3] x86/cpu/amd: Fetch S5_RESET_STATUS from PHAT when supported K Prateek Nayak
2026-06-03 14:26   ` Mario Limonciello
2026-06-05  4:10     ` K Prateek Nayak
2026-06-03 14:37 ` [RFC PATCH 0/3] ACPI, x86/cpu/amd: Parse S5_REST_STATUS from ACPI PHAT on supported AMD platforms Rong Zhang
2026-06-05  4:02   ` K Prateek Nayak

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=20260603063317.13665-2-kprateek.nayak@amd.com \
    --to=kprateek.nayak@amd.com \
    --cc=Vilas.Sridharan@amd.com \
    --cc=acpica-devel@lists.linux.dev \
    --cc=bp@alien8.de \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=rafael@kernel.org \
    --cc=yazen.ghannam@amd.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

all inboxes | Powered by JetHome®