From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Takashi Iwai <tiwai@suse.de>,
"Subhransu S. Prusty" <subhransu.s.prusty@intel.com>
Cc: patches.audio@intel.com, alsa-devel@alsa-project.org,
broonie@kernel.org, lgirdwood@gmail.com,
Ramesh Babu <ramesh.babu@intel.com>
Subject: Re: [PATCH v3] ALSA: core: let low-level driver or userspace disable rewinds
Date: Mon, 19 Jun 2017 10:16:28 -0500 [thread overview]
Message-ID: <a6c137ca-9158-50e2-fc55-eb6ef91db46c@linux.intel.com> (raw)
In-Reply-To: <s5hr2yg74f4.wl-tiwai@suse.de>
On 6/19/17 3:44 AM, Takashi Iwai wrote:
> On Mon, 19 Jun 2017 08:22:37 +0200,
> Subhransu S. Prusty wrote:
>>
>> From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
>>
>> Add new hw_params flag to explicitly tell driver that rewinds will never
>> be used. This can be used by low-level driver to optimize DMA operations
>> and reduce power consumption. Use this flag only when data written in
>> ring buffer will never be invalidated, e.g. any update of appl_ptr is
>> final.
>>
>> Note that the update of appl_ptr include both a read/write data
>> operation as well as snd_pcm_forward() whose behavior is not modified.
>>
>> Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
>> Signed-off-by: Ramesh Babu <ramesh.babu@intel.com>
>> Signed-off-by: Subhransu S. Prusty <subhransu.s.prusty@intel.com>
>> ---
>>
>> v2 -> v3
>> return error for rewind operation if no_rewinds set.
>
> Now I'm thinking whether this change is really needed or in the right
> direction. I suppose that the driver would change the behavior
> depending on the flag of this flag. But then how can application know
> that it should not rewind on a certain device and set the flag?
The application (which is in most cases an audio server) *knows* if it
requires rewinds or not. It's part of its design, with rewinds typically
disabled if period interrupts are required. It's been that way for a
number of years now. The use of rewinds is typically associated with the
combination of a large buffer and no interrupts (having either of the
two would not require rewinds).
So the idea is that the application makes a statement that rewinds will
not be used, and the low-level driver makes use of the information to
enable whatever optimizations are available at the hardware level.
Exposing more information to userspace would quickly lead to a confusing
decision-making and would require more than just a flag.
>
> We may, instead, let the driver behaving in the deep buffer mode as
> default (or turned on/off via the kcontrol). Then you can simply
> return an error for the negative appl_ptr change in ack callback --
> which effectively disables the rewind.
>
>
> thanks,
>
> Takashi
>
>> include/sound/pcm.h | 1 +
>> include/uapi/sound/asound.h | 1 +
>> sound/core/pcm_native.c | 8 ++++++++
>> 3 files changed, 10 insertions(+)
>>
>> diff --git a/include/sound/pcm.h b/include/sound/pcm.h
>> index 79fedf517070..c1e2b87cd409 100644
>> --- a/include/sound/pcm.h
>> +++ b/include/sound/pcm.h
>> @@ -368,6 +368,7 @@ struct snd_pcm_runtime {
>> unsigned int rate_num;
>> unsigned int rate_den;
>> unsigned int no_period_wakeup: 1;
>> + unsigned int no_rewinds:1;
>>
>> /* -- SW params -- */
>> int tstamp_mode; /* mmap timestamp is updated */
>> diff --git a/include/uapi/sound/asound.h b/include/uapi/sound/asound.h
>> index fd41697cb4d3..c697ff90450d 100644
>> --- a/include/uapi/sound/asound.h
>> +++ b/include/uapi/sound/asound.h
>> @@ -365,6 +365,7 @@ struct snd_pcm_info {
>> #define SNDRV_PCM_HW_PARAMS_NORESAMPLE (1<<0) /* avoid rate resampling */
>> #define SNDRV_PCM_HW_PARAMS_EXPORT_BUFFER (1<<1) /* export buffer */
>> #define SNDRV_PCM_HW_PARAMS_NO_PERIOD_WAKEUP (1<<2) /* disable period wakeups */
>> +#define SNDRV_PCM_HW_PARAMS_NO_REWINDS (1<<3) /* disable rewinds */
>>
>> struct snd_interval {
>> unsigned int min, max;
>> diff --git a/sound/core/pcm_native.c b/sound/core/pcm_native.c
>> index bf5d0f2acfb9..6769f4751fa0 100644
>> --- a/sound/core/pcm_native.c
>> +++ b/sound/core/pcm_native.c
>> @@ -554,6 +554,8 @@ static int snd_pcm_hw_params(struct snd_pcm_substream *substream,
>> runtime->no_period_wakeup =
>> (params->info & SNDRV_PCM_INFO_NO_PERIOD_WAKEUP) &&
>> (params->flags & SNDRV_PCM_HW_PARAMS_NO_PERIOD_WAKEUP);
>> + runtime->no_rewinds =
>> + (params->flags & SNDRV_PCM_HW_PARAMS_NO_REWINDS) ? 1 : 0;
>>
>> bits = snd_pcm_format_physical_width(runtime->format);
>> runtime->sample_bits = bits;
>> @@ -2521,6 +2523,9 @@ static snd_pcm_sframes_t snd_pcm_playback_rewind(struct snd_pcm_substream *subst
>> if (frames == 0)
>> return 0;
>>
>> + if (runtime->no_rewinds)
>> + return -ENODEV;
>> +
>> snd_pcm_stream_lock_irq(substream);
>> ret = do_pcm_hwsync(substream);
>> if (!ret)
>> @@ -2539,6 +2544,9 @@ static snd_pcm_sframes_t snd_pcm_capture_rewind(struct snd_pcm_substream *substr
>> if (frames == 0)
>> return 0;
>>
>> + if (runtime->no_rewinds)
>> + return -ENODEV;
>> +
>> snd_pcm_stream_lock_irq(substream);
>> ret = do_pcm_hwsync(substream);
>> if (!ret)
>> --
>> 1.9.1
>>
next prev parent reply other threads:[~2017-06-19 15:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 6:22 [PATCH v3] ALSA: core: let low-level driver or userspace disable rewinds Subhransu S. Prusty
2017-06-19 8:03 ` Vinod Koul
2017-06-19 8:44 ` Takashi Iwai
2017-06-19 15:16 ` Pierre-Louis Bossart [this message]
2017-06-19 15:25 ` Takashi Iwai
2017-06-19 15:38 ` Pierre-Louis Bossart
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=a6c137ca-9158-50e2-fc55-eb6ef91db46c@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=patches.audio@intel.com \
--cc=ramesh.babu@intel.com \
--cc=subhransu.s.prusty@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox