diff options
| author | Koichiro Den <den@valinux.co.jp> | 2026-04-14 23:15:13 +0900 |
|---|---|---|
| committer | Bjorn Helgaas <bhelgaas@google.com> | 2026-05-04 18:01:33 -0500 |
| commit | 8fda2dd209d34396cf49504e2c8dd55d182b14bc (patch) | |
| tree | b0fe55a2bafcccc2c95eb6874af7e9a927fa342d /rust/zerocopy/src/pointer/git@git.tavy.me:linux-stable.git | |
| parent | 0c3f82a584082a0d2e09b65e0a2e9cdcf9046d0d (diff) | |
PCI: endpoint: pci-epf-test: Reuse pre-exposed doorbell targets
pci-epf-test advertises the doorbell target to the RC as a BAR number
and an offset, and the RC rings the doorbell with a single DWORD MMIO
write.
Some doorbell backends may report that the doorbell target is already
exposed via a platform-owned fixed BAR (db_msg[0].bar/offset). In that
case, reuse the pre-exposed window and do not reprogram the BAR with
pci_epc_set_bar().
Also honor db_msg[0].irq_flags when requesting the doorbell IRQ, and
only restore the original BAR mapping on disable if pci-epf-test
programmed it.
Signed-off-by: Koichiro Den <den@valinux.co.jp>
Signed-off-by: Manivannan Sadhasivam <mani@kernel.org>
[bhelgaas: wrap comment]
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Tested-by: Niklas Cassel <cassel@kernel.org>
Reviewed-by: Frank Li <Frank.Li@nxp.com>
Link: https://patch.msgid.link/20260414141514.1341429-7-den@valinux.co.jp
Diffstat (limited to 'rust/zerocopy/src/pointer/git@git.tavy.me:linux-stable.git')
0 files changed, 0 insertions, 0 deletions
