From: Mark Brown <broonie@kernel.org>
To: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, lars@metafoo.de,
patches@opensource.wolfsonmicro.com, lgirdwood@gmail.com,
Sergej Sawazki <ce3a@gmx.de>,
dan.carpenter@oracle.com
Subject: Re: [RFC PATCH] ASoC: wm8741: Allow master clock switching
Date: Fri, 5 Jun 2015 17:56:45 +0100 [thread overview]
Message-ID: <20150605165645.GX14071@sirena.org.uk> (raw)
In-Reply-To: <20150605152219.GA32730@opensource.wolfsonmicro.com>
[-- Attachment #1.1: Type: text/plain, Size: 775 bytes --]
On Fri, Jun 05, 2015 at 04:22:19PM +0100, Charles Keepax wrote:
> On Fri, Jun 05, 2015 at 02:05:44PM +0200, Sergej Sawazki wrote:
> > The set of supported sample rates depends on the master clock supplied
> > to the codec. Allow the machine driver to set the required master clock
Please delete undeleted context when replying.
> I think rather than removing the constraints entirely here,
> perhaps just don't set any constraints if there is no SYSCLK yet.
> That way we get the benefits of the constraints for single clock
> systems (such as user-space being able to arrange appropriate
> software resampling) but those like yours can configure the clock
> later.
Yes, that's the ideal thing. The machine driver should reset the clock
back to zero when things go idle.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2015-06-05 16:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 12:05 [RFC PATCH] ASoC: wm8741: Allow master clock switching Sergej Sawazki
2015-06-05 15:22 ` Charles Keepax
2015-06-05 16:56 ` Mark Brown [this message]
2015-06-05 18:56 ` Sergej Sawazki
2015-06-05 19:00 ` 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=20150605165645.GX14071@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=ce3a@gmx.de \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=dan.carpenter@oracle.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=patches@opensource.wolfsonmicro.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