[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <44c7274f-8a5e-0235-413a-6c3260018601@linaro.org>
Date: Tue, 7 Feb 2023 17:13:50 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Lucas Tanure <lucas.tanure@...labora.com>,
David Rhodes <david.rhodes@...rus.com>,
Charles Keepax <ckeepax@...nsource.cirrus.com>,
Liam Girdwood <lgirdwood@...il.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Mark Brown <broonie@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>
Cc: alsa-devel@...a-project.org, devicetree@...r.kernel.org,
patches@...nsource.cirrus.com, linux-kernel@...r.kernel.org,
kernel@...labora.com
Subject: Re: [PATCH 2/2] Documentation: cs35l41: Shared boost properties
On 07/02/2023 16:46, Lucas Tanure wrote:
>>> + Shared boost allows two amplifiers to share a single boost circuit by
>>> + communicating on the MDSYNC bus. The passive amplifier does not control
>>> + the boost and receives data from the active amplifier. GPIO1 should be
>>> + configured for Sync when shared boost is used. Shared boost is not
>>> + compatible with External boost. Active amplifier requires
>>> + boost-peak-milliamp, boost-ind-nanohenry and boost-cap-microfarad.
>>> 0 = Internal Boost
>>> 1 = External Boost
>>> + 2 = Reserved
>>
>> How binding can be reserved? For what and why? Drop. 2 is shared active,
>> 3 is shared passive.
> 2 Is shared boost without VSPK switch, a mode not supported for new
> system designs. But there is laptops using it, so we need to keep
> supporting in the driver.
That's not the answer. 2 is nothing here, so it cannot be reserved.
Aren't you mixing now some register value with bindings?
Best regards,
Krzysztof
Powered by blists - more mailing lists