From: Niklas Cassel <cassel@kernel.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: "Krzysztof Wilczyński" <kw@linux.com>,
"Kishon Vijay Abraham I" <kishon@kernel.org>,
"Damien Le Moal" <dlemoal@kernel.org>,
linux-pci@vger.kernel.org, "Frank Li" <Frank.Li@nxp.com>
Subject: Re: [PATCH v2 2/2] misc: pci_endpoint_test: Add support for capabilities
Date: Tue, 3 Dec 2024 05:48:44 +0100 [thread overview]
Message-ID: <Z06NrM2vcIvulp6B@x1-carbon> (raw)
In-Reply-To: <20241130082119.44zpza3ehlwf3zct@thinkpad>
On Sat, Nov 30, 2024 at 01:51:19PM +0530, Manivannan Sadhasivam wrote:
> >
> > +static void pci_endpoint_test_get_capabilities(struct pci_endpoint_test *test)
> > +{
> > + struct pci_dev *pdev = test->pdev;
> > + struct device *dev = &pdev->dev;
> > + u32 caps;
> > + bool ep_can_do_unaligned_access;
> > +
> > + caps = pci_endpoint_test_readl(test, PCI_ENDPOINT_TEST_CAPS);
> > +
> > + ep_can_do_unaligned_access = caps & CAP_UNALIGNED_ACCESS;
> > + dev_dbg(dev, "CAP_UNALIGNED_ACCESS: %d\n", ep_can_do_unaligned_access);
>
> IDK if the users really need to know about this flag, nor it will assist in any
> debugging. Otherwise, I'd suggest to drop this debug print and just do:
>
> if (pci_endpoint_test_readl(test, PCI_ENDPOINT_TEST_CAPS))
> test->alignment = 0;
>
> - Mani
I do think that there is value in having a debug print that prints the
capabilities, especially if more caps are added in the future.
Let me send a v3 that dumps all caps (as hex) in a single print instead,
i.e. simply:
caps = pci_endpoint_test_readl(test, PCI_ENDPOINT_TEST_CAPS);
dev_dbg(dev, "PCI_ENDPOINT_TEST_CAPS: %#x\n", caps);
Kind regards,
Niklas
next prev parent reply other threads:[~2024-12-03 4:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-21 15:23 [PATCH v2 0/2] PCI endpoint test: Add support for capabilities Niklas Cassel
2024-11-21 15:23 ` [PATCH v2 1/2] PCI: endpoint: pci-epf-test: " Niklas Cassel
2024-11-21 19:38 ` Frank Li
2024-11-30 8:12 ` Manivannan Sadhasivam
2024-12-03 4:43 ` Niklas Cassel
2024-12-08 12:42 ` Manivannan Sadhasivam
2024-12-12 8:49 ` Niklas Cassel
2024-11-21 15:23 ` [PATCH v2 2/2] misc: pci_endpoint_test: " Niklas Cassel
2024-11-21 19:43 ` Frank Li
2024-11-25 15:17 ` Niklas Cassel
2024-11-30 8:21 ` Manivannan Sadhasivam
2024-12-03 4:48 ` Niklas Cassel [this message]
2024-11-26 13:20 ` [PATCH v2 0/2] PCI endpoint test: " Manivannan Sadhasivam
2024-11-27 11:23 ` Niklas Cassel
2024-11-27 11:32 ` Niklas Cassel
2024-11-27 11:55 ` Niklas Cassel
2024-11-27 11:40 ` Damien Le Moal
2024-11-30 8:05 ` Manivannan Sadhasivam
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=Z06NrM2vcIvulp6B@x1-carbon \
--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