public inbox for linux-pci@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
Cc: "Krzysztof Wilczyński" <kwilczynski@kernel.org>,
	"Kishon Vijay Abraham I" <kishon@kernel.org>,
	"Shuah Khan" <shuah@kernel.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Koichiro Den" <den@valinux.co.jp>,
	"Niklas Cassel" <cassel@kernel.org>,
	"Christian Bruel" <christian.bruel@foss.st.com>,
	fabrice.gasnier@foss.st.com, linux-pci@vger.kernel.org,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Frank Li" <Frank.Li@nxp.com>
Subject: Re: [PATCH v4 0/3] Skip subrange map tests on DWC iATU allocation failure
Date: Wed, 8 Apr 2026 14:40:09 -0500	[thread overview]
Message-ID: <20260408194009.GA308328@bhelgaas> (raw)
In-Reply-To: <177557111043.286575.12032515827207230571.b4-ty@b4>

On Tue, Apr 07, 2026 at 07:41:50PM +0530, Manivannan Sadhasivam wrote:
> On Tue, 07 Apr 2026 14:04:07 +0200, Christian Bruel wrote:
> > For platforms with a limited iATU inbound window entries, pci_epc_set_bar()
> > might fail to allocate the ATU entries for subrange maps requiring more
> > than 1 slot.
> > For the dwc controller, this failure is reported with -ENOSPC in
> > dw_pcie_ep_set_bar(). In this case, the epf test cannot be run and needs
> > to be skipped.
> > 
> > [...]
> 
> Applied, thanks!
> 
> [1/3] PCI: endpoint: pci-epf-test: Handle -ENOSPC in subrange_setup
>       commit: dfac277624c82b361dbb3e0fc57f577a270bebbb
> [2/3] misc: pci_endpoint_test: Handle -ENOSPC in subrange mapping test case
>       commit: a51c75fc48c2a0d2ead2d7e8c521de0423ec8dec
> [3/3] selftests: pci_endpoint: Skip BAR subrange test on -ENOSPC
>       commit: 2b729b7721bd4d0640b26790ea6c360c85a4af8c

I squashed these together because they need to be understood together.

I'm missing the details, but it seems unfortunate that the COMMAND_*,
STATUS_*, and CAP_* definitions have to be duplicated and presumably
kept in sync in drivers/misc/pci_endpoint_test.c and
drivers/pci/endpoint/functions/pci-epf-test.c.

      reply	other threads:[~2026-04-08 19:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-07 12:04 [PATCH v4 0/3] Skip subrange map tests on DWC iATU allocation failure Christian Bruel
2026-04-07 12:04 ` [PATCH v4 1/3] PCI: endpoint: pci-epf-test: Handle -ENOSPC in subrange_setup Christian Bruel
2026-04-07 12:04 ` [PATCH v4 2/3] misc: pci_endpoint_test: Handle -ENOSPC in subrange mapping test case Christian Bruel
2026-04-07 12:04 ` [PATCH v4 3/3] selftests: pci_endpoint: Skip BAR subrange test on -ENOSPC Christian Bruel
2026-04-07 14:11 ` [PATCH v4 0/3] Skip subrange map tests on DWC iATU allocation failure Manivannan Sadhasivam
2026-04-08 19:40   ` 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=20260408194009.GA308328@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=Frank.Li@nxp.com \
    --cc=arnd@arndb.de \
    --cc=bhelgaas@google.com \
    --cc=cassel@kernel.org \
    --cc=christian.bruel@foss.st.com \
    --cc=den@valinux.co.jp \
    --cc=fabrice.gasnier@foss.st.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kishon@kernel.org \
    --cc=kwilczynski@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=manivannan.sadhasivam@oss.qualcomm.com \
    --cc=shuah@kernel.org \
    /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