From: Niklas Cassel <cassel@kernel.org>
To: Aksh Garg <a-garg7@ti.com>
Cc: linux-pci@vger.kernel.org, linux-doc@vger.kernel.org,
bhelgaas@google.com, corbet@lwn.net,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, s-vadapalli@ti.com,
danishanwar@ti.com, srk@ti.com
Subject: Re: [RFC PATCH 3/4] PCI/DOE: Add DOE mailbox support for endpoint functions
Date: Fri, 13 Feb 2026 14:21:32 +0100 [thread overview]
Message-ID: <aY8lXB5JB3ffiUlK@fedora> (raw)
In-Reply-To: <20260213123603.420941-4-a-garg7@ti.com>
On Fri, Feb 13, 2026 at 06:06:02PM +0530, Aksh Garg wrote:
(snip)
> diff --git a/drivers/pci/Kconfig b/drivers/pci/Kconfig
> index e3f848ffb52a..2a57a314054c 100644
> --- a/drivers/pci/Kconfig
> +++ b/drivers/pci/Kconfig
> @@ -146,6 +146,20 @@ config PCI_DOE
> Say Y here if you want be able to communicate with PCIe DOE
> mailboxes.
>
> +config PCI_DOE_EP
> + bool "PCI Endpoint Data Object Exchange (DOE) support"
> + depends on PCI_ENDPOINT
> + help
> + This enables support for Data Object Exchange (DOE) protocol
> + on PCI Endpoint controllers. It provides a communication
> + mechanism through mailboxes, primarily used for PCIe security
> + features.
> +
> + Say Y here if you want be able to communicate using PCIe DOE
> + mailboxes.
> +
> + If unsure, say N.
> +
I think this new Kconfig should live in:
drivers/pci/endpoint/Kconfig
Kind regards,
Niklas
next prev parent reply other threads:[~2026-02-13 13:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 12:35 [RFC PATCH 0/4] PCI: Add DOE support for endpoint Aksh Garg
2026-02-13 12:36 ` [RFC PATCH 1/4] PCI: Add documentation for DOE endpoint support Aksh Garg
2026-02-13 20:33 ` Niklas Cassel
2026-02-18 11:21 ` Aksh Garg
2026-02-13 12:36 ` [RFC PATCH 2/4] PCI/DOE: Move common definitions to the header file Aksh Garg
2026-02-22 13:01 ` Lukas Wunner
2026-02-23 7:30 ` Aksh Garg
2026-02-13 12:36 ` [RFC PATCH 3/4] PCI/DOE: Add DOE mailbox support for endpoint functions Aksh Garg
2026-02-13 13:21 ` Niklas Cassel [this message]
2026-02-18 4:28 ` Alistair Francis
2026-03-04 14:18 ` Manivannan Sadhasivam
2026-03-06 12:14 ` Aksh Garg
2026-02-22 13:06 ` Lukas Wunner
2026-02-23 10:44 ` Aksh Garg
2026-03-04 14:17 ` Manivannan Sadhasivam
2026-03-06 8:17 ` Aksh Garg
2026-02-13 12:36 ` [RFC PATCH 4/4] PCI: Document APIs for endpoint DOE implementation Aksh Garg
2026-02-13 13:16 ` [RFC PATCH 0/4] PCI: Add DOE support for endpoint Niklas Cassel
2026-03-04 14:22 ` Manivannan Sadhasivam
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=aY8lXB5JB3ffiUlK@fedora \
--to=cassel@kernel.org \
--cc=a-garg7@ti.com \
--cc=bhelgaas@google.com \
--cc=corbet@lwn.net \
--cc=danishanwar@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=s-vadapalli@ti.com \
--cc=srk@ti.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