All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: [RFC PATCH 0/4] better support for bursty DMA usages
Date: Wed, 08 Jul 2015 19:50:45 +0200	[thread overview]
Message-ID: <559D62F5.8080201@linux.intel.com> (raw)
In-Reply-To: <s5hk2uahgap.wl-tiwai@suse.de>

On 7/8/15 4:31 PM, Takashi Iwai wrote:
> On Wed, 08 Jul 2015 12:10:32 +0200,
> Pierre-Louis Bossart wrote:
>>
>> Set of patches to fix issues with hw_ptr fuzziness [1] and increased buffering
>>   w/ DSPs
>>
>> 1. disable rewinds to allow for new HDaudio SPIB DMA functionality (fetch up to
>> the application pointer, rewinds not supported)
>> 2. report max in-flight bytes to avoid problems with stale data (late wake-ups,
>> rewinds)
>>
>> [1] http://mailman.alsa-project.org/pipermail/alsa-devel/2015-June/093646.html
>>
>> TODO:
>> 1. fixes and alsa-lib updates (compile-tested only for now)
>> 2. get feedback
>> 3. if supported, set DMA buffering based on negotiation between driver and app (capabilities vs.
>> latency needs)
>
> Thanks for heading up.  I wanted to start working on this by myself,
> too, but it was pending due to the horribly hot summer days here :)

Thanks for the quick review Takashi, much appreciated. The work was done 
before the heat wave on my side...

> The new flag and the callback are fairly similar as what I had in my
> mind.  They look simple enough (although details need more discussion
> and evaulation).
>
> For the DMA burst thing, I'm not quite sure whether it's the best
> form, including its naming.  But I'd like to be neutral about this,
> and hopefully others will give opinion for this or give alternatives.

Yes, this is really a first draft to try and solve the problems 
mentioned multiple times by Arun and Alexander and help use the latest 
and greatest hardware. If others have comments we are all ears.

  reply	other threads:[~2015-07-08 17:50 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-08 10:10 [RFC PATCH 0/4] better support for bursty DMA usages Pierre-Louis Bossart
2015-07-08 10:10 ` [RFC PATCH 1/4] ALSA: core: let low-level driver or userspace disable rewinds Pierre-Louis Bossart
2015-07-08 14:21   ` Takashi Iwai
2015-07-08 16:58     ` Pierre-Louis Bossart
2015-07-11 17:06   ` Alexander E. Patrakov
2015-07-14  3:32     ` Raymond Yau
2015-07-14 17:39       ` Alexander E. Patrakov
2015-07-15  1:23         ` Raymond Yau
2015-07-15  4:51           ` Alexander E. Patrakov
2015-07-28 14:19     ` Pierre-Louis Bossart
2015-07-28 15:43       ` Alexander E. Patrakov
2015-07-29 17:46         ` Pierre-Louis Bossart
2015-07-30  6:11           ` Alexander E. Patrakov
2015-07-30 13:46             ` Pierre-Louis Bossart
2015-07-08 10:10 ` [RFC PATCH 2/4] ALSA: core: add .notify callback for pcm ops Pierre-Louis Bossart
2015-07-08 14:27   ` Takashi Iwai
2015-07-08 17:10     ` Pierre-Louis Bossart
2015-07-09 14:44       ` Takashi Iwai
2015-07-09  7:25     ` Raymond Yau
2015-07-09  7:35       ` Pierre-Louis Bossart
2015-07-08 10:10 ` [RFC PATCH 3/4] ALSA: core: add report of max dma burst Pierre-Louis Bossart
2015-07-08 14:37   ` Takashi Iwai
2015-07-08 17:46     ` Pierre-Louis Bossart
2015-07-10  2:35       ` Raymond Yau
2015-07-10 17:13         ` Lars-Peter Clausen
2015-07-11 17:46     ` Alexander E. Patrakov
2015-07-11 18:28       ` Jaroslav Kysela
2015-07-16  2:11         ` Raymond Yau
2015-07-08 10:10 ` [RFC PATCH 4/4] ALSA: hda: add default value for max_dma_burst Pierre-Louis Bossart
2015-07-08 14:31 ` [RFC PATCH 0/4] better support for bursty DMA usages Takashi Iwai
2015-07-08 17:50   ` Pierre-Louis Bossart [this message]
2015-07-15 10:14 ` Raymond Yau
2015-07-15 10:38   ` Alexander E. Patrakov
2015-07-22 14:44     ` Raymond Yau

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=559D62F5.8080201@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    /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.