public inbox for linux-pci@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: linux-pci@vger.kernel.org, Martin Mares <mj@ucw.cz>,
	Ira Weiny <ira.weiny@intel.com>,
	Dan Williams <dan.j.williams@intel.com>,
	linuxarm@huawei.com
Subject: Re: [PATCH 1/1] pciutils: Add decode support for Data Object Exchange Extended Capability
Date: Tue, 18 Jan 2022 11:50:06 -0600	[thread overview]
Message-ID: <20220118175006.GA881466@bhelgaas> (raw)
In-Reply-To: <20220118172515.18839-1-Jonathan.Cameron@huawei.com>

On Tue, Jan 18, 2022 at 05:25:15PM +0000, Jonathan Cameron wrote:
> PCI Data Object Exchange [1] provides a mailbox interface used as the
> transport for various protocols defined by PCI-SIG and others. Make the
> limited information in config space available. Note the Read/Write
> Mailbox registers themselves are not currently parsed as the usefulness
> of accessing one dword of a protocol is probably limited.
> 
> In future, operating systems may provide means to safely query the
> supported protocols, but those have not yet been defined.
> 
> Example output:
> 
> Capabilities: [190 v1] Data Object Exchange
>                 DOECap: IntSup:+
>                         Interrupt Message Number: 001
>                 DOECtl: IntEn:-
>                 DOESta: Busy:- IntSta:- Error:- ObjectReady:-

Typical lspci output omits the ":" for each field, e.g., from your
test:

> +             DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
> +                     RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-

> [1] Data Object Exchange (DOE) ECN, approved 12 March 2020

DOE is included in the just-released PCIe r6.0 base spec, so we should
cite that (PCIe r6.0, sec 6.30, 7.9.24).

Bjorn

      reply	other threads:[~2022-01-18 17:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-18 17:25 [PATCH 1/1] pciutils: Add decode support for Data Object Exchange Extended Capability Jonathan Cameron
2022-01-18 17:50 ` Bjorn Helgaas [this message]

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=20220118175006.GA881466@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=dan.j.williams@intel.com \
    --cc=ira.weiny@intel.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=mj@ucw.cz \
    /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