public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Yuquan Wang" <wangyuquan1236@phytium.com.cn>
To: Alejandro Lucero Palau <alucerop@amd.com>
Cc: marcin.juszkiewicz@linaro.org, ardb+tianocore@kernel.org,
	quic_llindhol@quicinc.com, Jonathan.Cameron@huawei.com,
	chenbaozi@phytium.com.cn, devel@edk2.groups.io,
	linux-cxl@vger.kernel.org
Subject: Re: [edk2-devel] [RFC PATCH edk2-platforms v4 0/1] add basic support for CXL on sbsa-ref
Date: Thu, 12 Dec 2024 11:51:54 +0800	[thread overview]
Message-ID: <Z1pd2nyOs2ryoZXt@phytium.com.cn> (raw)
In-Reply-To: <46b1b4e4-8588-46ae-8331-1ccb40a069ac@amd.com>

On Wed, Dec 11, 2024 at 03:40:03PM +0000, Alejandro Lucero Palau wrote:
> 
> On 12/10/24 10:36, Yuquan Wang wrote:
> > v3 -> v4:
> > - Align base addresses of CXL relevant Windows
> > 
> > v2 -> v3:
> > - PCDs values of pio, mmio32, mmio64 & ecam space for the independent cxl host
> > - CXL Bus range: 0x00 ~ 0xff
> > - Mcfg ecam structure for cxl
> > - Iort RC node for cxl
> > 
> > RFC because
> > - Many contents are ported from Jonathan' patch on qemu virt design
> > 
> > - Bring plenty of PCDs values
> > 
> > - Less experience and not particularly confident in ACPI area
> > 
> > This series leverages Jonathan's patches[1] to add acpi0016 & acpi0017 objects into the
> > previous DSDT table of sbsa-ref. Since my latest acpi0016 implementation model on qemu
> > side is a new host bridge qemu object rather than pxb-cxl, the cxl host(Segment 0001)
> > would have its own ECAM sapce. Meanwhile, this adds exclusive pio, mmio32 & mmio64 space
> > for cxl host.
> 
> 
> Hi Yuquan,
> 
> 
> Is there a roadmap for edk2 supporting other CXL features?
> 
Hi, Alejandro

Emmm. I have not find such edk2 roadmap (docs/webs/blog) yet. According to
what I've learnd, the edk2 upstream only support some head files which
define cxl registers structs and no cxl drivers have merged into upstream
now, and mostly system software's work haved been done in linux kernel.

Regard to cxl patches in edk2, there is a series of patches in reviewing to
support enabling cxl-type3 device as memory expander on Arm/RD platform[1].

Link:
[1]: https://edk2.groups.io/g/devel/message/109488
> 
> I have noticed UEFI extensions are not supported yet, specifically
> EFI_ADAPTER_INFO_CDAT_TYPE_GUID as an instance of
> EFI_ADAPTER_INFORMATION_PROTOCOL.
> 
> 
> Any feedback would be welcome.
> 
> 
> Thanks
> 
> 



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120897): https://edk2.groups.io/g/devel/message/120897
Mute This Topic: https://groups.io/mt/110023229/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



  reply	other threads:[~2024-12-12  3:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-10 10:36 [edk2-devel] [RFC PATCH edk2-platforms v4 0/1] add basic support for CXL on sbsa-ref Yuquan Wang
2024-12-10 10:36 ` [edk2-devel] [RFC PATCH edk2-platforms v4 1/1] SbsaQemu: Support basic CXL enablement Yuquan Wang
2024-12-11 15:40 ` [edk2-devel] [RFC PATCH edk2-platforms v4 0/1] add basic support for CXL on sbsa-ref Alejandro Lucero Palau via groups.io
2024-12-12  3:51   ` Yuquan Wang [this message]
2024-12-18  3:23     ` Yuquan Wang

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-list 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=Z1pd2nyOs2ryoZXt@phytium.com.cn \
    --to=devel@edk2.groups.io \
    /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