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: <174793004987.85440.5412777644593320433.b4-ty@kernel.org>
Date: Thu, 22 May 2025 16:10:00 +0000
From: Krzysztof WilczyƄski <kwilczynski@...nel.org>
To: Bjorn Helgaas <bhelgaas@...gle.com>,
	Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>,
	Bartosz Golaszewski <bartosz.golaszewski@...aro.org>,
	Jim Quinlan <james.quinlan@...adcom.com>
Cc: linux-pci@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] PCI/pwrctrl: Skip creating platform device if CONFIG_PCI_PWRCTL is not enabled

Hello,

> For platforms that do not use pwrctrl framework, the existence of the
> pwrctrl platform device will prevent the enumeration of the PCI devices due
> to the devlink dependency. This issue is reported on the systems using the
> pci-brcmstb.c driver, which doesn't use pwrctrl framework and handles the
> endpoint supplies on its own.
> 
> So, skip creating the pwrctrl platform device if the framework is not
> enabled. It is only a temporary solution to the issue. The actual fix would
> be to make pwrctrl framework feature complete (by supporting system PM with
> WOL) and convert the drivers that already support system PM like
> pci-brcmstb.c to use it.
> 
> [...]

Applied to pwrctrl, thank you!

[1/1] PCI/pwrctrl: Skip creating platform device if CONFIG_PCI_PWRCTL is not enabled
      https://git.kernel.org/pci/pci/c/afcae53871ce

	Krzysztof

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ