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>
Subject: Re: [PATCH] ASoC: wm8994: Add clock bindings to the device tree
Date: Fri, 26 Jul 2013 16:54:09 +0100 [thread overview]
Message-ID: <20130726155409.GC3528@e106331-lin.cambridge.arm.com> (raw)
In-Reply-To: <20130725175642.GJ9858@sirena.org.uk>
On Thu, Jul 25, 2013 at 06:56:42PM +0100, Mark Brown wrote:
> On Thu, Jul 25, 2013 at 04:46:27PM +0100, Mark Rutland wrote:
>
> > Do these two clock inputs exist for all of wm1811, wm8994, and wm8958?
>
> Yes.
>
> > 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.
>
> The clocks are both optional but even if they were assumed to be present
> they aren't usable without knowing the rate which can vary widely. It
> is possible that the system may be able to infer their presence and
> rates from other information such as the audio system integration
> compatible string but that's out of scope for this and doesn't seem like
> a particularly good idea to encorage anyway.
Ok, that sounds sensible.
Thanks,
Mark.
next prev parent reply other threads:[~2013-07-26 15:54 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
2013-07-25 17:56 ` Mark Brown
2013-07-26 15:54 ` Mark Rutland [this message]
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=20130726155409.GC3528@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=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).