From: Zhang Yi <zhangyi@everest-semi.com>
To: alsa-devel@alsa-project.org, broonie@kernel.org,
devicetree@vger.kernel.org
Cc: tiwai@suse.com, amadeuszx.slawinski@linux.intel.com,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org
Subject: RE: [PATCH v4 1/2] ASoC: codecs: add support for ES8389
Date: Thu, 6 Mar 2025 15:23:54 +0800 [thread overview]
Message-ID: <20250306072354.19987-1-zhangyi@everest-semi.com> (raw)
> > > set_tdm_slot()
>
> > We will register multiple codecs inside a single dai_link and differentiate these
> > codecs by of_node. And the adc_slot and the dac_slot may be different, they can
> > be decided by the user.If we use set_tdm_slot,the adc_slot and the dac_slot will
> > be same.
>
> No, the machine driver should be configuring different TDM slots for
> each device - that's the whole point of the API.
We are using multiple codecs as a single device.So we can't use set_tdm_slot to configure
different slots for multiple codecs under one device.
> > > > + ret = clk_prepare_enable(es8389->mclk);
> > > > + if (ret) {
> > > > + dev_err(codec->dev, "%s, unable to enable mclk\n", __func__);
> > > > + return ret;
> > > > + }
> > > > + }
>
> > > Making the use of a MCLK depend on the configuration of a TDM slot for
> > > the ADC seems *very* unusual, what's going on there?
>
> > Because we are associating multiple codecs under a single dai_link, we will be
> > executing probe and init many times during initialization.But MCLK only needs
> > to be used once.So we decided making the use of a MCLK depend on the configuration
> > of a TDM slot for the ADC
>
> No, each device should just get and enable the MCLK itself - the clock
> API does reference counting so there's no problem with this, it's normal
> for a clok to have multiple consumers.
ok,I'll fix it
next reply other threads:[~2025-03-06 7:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 7:23 Zhang Yi [this message]
2025-03-06 13:24 ` [PATCH v4 1/2] ASoC: codecs: add support for ES8389 Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2025-03-10 7:43 Zhang Yi
2025-03-10 3:03 Zhang Yi
2025-03-10 7:10 ` Krzysztof Kozlowski
2025-03-07 8:00 Zhang Yi
2025-03-05 9:18 Zhang Yi
2025-03-05 2:56 Zhang Yi
2025-03-05 13:06 ` Mark Brown
2025-03-04 11:47 [PATCH v4 0/2] " Zhang Yi
2025-03-04 11:47 ` [PATCH v4 1/2] " Zhang Yi
2025-03-04 19:08 ` 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=20250306072354.19987-1-zhangyi@everest-semi.com \
--to=zhangyi@everest-semi.com \
--cc=alsa-devel@alsa-project.org \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--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).