[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <eabea4d4-366c-491a-bdcf-cbbfede66bd1@ixit.cz>
Date: Mon, 22 Dec 2025 15:01:23 +0100
From: David Heidelberg <david@...t.cz>
To: Konrad Dybcio <konrad.dybcio@....qualcomm.com>,
Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konradybcio@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
<conor+dt@...nel.org>, Vladimir Zapolskiy <vladimir.zapolskiy@...aro.org>,
Robert Foss <rfoss@...nel.org>
Cc: linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, phone-devel@...r.kernel.org
Subject: Re: [PATCH v2 2/2] arm64: dts: qcom: sdm845-db845c: Use pad fn
instead of defining own
On 18/12/2025 13:25, Konrad Dybcio wrote:
> On 12/17/25 12:39 PM, David Heidelberg via B4 Relay wrote:
>> From: David Heidelberg <david@...t.cz>
>>
>> Instead of defining own pad function for master clock, pick one offered
>> by sdm845 device-tree include.
>
> I'm a little bitter about the wording - the pad function here is "cam_mclk",
> whereas what you're doing is inheriting a common pinmux/pincfg node that
> refers to that function
>
> [...]
>
>> - mclk0-pins {
>> - pins = "gpio13";
>> - function = "cam_mclk";
>> -
>> - drive-strength = <16>;
>
> This patch changes the drive-strength (16 -> 2 mA)
>
> FWIW it's 2 on reference designs and Sony boards, check your
> downstream kernel
I don't have any. I'm fine with this patch not getting applied, but I'll
CC Robert who added the support, maybe he can verify.
David
>
> Konrad
--
David Heidelberg
Powered by blists - more mailing lists