[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aOUtlUIcHE8JIO4j@lizhi-Precision-Tower-5810>
Date: Tue, 7 Oct 2025 11:11:17 -0400
From: Frank Li <Frank.li@....com>
To: ALOK TIWARI <alok.a.tiwari@...cle.com>
Cc: Manivannan Sadhasivam <mani@...nel.org>,
Krzysztof WilczyĆski <kwilczynski@...nel.org>,
Kishon Vijay Abraham I <kishon@...nel.org>,
Bjorn Helgaas <bhelgaas@...gle.com>, Jon Mason <jdmason@...zu.us>,
Dave Jiang <dave.jiang@...el.com>, Allen Hubbe <allenbh@...il.com>,
linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
ntb@...ts.linux.dev, imx@...ts.linux.dev
Subject: Re: [External] : [PATCH v4 2/3] PCI: endpoint: Add API
pci_epf_assign_bar_space()
On Tue, Oct 07, 2025 at 12:25:59AM +0530, ALOK TIWARI wrote:
>
>
> 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 ?
bar_addr is easy to confuse with RC side's bar windows's address. This one
means the ATU convert bar's inbound transfer to what EP side's address.
The below API also use term 'inbound_addr'.
It is not big deal. Manivannan or Niklas Cassel, do you have any perfer?
I am okay for both names.
Frank
>
> > +
> > 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
Powered by blists - more mailing lists