From: Mark Brown <broonie@kernel.org>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Oder Chiou <oder_chiou@realtek.com>,
Bard Liao <bardliao@realtek.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
Flove <flove@realtek.com>
Subject: Re: [PATCH] ASoC: rt5640: add ASRC support
Date: Mon, 30 Jun 2014 15:50:56 +0100 [thread overview]
Message-ID: <20140630145056.GZ23300@sirena.org.uk> (raw)
In-Reply-To: <53B13FB2.1090304@metafoo.de>
[-- Attachment #1.1: Type: text/plain, Size: 769 bytes --]
On Mon, Jun 30, 2014 at 12:45:06PM +0200, Lars-Peter Clausen wrote:
> On 06/30/2014 08:09 AM, Bard Liao wrote:
> >To turn on/off rt5640's ASRC function is not decided by only one
> >condition. To make it flexible, I prefer to use a control to enable/
> >disable ASRC function.
> But the driver should be able to autodetect those conditions, shouldn't it?
That depends; we're back to issues with the clock API again. If the
device is slave on an interface which is ultimately clocked from a clock
which is also fed directly to the device it's not going to be able to
tell that the two are synchronous even if we have the common clock API.
However this still shouldn't be exposed directly to userspace since the
clocking is generally handled entirely in the kernel.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2014-06-30 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 10:58 [PATCH] ASoC: rt5640: add ASRC support bardliao
2014-06-27 14:05 ` Lars-Peter Clausen
2014-06-30 6:09 ` Bard Liao
2014-06-30 10:45 ` Lars-Peter Clausen
2014-06-30 14:50 ` Mark Brown [this message]
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=20140630145056.GZ23300@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bardliao@realtek.com \
--cc=flove@realtek.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=oder_chiou@realtek.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).