[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a770c905-1c7e-41ce-a5dd-ea9c43e7a7ba@kernel.org>
Date: Fri, 20 Jun 2025 10:33:16 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Wenmeng Liu <quic_wenmliu@...cinc.com>, rfoss@...nel.org,
todor.too@...il.com, bryan.odonoghue@...aro.org, mchehab@...nel.org,
robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org,
andersson@...nel.org, konradybcio@...nel.org, akapatra@...cinc.com,
hariramp@...cinc.com
Cc: linux-media@...r.kernel.org, linux-arm-msm@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
quic_svankada@...cinc.com, quic_depengs@...cinc.com,
quic_vikramsa@...cinc.com
Subject: Re: [RFC PATCH 3/3] arm64: dts: qcom: qcs6490-rb3gen2: Add csiphy
current support
On 20/06/2025 06:07, Wenmeng Liu wrote:
> Add csiphy current value to support csiphy current load setting.
Why? Why doing this? Why is this needed?
Best regards,
Krzysztof
Powered by blists - more mailing lists