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 1/2] PCI: dwc: ep: Fix resizable BAR support for multi-PF configurations
Date: Thu, 22 Jan 2026 06:56:21 +0100 [thread overview]
Message-ID: <F757BE07-47EB-49B0-BEA6-03ED01C4497C@kernel.org> (raw)
In-Reply-To: <5f83a07a-ef35-47e9-b40f-fc7617a4488c@ti.com>
On 22 January 2026 06:05:47 CET, Aksh Garg <a-garg7@ti.com> wrote:
>>> --
>>> 2.34.1
>>>
>>
>>
>> Thank you for fixing this!
>>
>> Reviewed-by: Niklas Cassel <cassel@kernel.org>
>>
>>
>> You do need another patch in this series though, that fixes:
>> https://github.com/torvalds/linux/blob/v6.19-rc6/drivers/pci/controller/dwc/pcie-designware-ep.c#L972-L986
>>
>> As currently, ptm_cap_base is fetched using dw_pcie_find_ext_capability()
>> instead of your new dw_pcie_ep_find_ext_capability() which takes a func_no.
>>
>
>I examined the register spaces across different PFs to check whether all the PFs have the PTM capability registers, and confirmed that PTM capability registers exist only in PF0. PCIe r6.0 section 7.9.15 'Precision Time Management Extended Capability (PTM Capability)' states that " For Endpoints and Switch Upstream Ports that support PTM, this Capability is required in exactly one Function of the Upstream Port and that Capability controls the PTM behavior of all PTM capable Functions associated with that Upstream Port". This indicates that PTM capabilities are controller-level registers rather than per-function registers. Hence, in my opinion, ptm_cap_base does not require modification, since dw_pcie_find_ext_capability() and dw_pcie_*_dbi() already correctly access PF0's register space, which is the expected behavior for controller-level PTM management.
Hello Aksh,
Thanks a lot for digging in to this.
Since commit:
https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git/commit/?h=controller/dwc&id=86291f774fe8524178446cb2c792939640b4970c
Together with your patch,
there will only be a single call site in pcie-designware-ep.c that uses dw_pcie_*_dbi() instead of dw_pcie_ep_*_dbi() remaining.
Thus, I think we should at least add a comment explain why this is the only place in the whole file that can ignore func_no.
Kind regards,
Niklas
next prev parent reply other threads:[~2026-01-22 5:56 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 [this message]
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 ` [PATCH 0/2] PCI: dwc: ep: Enhance multi-function endpoint support Niklas Cassel
2026-01-21 9:27 ` 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=F757BE07-47EB-49B0-BEA6-03ED01C4497C@kernel.org \
--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
all inboxes | Powered by JetHome®