linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Greg Knight <g.knight@symetrica.com>
Cc: Mark Brown <broonie@kernel.org>, 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: Fri, 20 Mar 2015 10:09:04 +0200	[thread overview]
Message-ID: <550BD5A0.6080400@ti.com> (raw)
In-Reply-To: <1426787288.13824.36.camel@symus-gk-mint>

Greg,

On 03/19/2015 07:48 PM, Greg Knight wrote:
>> For a codec such as the SGTL5000 I would connect a clock, which is
> running all
>> the time. If you take a look at the driver, it enables the clock at
> probe and
>> leaves it running as long as the driver is loaded.
> 
> Speaking briefly to my "electrical" colleague, he's a bit concerned
> about the extra power load that a crystal oscillator might incur, while
> I'm concerned about audio quality from a source like CLKOUT2.
> 
> 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.
> 
> Worst-case we can set up a GPIO and enable/disable it as needed in
> user-space - acceptable, if annoying, for our application.

See my reply to Nikolay.

-- 
Péter
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2015-03-20  8:09 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 [this message]
2015-03-22 17:48         ` Mark Brown
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=550BD5A0.6080400@ti.com \
    --to=peter.ujfalusi@ti.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=g.knight@symetrica.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=perex@perex.cz \
    /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).