linux-kernel - Re: [PATCH] dt-bindings: PCI: qcom: Allow 'vddpe-3v3-supply' again

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <ZqIJE5MSFFQ4iv-R@hovoldconsulting.com>
Date: Thu, 25 Jul 2024 10:13:07 +0200
From: Johan Hovold <johan@...nel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
Cc: Johan Hovold <johan+linaro@...nel.org>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	Lorenzo Pieralisi <lpieralisi@...nel.org>,
	Krzysztof Wilczyński <kw@...ux.com>,
	Rob Herring <robh@...nel.org>,
	Krzysztof Kozlowski <krzk+dt@...nel.org>,
	Conor Dooley <conor+dt@...nel.org>,
	Bjorn Andersson <andersson@...nel.org>,
	Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>,
	Abel Vesa <abel.vesa@...aro.org>, linux-arm-msm@...r.kernel.org,
	linux-pci@...r.kernel.org, devicetree@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] dt-bindings: PCI: qcom: Allow 'vddpe-3v3-supply' again

On Thu, Jul 25, 2024 at 10:49:41AM +0300, Dmitry Baryshkov wrote:
> On Thu, 25 Jul 2024 at 09:17, Johan Hovold <johan@...nel.org> wrote:
> > On Wed, Jul 24, 2024 at 08:22:54PM +0300, Dmitry Baryshkov wrote:
> > > On Tue, Jul 23, 2024 at 05:13:28PM GMT, Johan Hovold wrote:

> > > > Note that this property has been part of the Qualcomm PCIe bindings
> > > > since 2018 and would need to be deprecated rather than simply removed if
> > > > there is a desire to replace it with 'vpcie3v3' which is used for some
> > > > non-Qualcomm controllers.
> > >
> > > I think Rob Herring suggested [1] adding the property to the root port
> > > node rather than the host. If that suggestion still applies it might be
> > > better to enable the deprecated propertly only for the hosts, which
> > > already used it, and to define a new property at the root port.
> >
> > You seem to miss the point that this is just restoring status quo (and
> > that the property has not yet been deprecated).
> 
> You are restoring it for all platforms.

It is already part of the bindings for all platforms.

Johan