All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: sylvain.bertrand@gmail.com, alsa-devel@alsa-project.org
Subject: Re: [alsa-devel] no period wakeup support
Date: Wed, 29 Jan 2020 17:43:19 -0600	[thread overview]
Message-ID: <fffaf462-fd7a-6d09-e808-21d94f883365@linux.intel.com> (raw)
In-Reply-To: <20200129232340.GA23769@freedom>



> Nowadays, is this reasonable to consider disabling the period wakeup as default
> instead of expecting period wakeup by default?

I'd say yes - it's been nearly 10 years since this capability was added, 
and it's quite common across HDaudio, Chrome, Android plaforms.

But considering this as a default doesn't mean it's available in 100% of 
the cases, you still you need to check that

a) the driver is capable of disabling the period wakeup
b) the driver is capable of providing a precise position outside of 
period elapsed events (usually marked with the INFO_BATCH capability).

alsa-lib gives you the means to query both cases.

Note that you also have the case where you cannot disable interrupts but 
can still use timer-based solutions (e.g. for USB audio).

Hope this helps
-Pierre

_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2020-01-29 23:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-29 23:23 [alsa-devel] no period wakeup support sylvain.bertrand
2020-01-29 23:43 ` Pierre-Louis Bossart [this message]
2020-01-30  1:20   ` sylvain.bertrand
2020-01-30  7:06   ` Takashi Sakamoto
2020-01-30  7:46     ` Jaroslav Kysela
2020-01-30 13:22       ` Pierre-Louis Bossart
2020-01-30 23:56         ` Takashi Sakamoto

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=fffaf462-fd7a-6d09-e808-21d94f883365@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=sylvain.bertrand@gmail.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.