From: lucas.tanure@collabora.com
To: Charles Keepax <ckeepax@opensource.cirrus.com>,
David Rhodes <david.rhodes@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>,
alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
patches@opensource.cirrus.com, linux-kernel@vger.kernel.org,
kernel@collabora.com
Subject: Re: [PATCH v2 3/5] ALSA: cs35l41: Add shared boost feature
Date: Wed, 8 Feb 2023 12:27:02 +0000 [thread overview]
Message-ID: <9d3181ff-5c08-697d-43fa-65bdc9544a26@collabora.com> (raw)
In-Reply-To: <20230208100927.GF36097@ediswmail.ad.cirrus.com>
On 2/8/23 10:09 AM, Charles Keepax <ckeepax@opensource.cirrus.com> wrote:
> On Tue, Feb 07, 2023 at 04:25:24PM +0000, 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.
> >
> > Shared Boost is not supported in HDA Systems.
> > Based on David Rhodes shared boost patches.
> >
> > Signed-off-by: Lucas Tanure <lucas.tanure@collabora.com>
> > ---
> > -int cs35l41_global_enable(struct regmap *regmap, enum cs35l41_boost_type b_type, int enable)
> > +int cs35l41_global_enable(struct regmap *regmap, enum cs35l41_boost_type b_type, int enable,
> > + struct completion *pll_lock)
> > {
> > int ret;
> > + unsigned int gpio1;
> >
> > switch (b_type) {
> > + case CS35L41_SHD_BOOST_ACTV:
> > + case CS35L41_SHD_BOOST_PASS:
> > + regmap_update_bits(regmap, CS35L41_PWR_CTRL3, CS35L41_SYNC_EN_MASK, 0);
> > +
> > + gpio1 = enable ? CS35L41_GPIO1_MDSYNC : CS35L41_GPIO1_HIZ;
> > + regmap_update_bits(regmap, CS35L41_GPIO_PAD_CONTROL, CS35L41_GPIO1_CTRL_MASK,
> > + gpio1 << CS35L41_GPIO1_CTRL_SHIFT);
> > +
> > + ret = regmap_update_bits(regmap, CS35L41_PWR_CTRL1, CS35L41_GLOBAL_EN_MASK,
> > + enable << CS35L41_GLOBAL_EN_SHIFT);
> > + usleep_range(3000, 3100);
> > + if (!enable)
> > + break;
> > +
> > + if (!pll_lock)
> > + return -EINVAL;
> > +
> > + ret = wait_for_completion_timeout(pll_lock, msecs_to_jiffies(1000));
> > + if (ret == 0) {
> > + ret = -ETIMEDOUT;
> > + } else {
> > + regmap_update_bits(regmap, CS35L41_PWR_CTRL3, CS35L41_SYNC_EN_MASK, 0);
Its wrong here. Should be enabling it not disable.
I will send v3.
> > + regmap_update_bits(regmap, CS35L41_PWR_CTRL1, CS35L41_GLOBAL_EN_MASK,
> > + 0 << CS35L41_GLOBAL_EN_SHIFT);
> > + usleep_range(3000, 3100);
> > + regmap_update_bits(regmap, CS35L41_PWR_CTRL1, CS35L41_GLOBAL_EN_MASK,
> > + 1 << CS35L41_GLOBAL_EN_SHIFT);
> > + usleep_range(3000, 3100);
> > + }
>
> This approach also makes me nervous, I was somewhat imagining the
> usage of regmap_multi_reg_write for this sequence was because it
> was very important that no other register writes could interleave
> in between these writes. But I don't know, so it could also have
> just been a random design choice. So we probably need David to
> confirm if that was the reason for the original code here.
>
> Thanks,
> Charles
>
next prev parent reply other threads:[~2023-02-08 12:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 16:25 [PATCH v2 0/5] Add CS35L41 shared boost feature Lucas Tanure
2023-02-07 16:25 ` [PATCH v2 1/5] ASoC: cs35l41: Only disable internal boost Lucas Tanure
2023-02-08 10:02 ` Charles Keepax
2023-02-07 16:25 ` [PATCH v2 2/5] ASoC: cs35l41: Refactor error release code Lucas Tanure
2023-02-08 10:03 ` Charles Keepax
2023-02-07 16:25 ` [PATCH v2 3/5] ALSA: cs35l41: Add shared boost feature Lucas Tanure
2023-02-08 10:09 ` Charles Keepax
2023-02-08 12:27 ` lucas.tanure [this message]
2023-02-07 16:25 ` [PATCH v2 4/5] ASoC: cs35l41: Document CS35l41 external boost without VSPK Lucas Tanure
2023-02-07 16:48 ` Krzysztof Kozlowski
2023-02-07 16:25 ` [PATCH v2 5/5] ASoC: cs35l41: Document CS35l41 shared boost Lucas Tanure
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=9d3181ff-5c08-697d-43fa-65bdc9544a26@collabora.com \
--to=lucas.tanure@collabora.com \
--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=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