From: Bjorn Andersson <andersson@kernel.org>
To: agross@kernel.org, jingoohan1@gmail.com,
konrad.dybcio@somainline.org,
Bjorn Andersson <andersson@kernel.org>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
gustavo.pimentel@synopsys.com, dmitry.baryshkov@linaro.org,
svarbanov@mm-sol.com, robh+dt@kernel.org, bhelgaas@google.com,
krzysztof.kozlowski+dt@linaro.org,
Manivannan Sadhasivam <mani@kernel.org>
Cc: johan@kernel.org, vkoul@kernel.org, devicetree@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: (subset) [PATCH v17 0/6] PCI: dwc: Fix higher MSI vectors handling
Date: Wed, 14 Sep 2022 22:36:52 -0500 [thread overview]
Message-ID: <166321302057.788007.12231815201009656469.b4-ty@kernel.org> (raw)
In-Reply-To: <20220707134733.2436629-1-dmitry.baryshkov@linaro.org>
On Thu, 7 Jul 2022 16:47:27 +0300, Dmitry Baryshkov wrote:
> I have replied with my Tested-by to the patch at [2], which has landed
> in the linux-next as the commit 20f1bfb8dd62 ("PCI: qcom:
> Add support for handling MSIs from 8 endpoints"). However lately I
> noticed that during the tests I still had 'pcie_pme=nomsi', so the
> device was not forced to use higher MSI vectors.
>
> After removing this option I noticed that hight MSI vectors are not
> delivered on tested platforms. After additional research I stumbled upon
> a patch in msm-4.14 ([1]), which describes that each group of MSI
> vectors is mapped to the separate interrupt. Implement corresponding
> mapping.
>
> [...]
Applied, thanks!
[6/6] arm64: dts: qcom: sm8250: provide additional MSI interrupts
commit: f2819650aab5b037e5e730c88abcd971e96a1637
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2022-09-15 3:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 13:47 [PATCH v17 0/6] PCI: dwc: Fix higher MSI vectors handling Dmitry Baryshkov
2022-07-07 13:47 ` [PATCH v17 1/6] PCI: dwc: Correct msi_irq condition in dw_pcie_free_msi() Dmitry Baryshkov
2022-07-07 13:47 ` [PATCH v17 2/6] PCI: dwc: Convert msi_irq to the array Dmitry Baryshkov
2022-07-07 13:47 ` [PATCH v17 3/6] PCI: dwc: split MSI IRQ parsing/allocation to a separate function Dmitry Baryshkov
2022-07-07 13:47 ` [PATCH v17 4/6] PCI: dwc: Handle MSIs routed to multiple GIC interrupts Dmitry Baryshkov
2022-07-07 13:47 ` [PATCH v17 5/6] dt-bindings: PCI: qcom: Support additional MSI interrupts Dmitry Baryshkov
2022-07-07 14:00 ` Johan Hovold
2022-07-14 1:02 ` Stanimir Varbanov
2022-07-07 13:47 ` [PATCH v17 6/6] arm64: dts: qcom: sm8250: provide " Dmitry Baryshkov
2022-07-14 11:58 ` [PATCH v17 0/6] PCI: dwc: Fix higher MSI vectors handling Dmitry Baryshkov
2022-07-22 9:04 ` Dmitry Baryshkov
2022-07-22 17:09 ` Bjorn Helgaas
2022-07-22 21:21 ` Dmitry Baryshkov
2022-09-15 3:36 ` Bjorn Andersson [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=166321302057.788007.12231815201009656469.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=agross@kernel.org \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=gustavo.pimentel@synopsys.com \
--cc=jingoohan1@gmail.com \
--cc=johan@kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=robh+dt@kernel.org \
--cc=svarbanov@mm-sol.com \
--cc=vkoul@kernel.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