From: Ben Widawsky <firstname.lastname@example.org> To: email@example.com, firstname.lastname@example.org Cc: Ben Widawsky <email@example.com>, Alison Schofield <firstname.lastname@example.org>, Dan Williams <email@example.com>, Ira Weiny <firstname.lastname@example.org>, Jonathan Cameron <Jonathan.Cameron@Huawei.com>, Vishal Verma <email@example.com> Subject: [PATCH 0/7] cxl_pci refactor for reusability Date: Tue, 21 Sep 2021 15:04:52 -0700 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) Provide the ability to obtain CXL register blocks as discrete functionality. This functionality will become useful for other CXL drivers that need access to CXL register blocks. It is also in line with other additions to core which moves register mapping functionality. At the introduction of the CXL driver the only user of CXL MMIO was cxl_pci (then known as cxl_mem). As the driver has evolved it is clear that cxl_pci will not be the only entity that needs access to CXL MMIO. This series stops short of moving the generalized functionality into cxl_core for the sake of getting eyes on the important foundational bits sooner rather than later. The ultimate plan is to move much of the code into cxl_core. Via review of two previous patches  &  it has been suggested that the bits which are being used for DVSEC enumeration move into PCI core. As CXL core is soon going to require these, let's try to get the ball rolling now on making that happen. : https://email@example.com/ : https://firstname.lastname@example.org/ Ben Widawsky (7): cxl: Convert "RBI" to enum cxl/pci: Remove dev_dbg for unknown register blocks cxl/pci: Refactor cxl_pci_setup_regs cxl/pci: Make more use of cxl_register_map PCI: Add pci_find_dvsec_capability to find designated VSEC cxl/pci: Use pci core's DVSEC functionality ocxl: Use pci core's DVSEC functionality drivers/cxl/pci.c | 144 ++++++++++++++++++------------------- drivers/cxl/pci.h | 14 ++-- drivers/misc/ocxl/config.c | 13 +--- drivers/pci/pci.c | 32 +++++++++ include/linux/pci.h | 1 + 5 files changed, 113 insertions(+), 91 deletions(-) -- 2.33.0
next reply other threads:[~2021-09-21 22:05 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-21 22:04 Ben Widawsky [this message] 2021-09-21 22:04 ` [PATCH 1/7] cxl: Convert "RBI" to enum Ben Widawsky 2021-09-21 22:04 ` [PATCH 2/7] cxl/pci: Remove dev_dbg for unknown register blocks Ben Widawsky 2021-09-21 22:04 ` [PATCH 3/7] cxl/pci: Refactor cxl_pci_setup_regs Ben Widawsky 2021-09-21 23:39 ` Dan Williams 2021-09-22 4:31 ` Ben Widawsky 2021-09-21 22:04 ` [PATCH 4/7] cxl/pci: Make more use of cxl_register_map Ben Widawsky 2021-09-21 22:04 ` [PATCH 5/7] PCI: Add pci_find_dvsec_capability to find designated VSEC Ben Widawsky 2021-09-22 9:33 ` Frederic Barrat 2021-09-21 22:04 ` [PATCH 6/7] cxl/pci: Use pci core's DVSEC functionality Ben Widawsky 2021-09-21 22:04 ` [PATCH 7/7] ocxl: " Ben Widawsky 2021-09-22 0:44 ` Dan Williams 2021-09-22 9:38 ` Frederic Barrat 2021-09-21 22:14 ` [PATCH 0/7] cxl_pci refactor for reusability Ben Widawsky 2021-09-21 22:28 ` Dan Williams 2021-09-21 23:03 ` Ben Widawsky
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 \ --email@example.com \ --firstname.lastname@example.org \ --cc=Jonathan.Cameron@Huawei.com \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH 0/7] cxl_pci refactor for reusability' \ /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
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).