From: Mark Brown <broonie@kernel.org>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Rob Herring <rob.herring@calxeda.com>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ian.campbell@citrix.com>,
devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH] ASoC: wm8994: Add clock bindings to the device tree
Date: Fri, 26 Jul 2013 16:55:30 +0100 [thread overview]
Message-ID: <20130726155530.GP9858@sirena.org.uk> (raw)
In-Reply-To: <51F298C0.1090801@wwwdotorg.org>
[-- Attachment #1: Type: text/plain, Size: 673 bytes --]
On Fri, Jul 26, 2013 at 09:41:52AM -0600, Stephen Warren wrote:
> On 07/25/2013 08:31 AM, Mark Brown wrote:
> > 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.
> Presumably before considering any/most CODEC bindings complete, we need
> to make a similar change?
Yeah, ideally. I was going to go through the ones I know about at some
point. On the other hand it's not really a big deal given how far off
we are being able to rely on the clock API and we still need to work out
what to do with hooking the audio buses in too.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-07-26 15:55 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
2013-07-26 15:41 ` Stephen Warren
2013-07-26 15:55 ` 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=20130726155530.GP9858@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree@vger.kernel.org \
--cc=ian.campbell@citrix.com \
--cc=mark.rutland@arm.com \
--cc=patches@opensource.wolfsonmicro.com \
--cc=pawel.moll@arm.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).