From: Tony Lindgren <tony@atomide.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: alsa-devel@alsa-project.org,
"Ivaylo Dimitrov" <ivo.g.dimitrov.75@gmail.com>,
"Aaro Koskinen" <aaro.koskinen@iki.fi>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Sebastian Reichel" <sre@kernel.org>,
"Kristo, Tero" <t-kristo@ti.com>,
"Mark Brown" <broonie@kernel.org>,
"Jarkko Nikula" <jarkko.nikula@linux.intel.com>,
"Pavel Machel" <pavel@ucw.cz>,
"Pali Rohár" <pali.rohar@gmail.com>,
linux-omap@vger.kernel.org
Subject: Re: [PATCH] ASoC: omap-mcbsp: Add PM QoS support for McBSP to prevent glitches
Date: Wed, 7 Sep 2016 20:53:56 -0700 [thread overview]
Message-ID: <20160908035356.mkk35s5gpcemifcg@atomide.com> (raw)
In-Reply-To: <1b82e33a-7db5-81ed-de4f-75847f840088@ti.com>
* Peter Ujfalusi <peter.ujfalusi@ti.com> [160907 07:32]:
> On 09/06/2016 11:16 PM, Tony Lindgren wrote:
> > Makes sense. Do you have a formula or updated patch I can test here?
> > Then we can add comments about the possible unaccounted latencies that
> > can be worked out as needed.
>
> Not yet, but I'll try to come up with something in the coming days.
OK
> btw: I have tried the idle off on beagbeboard-xm with audio, but even w/o the
> qos it is not triggering. w/o audio I hit off but if audio is running, not.
OK yeah figured it out you need to comment out the watch -n5 command
as that keeps the serial console busy :) I was doing it over ssh earlier
on the torpedo board.
> btw2: if you set the qos to 30ms and set the mcbsp2 threshold to 1024 (or
> leave it as default) do you have audio glitches? I think if we hit C6 we
> should not be able to wake up in time...
Not that I've noticed at least with the default fifo size. How can
I force the threshold to 1024? I tried changing pkt_size for
omap_mcbsp_set_threshold but not getting any audio.
Regards,
Tony
next prev parent reply other threads:[~2016-09-08 3:53 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-29 18:27 [PATCH] ASoC: omap-mcbsp: Add PM QoS support for McBSP to prevent glitches Tony Lindgren
[not found] ` <201608300739.JrTVlIyd%fengguang.wu@intel.com>
2016-08-30 18:38 ` Tony Lindgren
2016-08-31 17:24 ` Mark Brown
2016-08-31 17:42 ` Tony Lindgren
2016-08-31 11:37 ` Peter Ujfalusi
2016-08-31 14:13 ` Tony Lindgren
2016-08-31 16:59 ` Tony Lindgren
2016-08-31 18:33 ` Peter Ujfalusi
2016-08-31 19:41 ` Tony Lindgren
2016-09-01 6:57 ` Peter Ujfalusi
2016-09-01 14:50 ` Tony Lindgren
2016-09-02 7:30 ` Peter Ujfalusi
2016-09-02 14:56 ` Tony Lindgren
2016-09-02 19:38 ` Peter Ujfalusi
2016-09-02 20:40 ` Tony Lindgren
2016-09-05 7:53 ` Peter Ujfalusi
2016-09-06 20:16 ` Tony Lindgren
2016-09-07 14:31 ` Peter Ujfalusi
2016-09-08 3:53 ` Tony Lindgren [this message]
2016-09-08 10:41 ` Peter Ujfalusi
2016-09-08 10:49 ` Peter Ujfalusi
2016-09-08 14:48 ` Tony Lindgren
2016-09-09 6:51 ` Peter Ujfalusi
2016-09-09 23:45 ` Tony Lindgren
2016-09-13 11:45 ` Peter Ujfalusi
2016-09-13 13:45 ` Tony Lindgren
2016-09-02 15:54 ` Pavel Machek
2016-09-02 19:45 ` Peter Ujfalusi
2016-09-02 20:09 ` Tony Lindgren
2016-09-03 16:08 ` Sebastian Reichel
2016-09-06 20:08 ` Tony Lindgren
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=20160908035356.mkk35s5gpcemifcg@atomide.com \
--to=tony@atomide.com \
--cc=aaro.koskinen@iki.fi \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=pavel@ucw.cz \
--cc=peter.ujfalusi@ti.com \
--cc=sre@kernel.org \
--cc=t-kristo@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