From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] ASoC: wm8904: add CCF support
Date: Fri, 21 Mar 2014 10:37:47 +0000 [thread overview]
Message-ID: <20140321103747.GK23372@e106331-lin.cambridge.arm.com> (raw)
In-Reply-To: <1395370262-23305-1-git-send-email-voice.shen@atmel.com>
On Fri, Mar 21, 2014 at 02:51:02AM +0000, Bo Shen wrote:
> Enable WM8904 to support common clock framework.
> And also supports different clk configuration.
>
> Signed-off-by: Bo Shen <voice.shen@atmel.com>
> ---
>
> Documentation/devicetree/bindings/sound/wm8904.txt | 57 ++++++++++++++++++++++
> sound/soc/codecs/wm8904.c | 39 +++++++++++++++
> 2 files changed, 96 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/sound/wm8904.txt
>
> diff --git a/Documentation/devicetree/bindings/sound/wm8904.txt b/Documentation/devicetree/bindings/sound/wm8904.txt
> new file mode 100644
> index 0000000..039374d
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/sound/wm8904.txt
> @@ -0,0 +1,57 @@
> +WM8904 audio CODEC
> +
> +This device supports I2C only.
> +
> +Required properties:
> + - compatible: "wlf,wm8904"
> + - reg: the I2C address of the device.
> +
> + if work with CCF, the following properties as required:
The DT shouldn't care about the software stack. You don't need to refer
to the CCF, just the clock bindings.
> + - wlf,sysclk-from-mclk: set the sys clock is driven from mclk,
Why can the kernel not decide this?
> + - 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?
> + - clocks: which clock generated clock to mclk.
> + - clock-names: the clock names use for retrieve.
NO. Is you wish to use clock-names, then define the set of names you
expect; clock-names are the names of the _input_ lines. The
documentation sets this out clearly. Take a look at
Documentation/devicetree/bindings/clock/clock-bindings.txt.
> + - 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?
Chers,
Mark.
next prev parent reply other threads:[~2014-03-21 10:37 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 [this message]
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
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=20140321103747.GK23372@e106331-lin.cambridge.arm.com \
--to=mark.rutland@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).