alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Grazvydas Ignotas <notasas@gmail.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: alsa-devel@alsa-project.org,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Liam Girdwood <lrg@ti.com>,
	Jarkko Nikula <jarkko.nikula@bitmer.com>
Subject: Re: [PATCH] ASoC: omap-mcbsp: When closing the port select PRCM source for CLKS signal
Date: Mon, 5 Mar 2012 14:51:10 +0200	[thread overview]
Message-ID: <CANOLnOOzXycmiESekOz4s305KFV0SPLSJHQ5M2aFgBVwY-dJmQ@mail.gmail.com> (raw)
In-Reply-To: <1330940332-16188-1-git-send-email-peter.ujfalusi@ti.com>

On Mon, Mar 5, 2012 at 11:38 AM, Peter Ujfalusi <peter.ujfalusi@ti.com> wrote:
> If external source for the CLKS signal selection kept after the port is no
> longer in use the system might refuse to go suspend.
> There is also a chance that the external clock is not running when next
> time the McBSP port is started which can result errors when we try to
> access McBSP registers.
> Reset the CLKS source back to PRCM source unconditionally.
>
> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>

I guess this depends on mcbsp move series?
Do we have those queued somewhere, so I don't have to collect patches
from the list?


-- 
Gražvydas
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  parent reply	other threads:[~2012-03-05 12:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-05  9:38 [PATCH] ASoC: omap-mcbsp: When closing the port select PRCM source for CLKS signal Peter Ujfalusi
2012-03-05 11:58 ` Mark Brown
2012-03-05 12:33   ` Peter Ujfalusi
2012-03-05 12:51 ` Grazvydas Ignotas [this message]
2012-03-05 13:02   ` Peter Ujfalusi
2012-03-06 12:54   ` Peter Ujfalusi
2012-03-06 14:44     ` Liam Girdwood
2012-03-08 14:00       ` Grazvydas Ignotas
2012-03-08 14:30         ` Ujfalusi, Peter
2012-03-08 22:48 ` Grazvydas Ignotas

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=CANOLnOOzXycmiESekOz4s305KFV0SPLSJHQ5M2aFgBVwY-dJmQ@mail.gmail.com \
    --to=notasas@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=jarkko.nikula@bitmer.com \
    --cc=lrg@ti.com \
    --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 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).