From: Mark Brown <broonie@kernel.org>
To: Boris BREZILLON <b.brezillon.dev@gmail.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
Bo Shen <voice.shen@atmel.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"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: Mon, 24 Mar 2014 11:07:51 +0000 [thread overview]
Message-ID: <20140324110751.GH2269@sirena.org.uk> (raw)
In-Reply-To: <532FFE7B.2040507@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 465 bytes --]
On Mon, Mar 24, 2014 at 10:44:27AM +0100, Boris BREZILLON wrote:
> 1) Expose the wm8904 clock tree using the CCF (and its DT bindings)
We can't use the common clock framework in generic drivers since the
common clock framework isn't generally available.
> clocks {
> fll {
> compatible = "wolfson,wm8904-fll"
If we're adding compatible strings for non-reusable subcomponents of a
device like this we're doing something seriously broken.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2014-03-24 11:07 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
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 [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=20140324110751.GH2269@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