From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Wentao Liang <vulab@iscas.ac.cn>
Cc: <lgirdwood@gmail.com>, <broonie@kernel.org>, <perex@perex.cz>,
<tiwai@suse.com>, <u.kleine-koenig@baylibre.com>,
<patches@opensource.cirrus.com>, <linux-sound@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ASoC: Add initialization for wm8997 component
Date: Tue, 18 Mar 2025 09:39:31 +0000 [thread overview]
Message-ID: <Z9k/U+8TSVfSzFKw@opensource.cirrus.com> (raw)
In-Reply-To: <20250317140845.702-1-vulab@iscas.ac.cn>
On Mon, Mar 17, 2025 at 10:08:44PM +0800, Wentao Liang wrote:
> In wm8997_component_probe(), wm8997 should be initialized by
> arizona_init_gpio(). A proper implementation can be found in
> 'wm8998_component_probe()' where the wm8998 component is
> initialized with arizona_init_gpio().
>
> Signed-off-by: Wentao Liang <vulab@iscas.ac.cn>
> ---
> sound/soc/codecs/wm8997.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/sound/soc/codecs/wm8997.c b/sound/soc/codecs/wm8997.c
> index 5389c363b14e..ef8e09cc7211 100644
> --- a/sound/soc/codecs/wm8997.c
> +++ b/sound/soc/codecs/wm8997.c
> @@ -1066,6 +1066,8 @@ static int wm8997_component_probe(struct snd_soc_component *component)
> if (ret < 0)
> return ret;
>
> + arizona_init_gpio(component);
> +
This is not a missing initialisation, arizona_init_gpios hooks up
the signal detect feature. I am not certain it is worth adding the
signal detect feature to wm8997 at this point given I am not even
sure it shipped any units. If you do actually have a reason for
doing so, this is not sufficient to enable the feature. You need
to also add the Signal Detect widgets and routes.
Thanks,
Charles
prev parent reply other threads:[~2025-03-18 9:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 14:08 [PATCH] ASoC: Add initialization for wm8997 component Wentao Liang
2025-03-18 9:39 ` Charles Keepax [this message]
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=Z9k/U+8TSVfSzFKw@opensource.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=u.kleine-koenig@baylibre.com \
--cc=vulab@iscas.ac.cn \
/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