From: Sergej Sawazki <ce3a@gmx.de>
To: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, lars@metafoo.de,
patches@opensource.wolfsonmicro.com, lgirdwood@gmail.com,
broonie@kernel.org, dan.carpenter@oracle.com
Subject: Re: [RFC PATCH] ASoC: wm8741: Allow master clock switching
Date: Fri, 05 Jun 2015 20:56:10 +0200 [thread overview]
Message-ID: <5571F0CA.4040405@gmx.de> (raw)
In-Reply-To: <20150605152219.GA32730@opensource.wolfsonmicro.com>
On 2015-06-05 at 05:22PM, Charles Keepax wrote:
>
> 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.
>
Good point, I will add it to v2.
>> + if (!wm8741->sysclk) {
>> + dev_err(codec->dev,
>> + "No MCLK configured, call set_sysclk() on hw_params\n");
>> + return -EINVAL;
>> + }
>
> Then you can keep this error check here and fail if we reach
> hw_params and still don't have a SYSCLK. You will probably need
> to provide a way to clear the SYSCLK though set_dai_sysclk as
> well.
Is snd_soc_dai_set_sysclk( , , 0, ) the right way to clear the SYSCLK?
Thanks,
Sergej
next prev parent reply other threads:[~2015-06-05 18:56 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
2015-06-05 18:56 ` Sergej Sawazki [this message]
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=5571F0CA.4040405@gmx.de \
--to=ce3a@gmx.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--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