From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Vlad Karpovich <vkarpovi@opensource.cirrus.com>
Cc: James Schulman <james.schulman@cirrus.com>,
David Rhodes <david.rhodes@cirrus.com>,
Richard Fitzgerald <rf@opensource.cirrus.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>, Rob Herring <robh+dt@kernel.org>,
<alsa-devel@alsa-project.org>, <patches@opensource.cirrus.com>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>
Subject: Re: [PATCH v3 3/4] ASoC: cs35l45: Connect DSP to the monitoring signals
Date: Fri, 1 Sep 2023 08:50:25 +0000 [thread overview]
Message-ID: <20230901085025.GB103419@ediswmail.ad.cirrus.com> (raw)
In-Reply-To: <20230831162042.471801-3-vkarpovi@opensource.cirrus.com>
On Thu, Aug 31, 2023 at 11:20:41AM -0500, Vlad Karpovich wrote:
> Link VMON, IMON, TEMPMON, VDD_BSTMON and VDD_BATTMON
> to DSP1. The CSPL firmware uses them for the speaker calibration
> and monitoring.
>
> Signed-off-by: Vlad Karpovich <vkarpovi@opensource.cirrus.com>
> ---
Acked-by: Charles Keepax <ckeepax@opensource.cirrus.com>
Thanks,
Charles
next prev parent reply other threads:[~2023-09-01 8:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 16:20 [PATCH v3 1/4] ASoC: cs35l45: Checks index of cs35l45_irqs[] Vlad Karpovich
2023-08-31 16:20 ` [PATCH v3 2/4] ASoC: cs35l45: Analog PCM Volume and Amplifier Mode controls Vlad Karpovich
2023-09-01 8:50 ` Charles Keepax
2023-08-31 16:20 ` [PATCH v3 3/4] ASoC: cs35l45: Connect DSP to the monitoring signals Vlad Karpovich
2023-09-01 8:50 ` Charles Keepax [this message]
2023-09-07 19:48 ` Rivera-Matos, Ricardo
2023-08-31 16:20 ` [PATCH v3 4/4] ASoC: cs35l45: Add AMP Enable Switch control Vlad Karpovich
2023-09-01 8:50 ` Charles Keepax
2023-09-07 19:49 ` Rivera-Matos, Ricardo
2023-09-11 0:27 ` Mark Brown
2023-09-01 8:48 ` [PATCH v3 1/4] ASoC: cs35l45: Checks index of cs35l45_irqs[] Charles Keepax
2023-09-07 19:40 ` Rivera-Matos, Ricardo
2023-09-11 23:57 ` Mark Brown
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=20230901085025.GB103419@ediswmail.ad.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=david.rhodes@cirrus.com \
--cc=devicetree@vger.kernel.org \
--cc=james.schulman@cirrus.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=perex@perex.cz \
--cc=rf@opensource.cirrus.com \
--cc=robh+dt@kernel.org \
--cc=tiwai@suse.com \
--cc=vkarpovi@opensource.cirrus.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).