From: Mark Brown <broonie@kernel.org>
To: ChiYuan Huang <cy_huang@richtek.com>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Allen Lin <allen_lin@richtek.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: codecs: rtq9128: Add TDM data source selection
Date: Wed, 27 Sep 2023 11:59:31 +0200 [thread overview]
Message-ID: <ZRP9Aw904ynL5Se/@finisterre.sirena.org.uk> (raw)
In-Reply-To: <20230927094637.GA25905@linuxcarl2.richtek.com>
[-- Attachment #1: Type: text/plain, Size: 929 bytes --]
On Wed, Sep 27, 2023 at 05:46:37PM +0800, ChiYuan Huang wrote:
> On Wed, Sep 27, 2023 at 11:13:22AM +0200, Mark Brown wrote:
> > Is this something that's going to be changing dynamically at runtime or
> > should this be a device property that's set either by firmware or when
> > we're doing the TDM setup? This sounds like something I'd expect to be
> > fixed by the board design.
> I may think one case if ASoC platform support multiple data source outputs
> that share the same bck/lcrk on different data pin. If it can be dynamically
> adjusted for the scenarios, this will keep the flexibility for the differet
> platform design.
Sure, but is that actually a practical design - or if someone is doing
this shouldn't it be joined up with the TDM configuration since with
just the control it'd only be possible to switch the pins but not change
the TDM layout? I'm not sure that this control works as a standalone
thing.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-09-27 9:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 2:06 cy_huang
2023-09-27 9:13 ` Mark Brown
2023-09-27 9:46 ` ChiYuan Huang
2023-09-27 9:59 ` Mark Brown [this message]
2023-09-27 10:19 ` ChiYuan Huang
2023-09-27 10:28 ` Mark Brown
2023-09-28 2:03 ` ChiYuan Huang
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=ZRP9Aw904ynL5Se/@finisterre.sirena.org.uk \
--to=broonie@kernel.org \
--cc=allen_lin@richtek.com \
--cc=alsa-devel@alsa-project.org \
--cc=cy_huang@richtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--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
all inboxes | Powered by JetHome®