Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Niklas Cassel <cassel@kernel.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: bhelgaas@google.com, kw@linux.com, linux-pci@vger.kernel.org,
	Damien Le Moal <dlemoal@kernel.org>,
	Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
Subject: Re: [PATCH 3/4] misc: pci_endpoint_test: Let PCITEST_{READ,WRITE,COPY} set IRQ type automatically
Date: Wed, 26 Mar 2025 20:22:08 +0100	[thread overview]
Message-ID: <Z+RT4BxBzK68Crac@x1-carbon> (raw)
In-Reply-To: <bbgwy44nxf4h4hiycyue56uzfktfqzzwvw73bovtz42uklhuri@ejqrp5kjqbqh>

On Wed, Mar 26, 2025 at 09:47:18PM +0530, Manivannan Sadhasivam wrote:
> On Wed, Mar 26, 2025 at 10:39:50AM -0400, Niklas Cassel wrote:
> > 
> > Can all Qcom platforms raise INTx in EP mode?
> > 
> 
> Yes, all Qcom platforms support INTx. But if we start setting the flag to true,
> there is no need to set it to false as that would be the default value. So let's
> just set 'true' for INTx capable platforms and assume others as not supported. I
> know that you had added justification in the commit message, but I think we'd
> have to drop the below commit:
> 
> PCI: dw-rockchip: Endpoint mode cannot raise INTx interrupts

Well, with that logic, we should also remove the following:

$ git grep "msi_capable = false"
drivers/pci/controller/dwc/pcie-tegra194.c:     .msi_capable = false,

$ git grep "msix_capable = false"
drivers/pci/controller/dwc/pci-dra7xx.c:        .msix_capable = false,
drivers/pci/controller/dwc/pci-imx6.c:  .msix_capable = false,
drivers/pci/controller/dwc/pci-imx6.c:  .msix_capable = false,
drivers/pci/controller/dwc/pcie-artpec6.c:      .msix_capable = false,
drivers/pci/controller/dwc/pcie-qcom-ep.c:      .msix_capable = false,
drivers/pci/controller/dwc/pcie-rcar-gen4.c:    .msix_capable = false,
drivers/pci/controller/dwc/pcie-tegra194.c:     .msix_capable = false,
drivers/pci/controller/dwc/pcie-uniphier-ep.c:          .msix_capable = false,
drivers/pci/controller/dwc/pcie-uniphier-ep.c:          .msix_capable = false,
drivers/pci/controller/pcie-rcar-ep.c:  .msix_capable = false,
drivers/pci/controller/pcie-rockchip-ep.c:      .msix_capable = false,

Feel free to send patches that removes all:
{msi_capable,msix_capable,intx_capable}=false;

I will be happy to help out with reviews.

However, I'm slightly leaning towards thinking that there actually is some
value in _explicitly_ seeing that something is not supported.


Kind regards,
Niklas

  reply	other threads:[~2025-03-26 19:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-18 10:33 [PATCH 0/4] pci_endpoint_test: Let PCITEST_{READ,WRITE,COPY} set IRQ type automatically Niklas Cassel
2025-03-18 10:33 ` [PATCH 1/4] Revert "misc: pci_endpoint_test: Add support for PCITEST_IRQ_TYPE_AUTO" Niklas Cassel
2025-03-18 10:33 ` [PATCH 2/4] misc: pci_endpoint_test: Fetch supported IRQ types in CAPS register Niklas Cassel
2025-03-18 10:33 ` [PATCH 3/4] misc: pci_endpoint_test: Let PCITEST_{READ,WRITE,COPY} set IRQ type automatically Niklas Cassel
2025-03-20 15:27   ` Manivannan Sadhasivam
2025-03-21 13:27     ` Niklas Cassel
2025-03-22  2:24       ` Manivannan Sadhasivam
2025-03-22  5:31         ` Niklas Cassel
2025-03-23 11:34           ` Krzysztof Wilczyński
2025-03-24 18:20             ` Niklas Cassel
2025-03-24 18:36               ` Damien Le Moal
2025-03-26  6:23               ` Krzysztof Wilczyński
2025-03-26 14:39           ` Niklas Cassel
2025-03-26 16:17             ` Manivannan Sadhasivam
2025-03-26 19:22               ` Niklas Cassel [this message]
2025-03-26 19:58                 ` Bjorn Helgaas
2025-04-02  7:24                 ` Manivannan Sadhasivam
2025-03-18 10:33 ` [PATCH 4/4] selftests: pci_endpoint: Remove PCITEST_SET_IRQTYPE ioctls for read/write/copy Niklas Cassel

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=Z+RT4BxBzK68Crac@x1-carbon \
    --to=cassel@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=dlemoal@kernel.org \
    --cc=hayashi.kunihiko@socionext.com \
    --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