From: ALOK TIWARI <alok.a.tiwari@oracle.com>
To: "Frank Li" <Frank.Li@nxp.com>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Kishon Vijay Abraham I" <kishon@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Jon Mason" <jdmason@kudzu.us>,
"Dave Jiang" <dave.jiang@intel.com>,
"Allen Hubbe" <allenbh@gmail.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
ntb@lists.linux.dev, imx@lists.linux.dev
Subject: Re: [External] : [PATCH v4 2/3] PCI: endpoint: Add API pci_epf_assign_bar_space()
Date: Tue, 7 Oct 2025 00:25:59 +0530 [thread overview]
Message-ID: <c9efa64c-20d7-4aa6-815e-2be040480ff9@oracle.com> (raw)
In-Reply-To: <20250930-vntb_msi_doorbell-v4-2-ea2c94c6ff2e@nxp.com>
On 10/1/2025 2:09 AM, Frank Li wrote:
> +int pci_epf_assign_bar_space(struct pci_epf *epf, size_t size,
> + enum pci_barno bar,
> + const struct pci_epc_features *epc_features,
> + enum pci_epc_interface_type type,
> + dma_addr_t inbound_addr);
nit: Any particular reason for using inbound_addr instead of bar_addr ?
> +
> int pci_epf_align_inbound_addr(struct pci_epf *epf, enum pci_barno bar,
> u64 addr, dma_addr_t *base, size_t *off);
> int pci_epf_bind(struct pci_epf *epf);
Thanks,
Alok
next prev parent reply other threads:[~2025-10-06 18:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-30 20:39 [PATCH v4 0/3] pci: endpoint: vntb: add MSI doorbell support Frank Li
2025-09-30 20:39 ` [PATCH v4 1/3] PCI: endpoint: Add helper function pci_epf_get_bar_required_size() Frank Li
2025-10-06 10:43 ` Niklas Cassel
2025-10-07 18:26 ` Frank Li
2025-10-07 23:45 ` Niklas Cassel
2025-09-30 20:39 ` [PATCH v4 2/3] PCI: endpoint: Add API pci_epf_assign_bar_space() Frank Li
2025-10-06 18:55 ` ALOK TIWARI [this message]
2025-10-07 15:11 ` [External] : " Frank Li
2025-10-07 15:44 ` ALOK TIWARI
2025-09-30 20:39 ` [PATCH v4 3/3] PCI: endpoint: pci-epf-vntb: Add MSI doorbell support Frank Li
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=c9efa64c-20d7-4aa6-815e-2be040480ff9@oracle.com \
--to=alok.a.tiwari@oracle.com \
--cc=Frank.Li@nxp.com \
--cc=allenbh@gmail.com \
--cc=bhelgaas@google.com \
--cc=dave.jiang@intel.com \
--cc=imx@lists.linux.dev \
--cc=jdmason@kudzu.us \
--cc=kishon@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mani@kernel.org \
--cc=ntb@lists.linux.dev \
/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®