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: <ZqI26iACl_mQX-zG@hovoldconsulting.com>
Date: Thu, 25 Jul 2024 13:28:42 +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 01:24:27PM +0300, Dmitry Baryshkov wrote:
> On Thu, Jul 25, 2024 at 11:05:07AM GMT, Johan Hovold wrote:
> > On Thu, Jul 25, 2024 at 11:57:39AM +0300, Dmitry Baryshkov wrote:
> > > On Thu, Jul 25, 2024 at 10:13:07AM GMT, Johan Hovold wrote:
> > 
> > > > It is already part of the bindings for all platforms.
> > > 
> > > It is not, it is enabled only for sc7280 and sc8280xp. 
> > 
> > No, that's both incorrect and irrelevant. It is used by msm8996 and
> > older platforms by in-kernel DTs as well. But the point is that is has
> > been part of the bindings an cannot simply be removed as there can be
> > out-of-tree DTs that are correctly using this property for any of these
> > platforms.
> 
> It can not be removed from the driver, but it definitely can be remove
> from bindings.

You apparently ignored the word "simply" in "cannot simply be removed".

Johan