All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Warren <swarren@nvidia.com>
Cc: "linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: Tegra audio clocking
Date: Fri, 7 Jan 2011 21:01:48 +0000	[thread overview]
Message-ID: <20110107210148.GA9482@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF0310567D81@HQMAIL01.nvidia.com>

On Fri, Jan 07, 2011 at 12:48:29PM -0800, Stephen Warren wrote:

> Does this sound sane to you? It will mean turning the clocks
> on/off a lot, which goes against something you'd mentioned
> above not glitching the clocks every time. However, the
> following explains why:

It'll only glitch the clocks if you allow them to be be reconfigured
while audio is active but since this would presumably cause the active
streams to be reconfigured which would disrupt them.

> Hence, I believe the machine driver needs to control both of
> those (although using utility code to avoid cut/paste of all
> the clock calls into each machine driver).

That's fine.

> I can see 3 ways to co-ordinate this:

> 1) Have all clocks off, except between two well-defined API
>    calls (e.g. trigger START/STOP) such that the machine
>    driver has a well-defined time the clock can be
>    reconfigured without explicit calls to co-ordinate with the
>    I2S driver.

It'd seem best from a power point of view to disable the clocks wherever
possible anyway so this seems like a good option.

      reply	other threads:[~2011-01-07 21:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-07 20:48 Tegra audio clocking Stephen Warren
2011-01-07 21:01 ` 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=20110107210148.GA9482@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=swarren@nvidia.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.