From: Mark Brown <broonie@kernel.org>
To: Greg Knight <g.knight@symetrica.com>
Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>,
Jaroslav Kysela <perex@perex.cz>,
alsa-devel@alsa-project.org,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Patches to bind the SGTL5000 chip to AM33XX McASP
Date: Sun, 22 Mar 2015 17:48:03 +0000 [thread overview]
Message-ID: <20150322174803.GL6643@sirena.org.uk> (raw)
In-Reply-To: <1426787288.13824.36.camel@symus-gk-mint>
[-- Attachment #1: Type: text/plain, Size: 455 bytes --]
On Thu, Mar 19, 2015 at 01:48:08PM -0400, Greg Knight wrote:
> Is there a straightforward way we could enable the clock on-demand -
> when we're communicating with the codec/mixer or actually using the
> audio subsystem - while keeping it disabled when not in use? We don't
> expect to be using the audio subsystem frequently.
This is what the clock API is there for - the driver can enable the
clock whenver it needs it and disable it when it doesn't.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-03-22 17:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 5:07 Patches to bind the SGTL5000 chip to AM33XX McASP Greg Knight
2015-03-19 11:38 ` Mark Brown
2015-03-19 12:56 ` Peter Ujfalusi
2015-03-19 14:34 ` Greg Knight
2015-03-19 16:07 ` Peter Ujfalusi
2015-03-19 17:17 ` Greg Knight
2015-03-19 17:48 ` Greg Knight
2015-03-20 8:09 ` Peter Ujfalusi
2015-03-22 17:48 ` Mark Brown [this message]
2015-03-19 18:06 ` Nikolay Dimitrov
2015-03-20 8:05 ` Peter Ujfalusi
2015-03-20 15:51 ` [alsa-devel] " Nikolay Dimitrov
2015-03-22 17:58 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2015-03-18 19:36 Greg Knight
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=20150322174803.GL6643@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=g.knight@symetrica.com \
--cc=linux-omap@vger.kernel.org \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.