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 10:39:50 -0400	[thread overview]
Message-ID: <01676177-4757-41D3-BEC2-F61C0C7C3F69@kernel.org> (raw)
In-Reply-To: <2D76B56E-00A1-4AC1-B7B5-4ABEA53267CF@kernel.org>



Hello Mani,

On 22 March 2025 01:31:44 GMT-04:00, Niklas Cassel <cassel@kernel.org> wrote:
>
>BTW, can all Qcom platform raise INTx interrupts in EP mode?
>
>Bjorn did not like that I added intx_capable to epc_features without having any platform that sets it to true. I'm quite sure that many platforms can raise INTx interrupts.
>If all Qcom platforms can raise INTx interrupts,
>then I could set intx_capable to true in epc_features in qcom-ep.c, to address Bjorns comment.

Can all Qcom platforms raise INTx in EP mode?


Kind regards,
Niklas

  parent reply	other threads:[~2025-03-26 14:39 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 [this message]
2025-03-26 16:17             ` Manivannan Sadhasivam
2025-03-26 19:22               ` Niklas Cassel
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=01676177-4757-41D3-BEC2-F61C0C7C3F69@kernel.org \
    --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