devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: "rob.herring@calxeda.com" <rob.herring@calxeda.com>,
	Pawel Moll <Pawel.Moll@arm.com>,
	Stephen Warren <swarren@wwwdotorg.org>,
	Ian Campbell <ian.campbell@citrix.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"patches@opensource.wolfsonmicro.com"
	<patches@opensource.wolfsonmicro.com>,
	Mark Brown <broonie@linaro.org>
Subject: Re: [PATCH] ASoC: wm8994: Add clock bindings to the device tree
Date: Thu, 25 Jul 2013 16:46:27 +0100	[thread overview]
Message-ID: <20130725154627.GA22291@e106331-lin.cambridge.arm.com> (raw)
In-Reply-To: <1374762668-5037-1-git-send-email-broonie@kernel.org>

On Thu, Jul 25, 2013 at 03:31:08PM +0100, Mark Brown wrote:
> From: Mark Brown <broonie@linaro.org>
> 
> Due to the variable availability of the clock API there is no code in the
> driver to use these at present, for the time being the machine drivers
> will need to handle requesting clocks.
> 
> Signed-off-by: Mark Brown <broonie@linaro.org>

Do these two clock inputs exist for all of wm1811, wm8994, and wm8958?

If I've read the context correctly, these are optional. Does this mean
that if not listed that an OS can assume they are already configured and
active? It would be nice to document that.

Otherwise, this looks sensible:

Acked-by: Mark Rutland <mark.rutland@arm.com>

Thanks,
Mark.

> ---
>  Documentation/devicetree/bindings/sound/wm8994.txt | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/sound/wm8994.txt b/Documentation/devicetree/bindings/sound/wm8994.txt
> index f2f3e80..e045e90 100644
> --- a/Documentation/devicetree/bindings/sound/wm8994.txt
> +++ b/Documentation/devicetree/bindings/sound/wm8994.txt
> @@ -32,6 +32,10 @@ Optional properties:
>      The second cell is the flags, encoded as the trigger masks from
>      Documentation/devicetree/bindings/interrupts.txt
>  
> +  - clocks : A list of up to two phandle and clock specifier pairs
> +  - clock-names : A list of clock names sorted in the same order as clocks.
> +                  Valid clock names are "MCLK1" and "MCLK2".
> +
>    - wlf,gpio-cfg : A list of GPIO configuration register values. If absent,
>      no configuration of these registers is performed. If any value is
>      over 0xffff then the register will be left as default. If present 11
> -- 
> 1.8.3.2
> 
> 

  reply	other threads:[~2013-07-25 15:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-25 14:31 [PATCH] ASoC: wm8994: Add clock bindings to the device tree Mark Brown
2013-07-25 15:46 ` Mark Rutland [this message]
2013-07-25 17:56   ` Mark Brown
2013-07-26 15:54     ` Mark Rutland
2013-07-26 15:41 ` Stephen Warren
2013-07-26 15:55   ` 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=20130725154627.GA22291@e106331-lin.cambridge.arm.com \
    --to=mark.rutland@arm.com \
    --cc=Pawel.Moll@arm.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=broonie@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=ian.campbell@citrix.com \
    --cc=patches@opensource.wolfsonmicro.com \
    --cc=rob.herring@calxeda.com \
    --cc=swarren@wwwdotorg.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).