From: Mark Brown <broonie@kernel.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Bo Shen <voice.shen@atmel.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"b.brezillon.dev@gmail.com" <b.brezillon.dev@gmail.com>,
"nicolas.ferre@atmel.com" <nicolas.ferre@atmel.com>,
"linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFC PATCH] ASoC: wm8904: add CCF support
Date: Fri, 21 Mar 2014 11:55:11 +0000 [thread overview]
Message-ID: <20140321115511.GM11706@sirena.org.uk> (raw)
In-Reply-To: <20140321103747.GK23372@e106331-lin.cambridge.arm.com>
[-- Attachment #1: Type: text/plain, Size: 991 bytes --]
On Fri, Mar 21, 2014 at 10:37:47AM +0000, Mark Rutland wrote:
> On Fri, Mar 21, 2014 at 02:51:02AM +0000, Bo Shen wrote:
> > + - wlf,sysclk-from-mclk: set the sys clock is driven from mclk,
> Why can the kernel not decide this?
It can.
> > + - wlf,mclk-use-xtal: if the mclk is generated by crystal.
> > + if without this property, the mclk is generated from SOC.
> Huh? What exact property do you actually are about here?
This should just be omitted - based on the previous posting it's saying
if this is a fixed or variable rate clock.
> > + - wlf,mclk-freq: mclk's frequency
> If you expect mclk, you should be able to query this from it. You don't
> need a separate property.
> Unless this is a frequency to set it to? If so, why can the kernel not
> choose this?
Yes, quite - and even if it needs to be set explicitly the clock API
generic bindings should be able to support this (I *think* that is due
to go in during the next merge window but iddn't check yet).
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-03-21 11:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 2:51 [RFC PATCH] ASoC: wm8904: add CCF support Bo Shen
2014-03-21 10:37 ` Mark Rutland
2014-03-21 11:55 ` Mark Brown [this message]
2014-03-24 2:15 ` Bo Shen
2014-03-24 11:06 ` Mark Brown
2014-03-25 8:01 ` Bo Shen
2014-03-25 8:19 ` Bo Shen
2014-03-24 9:44 ` Boris BREZILLON
2014-03-24 11:07 ` 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=20140321115511.GM11706@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=b.brezillon.dev@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-sound@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nicolas.ferre@atmel.com \
--cc=voice.shen@atmel.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