[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d803ead8-af3d-438a-9d9f-6194a7a5431a@kernel.org>
Date: Thu, 12 Dec 2024 08:31:58 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Ziyue Zhang <quic_ziyuzhan@...cinc.com>,
Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>
Cc: vkoul@...nel.org, kishon@...nel.org, dmitry.baryshkov@...aro.org,
abel.vesa@...aro.org, neil.armstrong@...aro.org, andersson@...nel.org,
konradybcio@...nel.org, robh@...nel.org, krzk+dt@...nel.org,
conor+dt@...nel.org, linux-arm-msm@...r.kernel.org,
linux-phy@...ts.infradead.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, quic_qianyu@...cinc.com
Subject: Re: [PATCH 1/3] dt-bindings: phy: qcom,qmp-pcie: add optional current
load properties
On 12/12/2024 08:29, Ziyue Zhang wrote:
>
>> In that case, I was wondering if the load set by the driver is going to vary
>> between platforms (boards) or not (question to Ziyue Zhang). If it varies
>> between SoC, then we can hardcode the load in driver based on compatible.
>
> Hi Mani, Krzystof
>
> Now we set the current to 165mA which is the max power supply the regulator
> can provide, so this is platform(boards) related. But we think PCIe PHY needs
Yeah, so that's the answer to what I asked just a second ago - you do
not put there device load. You put there regulator constraints.
> to set the current value we need, which is soc related.
So move it away from DT. I don't care what's in the driver, so you can
put there whatever fake value.
Best regards,
Krzysztof
Powered by blists - more mailing lists