From: Mark Brown <broonie@kernel.org>
To: Zhang Yi <zhangyi@everest-semi.com>
Cc: alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
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 13:24:12 +0000 [thread overview]
Message-ID: <b76309c6-9f8d-48d3-b4ef-9b51efe06acc@sirena.org.uk> (raw)
In-Reply-To: <20250306072354.19987-1-zhangyi@everest-semi.com>
[-- Attachment #1: Type: text/plain, Size: 461 bytes --]
On Thu, Mar 06, 2025 at 03:23:54PM +0800, Zhang Yi wrote:
> > 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.
What do you mean by using it "as a single device"? Multiple CODECs on
the same link is the main use case for set_tdm_slot().
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-03-06 13:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 7:23 [PATCH v4 1/2] ASoC: codecs: add support for ES8389 Zhang Yi
2025-03-06 13:24 ` Mark Brown [this message]
-- 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=b76309c6-9f8d-48d3-b4ef-9b51efe06acc@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=amadeuszx.slawinski@linux.intel.com \
--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 \
--cc=zhangyi@everest-semi.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).