From: Robert Kiraly <me@boldcoder.com>
To: linux-acpi@vger.kernel.org, linux-cxl@vger.kernel.org
Cc: Len Brown <lenb@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Dan Williams <dan.j.williams@intel.com>
Subject: Patch: Make ACPI subsystem provide CEDT table
Date: Thu, 27 Jan 2022 02:15:23 -0800 [thread overview]
Message-ID: <a20337bb-9e83-e387-7d10-a2843f7286b3@boldcoder.com> (raw)
In-Reply-To: <82f254a1-c765-0a87-f017-8c07c8ef07cd@boldcoder.com>
This is a simple ACPI patch. I'm submitting a revised version to
linux-acpi per Rafael Wysocki and linux-cxl per Dan Williams.
Thunderbird has added CRs so "patch -p1 -l" is needed.
==== start of patch ====
Subject: Make ACPI subsystem provide CEDT table
Signed-off-by: Robert Kiraly <me@boldcoder.com>
This is a simple patch to the ACPI subsystem. The patch adds ACPI
_SIG_CEDT to table_sigs[] in "drivers/acpi/tables.c".
Presently, CXL code isn't able to make use of the CEDT table at
the initrd stage. Subsequent to the change, the CEDT table can be
used.
If a developer plans to use the CEDT table to program the CXL
ports, this change is needed. Otherwise, it isn't expected to
make a difference.
I certify compliance with Developer’s Certificate of Origin 1.1
as listed in:
https://www.kernel.org/doc/html/v4.10/process/submitting-patches.
html
--- linux-5.16.old/drivers/acpi/tables.c
+++ linux-5.16/drivers/acpi/tables.c
@@ -500,7 +500,7 @@
ACPI_SIG_WDDT, ACPI_SIG_WDRT, ACPI_SIG_DSDT, ACPI_SIG_FADT,
ACPI_SIG_PSDT, ACPI_SIG_RSDT, ACPI_SIG_XSDT, ACPI_SIG_SSDT,
ACPI_SIG_IORT, ACPI_SIG_NFIT, ACPI_SIG_HMAT, ACPI_SIG_PPTT,
- ACPI_SIG_NHLT };
+ ACPI_SIG_CEDT, ACPI_SIG_NHLT };
#define ACPI_HEADER_SIZE sizeof(struct acpi_table_header)
==== end of patch ====
next prev parent reply other threads:[~2022-01-27 10:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1b871357-2231-336d-099c-cdccae03f837@boldcoder.com>
2022-01-25 6:30 ` Patch: Make ACPI subsystem provide CEDT table Robert Kiraly
2022-01-25 14:49 ` Rafael J. Wysocki
2022-01-26 3:12 ` Robert Kiraly
2022-01-26 15:55 ` Rafael J. Wysocki
2022-01-27 10:15 ` Robert Kiraly [this message]
2022-02-04 18:45 ` Rafael J. Wysocki
2022-02-04 19:34 ` Robert Kiraly
2022-01-12 23:07 Robert Kiraly
2022-01-13 11:38 ` Rafael J. Wysocki
2022-01-20 18:49 ` Rafael J. Wysocki
2022-01-20 19:06 ` Dan Williams
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=a20337bb-9e83-e387-7d10-a2843f7286b3@boldcoder.com \
--to=me@boldcoder.com \
--cc=dan.j.williams@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=rafael@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;
as well as URLs for NNTP newsgroup(s).