From: Niklas Cassel <cassel@kernel.org>
To: Manikanta Maddireddy <mmaddireddy@nvidia.com>
Cc: bhelgaas@google.com, lpieralisi@kernel.org,
kwilczynski@kernel.org, mani@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
thierry.reding@gmail.com, jonathanh@nvidia.com,
kishon@kernel.org, arnd@arndb.de, gregkh@linuxfoundation.org,
Frank.Li@nxp.com, den@valinux.co.jp, hongxing.zhu@nxp.com,
jingoohan1@gmail.com, vidyas@nvidia.com, 18255117159@163.com,
linux-pci@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] misc: pci_endpoint_test: Add Tegra194 and Tegra234 device table entries
Date: Wed, 25 Feb 2026 19:16:24 +0100 [thread overview]
Message-ID: <aZ88eNfiiMD8a7Gr@ryzen> (raw)
In-Reply-To: <aZ84XkM3RzJLCIYX@ryzen>
On Wed, Feb 25, 2026 at 06:59:02PM +0100, Niklas Cassel wrote:
> On Mon, Feb 23, 2026 at 01:04:56AM +0530, Manikanta Maddireddy wrote:
> > Add PCI device IDs and test data for Tegra194 (0x1ad4) and Tegra234
> > (0x229b) endpoints so pci_endpoint_test can bind and run on these
> > controllers (64K BAR alignment).
> >
> > Signed-off-by: Manikanta Maddireddy <mmaddireddy@nvidia.com>
> > ---
> > drivers/misc/pci_endpoint_test.c | 13 +++++++++++++
> > 1 file changed, 13 insertions(+)
> >
> > diff --git a/drivers/misc/pci_endpoint_test.c b/drivers/misc/pci_endpoint_test.c
> > index f166b6fea698..43545dbad26f 100644
> > --- a/drivers/misc/pci_endpoint_test.c
> > +++ b/drivers/misc/pci_endpoint_test.c
> > @@ -106,6 +106,9 @@
> >
> > #define PCI_DEVICE_ID_ROCKCHIP_RK3588 0x3588
> >
> > +#define PCI_DEVICE_ID_NVIDIA_TEGRA194_EP 0x1ad4
> > +#define PCI_DEVICE_ID_NVIDIA_TEGRA234_EP 0x229b
> > +
> > static DEFINE_IDA(pci_endpoint_test_ida);
> >
> > #define to_endpoint_test(priv) container_of((priv), struct pci_endpoint_test, \
> > @@ -1202,6 +1205,10 @@ static const struct pci_endpoint_test_data rk3588_data = {
> > .alignment = SZ_64K,
> > };
> >
> > +static const struct pci_endpoint_test_data tegra_ep_data = {
> > + .alignment = SZ_64K,
> > +};
>
> An explcit .alignment is not needed anymore, it was only needed before we
> introduced capabilities. New entries should be added without an explicit
> alignment, since it will be provided by the capabilties register.
Sorry, small clarification:
Allocating extra large buffers on the host side (.alignment) is not needed
anymore, since pci-epf-test (the endpoint side) nowadays can do unaligned
accesses using pci_epc_mem_map()/unmap().
See:
ce1dfe6d3289 ("PCI: endpoint: Introduce pci_epc_mem_map()/unmap()")
08cac1006bfc ("PCI: endpoint: test: Use pci_epc_mem_map/unmap()")
8a02612f8566 ("PCI: endpoint: pci-epf-test: Add support for capabilities")
Kind regards,
Niklas
prev parent reply other threads:[~2026-02-25 18:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-22 19:34 [PATCH 0/4] PCI: endpoint: Add Tegra194/234 BAR layout and pci_endpoint_test support Manikanta Maddireddy
2026-02-22 19:34 ` [PATCH 1/4] PCI: endpoint: Add reserved region type for MSI-X Table and PBA Manikanta Maddireddy
2026-02-25 17:21 ` Niklas Cassel
2026-02-22 19:34 ` [PATCH 2/4] PCI: tegra194: Make BAR0 programmable and remove 1MB size limit Manikanta Maddireddy
2026-02-25 17:31 ` Niklas Cassel
2026-03-03 7:19 ` Manikanta Maddireddy
2026-02-22 19:34 ` [PATCH 3/4] PCI: tegra194: Expose BAR2 (MSI-X) and BAR4 (DMA) as 64-bit BAR_RESERVED Manikanta Maddireddy
2026-02-25 17:51 ` Niklas Cassel
2026-02-22 19:34 ` [PATCH 4/4] misc: pci_endpoint_test: Add Tegra194 and Tegra234 device table entries Manikanta Maddireddy
2026-02-25 17:58 ` Niklas Cassel
2026-02-25 18:16 ` Niklas Cassel [this message]
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=aZ88eNfiiMD8a7Gr@ryzen \
--to=cassel@kernel.org \
--cc=18255117159@163.com \
--cc=Frank.Li@nxp.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=den@valinux.co.jp \
--cc=gregkh@linuxfoundation.org \
--cc=hongxing.zhu@nxp.com \
--cc=jingoohan1@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=mmaddireddy@nvidia.com \
--cc=robh@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=vidyas@nvidia.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