lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <176259710138.9726.16225246756188234387.b4-ty@kernel.org>
Date: Sat, 08 Nov 2025 15:48:21 +0530
From: Manivannan Sadhasivam <manivannan.sadhasivam@....qualcomm.com>
To: jingoohan1@...il.com, lpieralisi@...nel.org, kwilczynski@...nel.org,
        Manivannan Sadhasivam <manivannan.sadhasivam@....qualcomm.com>
Cc: robh@...nel.org, bhelgaas@...gle.com, linux-pci@...r.kernel.org,
        linux-kernel@...r.kernel.org, elder@...cstar.com
Subject: Re: [PATCH] PCI: dwc: Warn if the MSI ctrl doesn't have an
 associated platform IRQ in DT


On Thu, 30 Oct 2025 22:43:46 +0530, Manivannan Sadhasivam wrote:
> The internal MSI controller in DWC IPs supports multiple MSI ctrls, each
> capable of receiving 32 MSI vectors per ctrl. And each MSI ctrl requires a
> dedicated MSI platform IRQ in devicetree to function. Otherwise, MSIs won't
> be received from the endpoints.
> 
> Currently, dw_pcie_msi_host_init() only registers the IRQ handler if the
> MSI ctrl has the associated MSI platform IRQ in DT. But it doesn't warn if
> the IRQ is not available. This may cause developers/users to believe that
> the platform supports MSI vectors from all MSI ctrls, but it doesn't.
> 
> [...]

Applied, thanks!

[1/1] PCI: dwc: Warn if the MSI ctrl doesn't have an associated platform IRQ in DT
      commit: 571dd53fca80508de39cb2edc49a43be3ea5ae12

Best regards,
-- 
Manivannan Sadhasivam <mani@...nel.org>


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ