From: Alison Schofield <alison.schofield@intel.com>
To: Ben Widawsky <ben.widawsky@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>
Cc: linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org,
Linux ACPI <linux-acpi@vger.kernel.org>
Subject: [PATCH v2 0/2] CXL ACPI tables for object creation
Date: Tue, 15 Jun 2021 17:20:37 -0700 [thread overview]
Message-ID: <cover.1623800340.git.alison.schofield@intel.com> (raw)
Changes since v1 [1]:
- open code the cfmws restrictions to decode flags work (Dan)
- add range info on error messages when adding a decoder fails (Dan)
- make find_dport_by_dev() static (Dan)
- add linux-acpi to cc list (Dan)
[1] https://lore.kernel.org/linux-cxl/cover.1623705308.git.alison.schofield@intel.com/
Parse the ACPI CXL Early Discovery Table (CEDT) and use the CHBS & CFMWS
when creating port and decoder objects.
CHBS: CXL Host Bridge Structure - Patch 1
CFMWS: CXL Fixed Memory Window Structure - Patch 2
Alison Schofield (2):
cxl/acpi: Add the Host Bridge base address to CXL port objects
cxl/acpi: Use the ACPI CFMWS to create static decoder objects
drivers/cxl/acpi.c | 219 +++++++++++++++++++++++++++++++++++++++++++--
1 file changed, 213 insertions(+), 6 deletions(-)
base-commit: 195d5a63f0f9a47aa128a5050fe4ad7f5d27a901
--
2.26.2
next reply other threads:[~2021-06-16 0:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 0:20 Alison Schofield [this message]
2021-06-16 0:20 ` [PATCH v2 1/2] cxl/acpi: Add the Host Bridge base address to CXL port objects Alison Schofield
2021-06-16 16:08 ` Ben Widawsky
2021-06-16 23:11 ` Alison Schofield
2021-06-16 16:13 ` Jonathan Cameron
2021-06-16 23:16 ` Alison Schofield
2021-06-16 23:50 ` Dan Williams
2021-06-16 0:20 ` [PATCH v2 2/2] cxl/acpi: Use the ACPI CFMWS to create static decoder objects Alison Schofield
2021-06-16 16:17 ` Ben Widawsky
2021-06-16 16:32 ` Dan Williams
2021-06-16 23:21 ` Alison Schofield
2021-06-16 16:43 ` Jonathan Cameron
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.1623800340.git.alison.schofield@intel.com \
--to=alison.schofield@intel.com \
--cc=ben.widawsky@intel.com \
--cc=dan.j.williams@intel.com \
--cc=ira.weiny@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vishal.l.verma@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.