From: Steven Eckhoff <steven.eckhoff.opensource@gmail.com>
To: Charles Keepax <ckeepax@opensource.cirrus.com>
Cc: Mark Brown <broonie@kernel.org>,
linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
Takashi Iwai <tiwai@suse.com>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [alsa-devel] [PATCH v5] ASoC: TSCS42xx: Add support for Tempo Semiconductor's TSCS42xx audio CODEC
Date: Fri, 15 Dec 2017 10:08:50 -0600 [thread overview]
Message-ID: <20171215160848.iuycdjc7v5crbnxi@localhost.localdomain> (raw)
In-Reply-To: <20171215113654.a47ddf2bo44ziucl@localhost.localdomain>
On Fri, Dec 15, 2017 at 11:36:54AM +0000, Charles Keepax wrote:
> Hmm... might need to think about the case of whether to share a
> clock depends a little on what the hardware actually looks like.
>
> But basically my point is that writing random CODEC registers
> from the machine driver is not very nice. You want to be making
> use of ASoC calls etc. to have the CODEC driver apply the setting
> you want.
>
> For example you might call snd_soc_dai_set_fmt to configure
> who is master/slave, but you wouldn't want to write the bit
> that selects master mode on the CODEC directly from the machine
> driver.
I completely agree. ASoC calls would be better or maybe something in the
DT. The register setting needs to reflect what the physical connections
are. There is no ASRC on the chip so to have the ADC run at a different
rate you would need to use an extra bclk and lrclk and configure
it for that. The current version configures the chip so that the DAC and
ADCs run synchronously which only needs the bclk, lrclk, din, and dout
to function. Doing this in the machine driver is indeed broken as it is
making assumptions.
The next version will either set a sane default using your suggestion
or it will implement something through the device tree. I will think on
it a bit more.
next prev parent reply other threads:[~2017-12-15 16:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 19:54 Steven Eckhoff
2017-12-12 13:04 ` Charles Keepax
2017-12-12 13:10 ` Takashi Iwai
2017-12-12 16:54 ` Steven Eckhoff
2017-12-12 16:35 ` Steven Eckhoff
2017-12-12 16:32 ` Mark Brown
2017-12-12 21:31 ` Steven Eckhoff
2017-12-12 22:51 ` Steven Eckhoff
2017-12-13 6:20 ` Steven Eckhoff
2017-12-13 10:47 ` Mark Brown
2017-12-13 15:40 ` Steven Eckhoff
2017-12-14 9:32 ` [alsa-devel] " Charles Keepax
2017-12-14 22:36 ` Steven Eckhoff
2017-12-14 22:43 ` Steven Eckhoff
2017-12-15 11:36 ` Charles Keepax
2017-12-15 16:08 ` Steven Eckhoff [this message]
2017-12-17 19:23 ` Steven Eckhoff
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=20171215160848.iuycdjc7v5crbnxi@localhost.localdomain \
--to=steven.eckhoff.opensource@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®