From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "dave@stgolabs.net" <dave@stgolabs.net>
Cc: "rafael@kernel.org" <rafael@kernel.org>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
"Jonathan.Cameron@Huawei.com" <Jonathan.Cameron@Huawei.com>,
"Williams, Dan J" <dan.j.williams@intel.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
"Moore, Robert" <robert.moore@intel.com>,
"bhelgaas@google.com" <bhelgaas@google.com>
Subject: Re: [PATCH v2 1/2] PCI/ACPI: Use CXL _OSC instead of PCIe _OSC
Date: Mon, 28 Mar 2022 19:04:04 +0000 [thread overview]
Message-ID: <c25d5f67db41ff10fe1e43ba62837114d388a3c6.camel@intel.com> (raw)
In-Reply-To: <20220328183515.nk3e3tr5ecn2amzf@offworld>
On Mon, 2022-03-28 at 11:35 -0700, Davidlohr Bueso wrote:
> On Fri, 25 Mar 2022, Vishal Verma wrote:
>
> > +static bool is_pcie(struct acpi_pci_root *root)
> > +{
> > + if (root->bridge_type == ACPI_BRIDGE_TYPE_PCIE)
> > + return true;
> > + return false;
> > +}
> >
> > -static acpi_status acpi_pci_run_osc(acpi_handle handle,
> > +static bool is_cxl(struct acpi_pci_root *root)
> > +{
> > + if (root->bridge_type == ACPI_BRIDGE_TYPE_CXL)
> > + return true;
> > + return false;
> > +}
>
> return root->bridge_type == TYPE
Oh, yes, of course - I'll fix up!
next prev parent reply other threads:[~2022-03-28 19:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-26 0:24 [PATCH v2 0/2] acpi: add support for CXL _OSC Vishal Verma
2022-03-26 0:24 ` [PATCH v2 1/2] PCI/ACPI: Use CXL _OSC instead of PCIe _OSC Vishal Verma
2022-03-28 18:35 ` Davidlohr Bueso
2022-03-28 19:04 ` Verma, Vishal L [this message]
2022-03-26 0:24 ` [PATCH v2 2/2] acpi/pci_root: negotiate CXL _OSC Vishal Verma
2022-03-28 18:23 ` Davidlohr Bueso
2022-03-28 18:51 ` Davidlohr Bueso
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=c25d5f67db41ff10fe1e43ba62837114d388a3c6.camel@intel.com \
--to=vishal.l.verma@intel.com \
--cc=Jonathan.Cameron@Huawei.com \
--cc=bhelgaas@google.com \
--cc=dan.j.williams@intel.com \
--cc=dave@stgolabs.net \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=robert.moore@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox