From: Niklas Cassel <cassel@kernel.org>
To: "Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Kishon Vijay Abraham I" <kishon@kernel.org>
Cc: Damien Le Moal <dlemoal@kernel.org>,
linux-pci@vger.kernel.org, Frank Li <Frank.Li@nxp.com>
Subject: Re: [PATCH v3 0/2] PCI endpoint test: Add support for capabilities
Date: Thu, 12 Dec 2024 09:52:17 +0100 [thread overview]
Message-ID: <Z1qkQaVPMVz3vtmj@ryzen> (raw)
In-Reply-To: <20241203063851.695733-4-cassel@kernel.org>
On Tue, Dec 03, 2024 at 07:38:52AM +0100, Niklas Cassel wrote:
> Hello all,
>
> The pci-epf-test driver recently moved to the pci_epc_mem_map() API.
> This API call handle unaligned addresses seamlessly, if the EPC driver
> being used has implemented the .align_addr callback.
>
> This means that pci-epf-test no longer need any special padding to the
> buffers that is allocated on the host side. (This was only done in order
> to satisfy the EPC's alignment requirements.)
>
> In fact, to test that the pci_epc_mem_map() API is working as intended,
> it is important that the host side does not only provide buffers that
> are nicely aligned.
>
> However, since not all EPC drivers have implemented the .align_addr
> callback, add support for capabilities in pci-epf-test, and if the
> EPC driver implements the .align_addr callback, set a new
> CAP_UNALIGNED_ACCESS capability. If CAP_UNALIGNED_ACCESS is set, do not
> allocate overly sized buffers on the host side.
>
> For EPC drivers that have not implemented the .align_addr callback, this
> series will not introduce any functional changes.
>
>
> Kind regards,
> Niklas
>
>
> Changes since v2:
> -Picked up tags
> -Changed debug print to dump the CAPS register instead of having a print
> per capability.
>
>
> Niklas Cassel (2):
> PCI: endpoint: pci-epf-test: Add support for capabilities
> misc: pci_endpoint_test: Add support for capabilities
>
> drivers/misc/pci_endpoint_test.c | 19 +++++++++++++++++++
> drivers/pci/endpoint/functions/pci-epf-test.c | 19 +++++++++++++++++++
> 2 files changed, 38 insertions(+)
>
> --
> 2.47.1
>
Since this series has two R-b tags on both patches in the series,
any chance of getting this series picked up?
Kind regards,
Niklas
next prev parent reply other threads:[~2024-12-12 8:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 6:38 [PATCH v3 0/2] PCI endpoint test: Add support for capabilities Niklas Cassel
2024-12-03 6:38 ` [PATCH v3 1/2] PCI: endpoint: pci-epf-test: " Niklas Cassel
2025-01-18 20:34 ` Bjorn Helgaas
2025-01-20 12:00 ` Niklas Cassel
2025-01-20 15:44 ` Manivannan Sadhasivam
2025-01-20 16:07 ` Niklas Cassel
2024-12-03 6:38 ` [PATCH v3 2/2] misc: pci_endpoint_test: " Niklas Cassel
2024-12-12 8:52 ` Niklas Cassel [this message]
2024-12-19 14:20 ` [PATCH v3 0/2] PCI endpoint test: " Niklas Cassel
2024-12-22 20:58 ` Krzysztof Wilczyński
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=Z1qkQaVPMVz3vtmj@ryzen \
--to=cassel@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=dlemoal@kernel.org \
--cc=kishon@kernel.org \
--cc=kw@linux.com \
--cc=linux-pci@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
/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