From: Niklas Cassel <cassel@kernel.org>
To: Aksh Garg <a-garg7@ti.com>
Cc: linux-pci@vger.kernel.org, jingoohan1@gmail.com, mani@kernel.org,
lpieralisi@kernel.org, kwilczynski@kernel.org, robh@kernel.org,
bhelgaas@google.com, linux-kernel@vger.kernel.org,
s-vadapalli@ti.com, danishanwar@ti.com
Subject: Re: [PATCH 0/2] PCI: dwc: ep: Enhance multi-function endpoint support
Date: Wed, 21 Jan 2026 09:50:53 +0100 [thread overview]
Message-ID: <aXCTbb-0BWAWc2DB@ryzen> (raw)
In-Reply-To: <20260121054214.274429-1-a-garg7@ti.com>
On Wed, Jan 21, 2026 at 11:12:12AM +0530, Aksh Garg wrote:
> This series addresses multi-function endpoint configuration issues in
> the DWC PCIe controller driver. The changes enable proper operations
> for physical functions and enhance the multi-function endpoint support.
Considering that the DWC driver design has always been broken with regards
to multiple physical functions, as you explain yourself, the iATU to BAR
mapping has always been per controller, not per PF.
Thus, it would be nice if you explained how you have actually tested this.
Does the controller you are using have both Resizable and Programmable BARs?
Kind regards,
Niklas
next prev parent reply other threads:[~2026-01-21 8:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 5:42 [PATCH 0/2] PCI: dwc: ep: Enhance multi-function endpoint support Aksh Garg
2026-01-21 5:42 ` [PATCH 1/2] PCI: dwc: ep: Fix resizable BAR support for multi-PF configurations Aksh Garg
2026-01-21 9:58 ` Niklas Cassel
2026-01-21 11:40 ` Aksh Garg
2026-01-22 5:05 ` Aksh Garg
2026-01-22 5:56 ` Niklas Cassel
2026-01-22 6:20 ` Aksh Garg
2026-01-21 5:42 ` [PATCH 2/2] PCI: dwc: ep: Add per-PF BAR and iATU mapping support Aksh Garg
2026-01-21 9:20 ` Niklas Cassel
2026-01-21 11:35 ` [EXTERNAL] " Aksh Garg
2026-01-21 12:56 ` Niklas Cassel
2026-01-21 8:50 ` Niklas Cassel [this message]
2026-01-21 9:27 ` [PATCH 0/2] PCI: dwc: ep: Enhance multi-function endpoint support Niklas Cassel
2026-01-21 11:04 ` [EXTERNAL] " Aksh Garg
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=aXCTbb-0BWAWc2DB@ryzen \
--to=cassel@kernel.org \
--cc=a-garg7@ti.com \
--cc=bhelgaas@google.com \
--cc=danishanwar@ti.com \
--cc=jingoohan1@gmail.com \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=robh@kernel.org \
--cc=s-vadapalli@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