[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6d6a7643-fad3-4d3f-b410-3eb6e033c29b@kernel.org>
Date: Sun, 1 Jun 2025 16:54:15 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Prasad Kumpatla <quic_pkumpatl@...cinc.com>,
Bjorn Andersson <andersson@...nel.org>,
Linus Walleij <linus.walleij@...aro.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
<conor+dt@...nel.org>, Srinivas Kandagatla <srini@...nel.org>,
Liam Girdwood <lgirdwood@...il.com>, Mark Brown <broonie@...nel.org>,
Konrad Dybcio <konradybcio@...nel.org>
Cc: cros-qcom-dts-watchers@...omium.org, linux-arm-msm@...r.kernel.org,
linux-gpio@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-sound@...r.kernel.org,
kernel@....qualcomm.com, Mohammad Rafi Shaik <quic_mohs@...cinc.com>
Subject: Re: [PATCH v4 5/8] arm64: dts: qcom: qcs6490-rb3gen2: Add WSA8830
speakers amplifier
On 01/06/2025 14:52, Prasad Kumpatla wrote:
>
>
> On 5/27/2025 5:29 PM, Krzysztof Kozlowski wrote:
>> On 27/05/2025 13:12, Prasad Kumpatla wrote:
>>> + left_spkr: speaker@0,1 {
>>> + compatible = "sdw10217020200";
>>> + reg = <0 1>;
>>> + powerdown-gpios = <&tlmm 158 GPIO_ACTIVE_LOW>;
>>> + #sound-dai-cells = <0>;
>>> + sound-name-prefix = "SpkrLeft";
>>> + #thermal-sensor-cells = <0>;
>>> + vdd-supply = <&vreg_l18b_1p8>;
>>> + qcom,port-mapping = <1 2 3 7>;
>>> + };
>>> +
>>> + right_spkr: speaker@0,2 {
>>> + compatible = "sdw10217020200";
>>> + reg = <0 2>;
>>> + powerdown-gpios = <&tlmm 158 GPIO_ACTIVE_LOW>;
>>
>>
>> This will fail during runtime. You never booted your DTS.
>
> No, its working fine, didn't seen any issues for far. Please help to
> provide at which point of line seen issue or provide more context to
> understand for me?
Okay, so the driver uses non-exclusive GPIO. Well, this should be really
fixed now. There is no excuse now "cannot work", because I fixed WSA884x
so new DTS using this method should not be allowed. Non-exclusive in
this driver is buggy and works by pure coincidence. You should see clear
warnings and issues during probe, because working device WILL be reset
by the other device.
Best regards,
Krzysztof
Powered by blists - more mailing lists