Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH 0/3] ALSA: pcm:
Date: Fri, 09 Jun 2017 09:19:00 +0200	[thread overview]
Message-ID: <s5hefut1vdn.wl-tiwai@suse.de> (raw)
In-Reply-To: <20170609003440.4178-1-o-takashi@sakamocchi.jp>

On Fri, 09 Jun 2017 02:34:37 +0200,
Takashi Sakamoto wrote:
> 
> Hi,
> 
> This patchset is a revised version of my former RFC.
> 
> 
> [alsa-devel] [PATCH RFC 00/21] ALSA: pcm: add tracepoints for PCM params operation
> http://mailman.alsa-project.org/pipermail/alsa-devel/2017-May/120548.html
> 
> In ALSA PCM interface, applications can get hardware capability as
> 'struct snd_pcm_hw_params' type of data returned by a call of ioctl(2)
> with SNDRV_PCM_IOCTL_HW_REFINE/SNDRV_PCM_IOCTL_HW_PARAMS' commands.
> Results of these commands should be the same in a certain conditions but
> actually it's not.
> 
> This is a part of layout of the structure.
> 
> struct snd_pcm_hw_params {
>     ...
>     unsigned int info;
>     unsigned int msbits;
>     unsigned int rate_num;
>     unsigned int rate_den;
>     snd_pcm_uframes_t fifo_size;
>     ...
> };
> 
> For example, although the 'msbits', 'rate_num' and 'rate_den' fields are
> filled in a result of HW_REFINE command conditionally, they're never
> filled in a result of HW_PARAMS command. This seems a bug.
> 
> This patchset attempts to fix the bug. This affects userspace applications
> in cotents of the result, but it's acceptrable with a merit for the
> applications to get enough parameters.
> 
> Takashi Sakamoto (3):
>   ALSA: pcm: use helper functions to refer parameters as constants
>   ALSA: pcm: calculate non-mask/non-interval parameters always when
>     possible
>   ALSA: pcm: move fixup of info flag after selecting single parameters

Applied all three patches now.  Thanks.


Takashi

      parent reply	other threads:[~2017-06-09  7:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-09  0:34 [PATCH 0/3] ALSA: pcm: Takashi Sakamoto
2017-06-09  0:34 ` [PATCH 1/3] ALSA: pcm: use helper functions to refer parameters as constants Takashi Sakamoto
2017-06-09  0:34 ` [PATCH 2/3] ALSA: pcm: calculate non-mask/non-interval parameters always when possible Takashi Sakamoto
2017-06-09  0:34 ` [PATCH 3/3] ALSA: pcm: move fixup of info flag after selecting single parameters Takashi Sakamoto
2017-06-09  1:45 ` [PATCH 0/3] ALSA: pcm: Takashi Sakamoto
2017-06-09  7:19 ` Takashi Iwai [this message]

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=s5hefut1vdn.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=o-takashi@sakamocchi.jp \
    /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