From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Lucas Tanure <lucas.tanure@collabora.com>,
David Rhodes <david.rhodes@cirrus.com>,
Charles Keepax <ckeepax@opensource.cirrus.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>
Cc: alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
patches@opensource.cirrus.com, linux-kernel@vger.kernel.org,
kernel@collabora.com
Subject: Re: [PATCH 2/2] Documentation: cs35l41: Shared boost properties
Date: Tue, 7 Feb 2023 17:48:59 +0100 [thread overview]
Message-ID: <56ce2617-4fd1-d597-a4dc-918654cdd3f6@linaro.org> (raw)
In-Reply-To: <4efe9796-6d3e-09d1-d5f7-cfb25a439061@collabora.com>
On 07/02/2023 17:34, Lucas Tanure wrote:
> On 07-02-2023 16:13, Krzysztof Kozlowski wrote:
>> 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
>>
>>
> I have added a new patch with propper documentation.
> And I would like to use 3 and 4 for shared boost as
> CS35L41_EXT_BOOST_NO_VSPK_SWITCH already exist as 2 and is used in the
> current driver.
I don't see CS35L41_EXT_BOOST_NO_VSPK_SWITCH in the bindings.
> The laptop that uses CS35L41_EXT_BOOST_NO_VSPK_SWITCH doesn't have the
> property "cirrus,boost-type", but to make everything consistent I would
> prefer to use 3 and 4 for the new boost types.
> Is that ok with you?
I don't see how it is related. The value does not exist, so whether
laptop has that property or not, is not really related, right?
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-02-07 16:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 10:40 [PATCH 0/2] Add CS35L41 shared boost feature Lucas Tanure
2023-02-07 10:40 ` [PATCH 1/2] ALSA: cs35l41: Add " Lucas Tanure
2023-02-07 11:48 ` Charles Keepax
2023-02-07 15:49 ` Lucas Tanure
2023-02-08 11:46 ` kernel test robot
2023-02-07 10:40 ` [PATCH 2/2] Documentation: cs35l41: Shared boost properties Lucas Tanure
2023-02-07 10:42 ` Krzysztof Kozlowski
2023-02-07 15:46 ` Lucas Tanure
2023-02-07 16:13 ` Krzysztof Kozlowski
2023-02-07 16:34 ` Lucas Tanure
2023-02-07 16:48 ` Krzysztof Kozlowski [this message]
2023-02-07 17:03 ` lucas.tanure
2023-02-08 10:23 ` Krzysztof Kozlowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56ce2617-4fd1-d597-a4dc-918654cdd3f6@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=david.rhodes@cirrus.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@collabora.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.tanure@collabora.com \
--cc=patches@opensource.cirrus.com \
--cc=perex@perex.cz \
--cc=robh+dt@kernel.org \
--cc=tiwai@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).