public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ChiYuan Huang <cy_huang@richtek.com>
To: Mark Brown <broonie@kernel.org>
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 17:46:37 +0800	[thread overview]
Message-ID: <20230927094637.GA25905@linuxcarl2.richtek.com> (raw)
In-Reply-To: <ZRPyMolOIjLBWXPC@finisterre.sirena.org.uk>

On Wed, Sep 27, 2023 at 11:13:22AM +0200, Mark Brown wrote:
> On Wed, Sep 27, 2023 at 10:06:16AM +0800, cy_huang@richtek.com wrote:
> 
> > Since rtq9128 can support 4 channel I2S mode audio data, there are two
> > dedicated data input pins for CH12 and CH34.  But in TDM mode, input
> > source was already drived on one data pin for multiple data slots. In
> > this case, only one input source is needed for TDM mode.
> > 
> > This patch is to add the data source pin selection for CH12 and CH34.
> 
> > +	SOC_ENUM("CH12 TDM Data Select", rtq9128_ch12_tdm_data_select_enum),
> > +	SOC_ENUM("CH34 TDM Data Select", rtq9128_ch34_tdm_data_select_enum),
> 
> 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.

Like as in most codecs, there could be mux design that can use to choose the 
dedicated data input. If we fixed in device property, the flexibility will be
missing. It's our original thought to have the control for the data select
mutiplexer.

  reply	other threads:[~2023-09-27  9:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-27  2:06 [PATCH] ASoC: codecs: rtq9128: Add TDM data source selection cy_huang
2023-09-27  9:13 ` Mark Brown
2023-09-27  9:46   ` ChiYuan Huang [this message]
2023-09-27  9:59     ` Mark Brown
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=20230927094637.GA25905@linuxcarl2.richtek.com \
    --to=cy_huang@richtek.com \
    --cc=allen_lin@richtek.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --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