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: add tracepoints for PCM params refinement
Date: Wed, 07 Jun 2017 10:50:29 +0200	[thread overview]
Message-ID: <s5hlgp441wq.wl-tiwai@suse.de> (raw)
In-Reply-To: <f673a8f5-204a-ac5d-a366-31f72c0d7106@sakamocchi.jp>

On Wed, 07 Jun 2017 10:38:24 +0200,
Takashi Sakamoto wrote:
> 
> On Ju 7 2017 17:09, Takashi Iwai wrote:
> >>>> The second field represents id of each rule applied to the runtime, and
> >>>> the total number of rules added to the runtime. Basically, when the rule
> >>>> is applied to the runtime, these events are probed, but lines with id 0
> >>>> are exceptions. They're application of constraints to the runtime.
> >>>>
> >>>> The third field is name of parameter in the runtime. The rest fields
> >>>> depends on type of the parameter (mask/interval).
> >>>>
> >>>>
> >>>> In ALSA PCM core, runtimes get 22 (or 21) rules as a default. In a below
> >>>> sample, the 21st rule is added by driver (snd-soc-imx-ssi.ko). The rest is
> >>>> added by snd-pcm.ko. In detail, please see 'snd_pcm_hw_constraints_init()'
> >>>> and 'snd_pcm_hw_constraints_complete()' in 'sound/core/pcm_native.c'.
> >>>>
> >>>> hw_interval_param: 0,0,0,0 019/023 PERIOD_TIME 0 0 [0 4294967295] 0 0 (166 4095875]
> >>>> hw_interval_param: 0,0,0,0 020/023 BUFFER_TIME 0 0 [0 4294967295] 0 0 (333 4096000]
> >>>> hw_interval_param: 0,0,0,0 021/023 PERIOD_SIZE 0 1 [16 32767] 0 1 [16 32766]
> >>>> hw_interval_param: 0,0,0,0 022/023 BUFFER_BYTES 0 1 [128 65536] 0 1 [128 65536]
> >>>> hw_interval_param: 0,0,0,0 023/023 RATE 0 0 [8000 96000] 0 0 [8000 96000]
> >>>> hw_mask_param:     0,0,0,0 001/023 FORMAT 00000000000000000000001000000044 00000000000000000000001000000044
> >>>
> >>> Could you add these explanations in Documentation?  The cover letter
> >>> is gone at merging.
> >>
> >> Hm. Could I postpone the task for my later work in this development
> >> period? Text writing takes me a bit time, but I have patches for the
> >> rest of my RFC and firewire stack.
> >
> > It's fine if you can promise to submit the document patch in this
> > development cycle :)
> 
> I promise.

Good to hear, I merged your three patches now.  Thanks!


Takashi

      reply	other threads:[~2017-06-07  8:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-06 23:46 [PATCH 0/3] ALSA: pcm: add tracepoints for PCM params refinement Takashi Sakamoto
2017-06-06 23:46 ` [PATCH 1/3] ALSA: pcm: tracepoints for refining PCM parameters Takashi Sakamoto
2017-06-06 23:46 ` [PATCH 2/3] ALSA: pcm: enable parameter tracepoints only when CONFIG_SND_DEBUG is enabled Takashi Sakamoto
2017-06-06 23:46 ` [PATCH 3/3] ALSA: pcm: obsolete RULES_DEBUG local macro Takashi Sakamoto
2017-06-07  5:42 ` [PATCH 0/3] ALSA: pcm: add tracepoints for PCM params refinement Takashi Iwai
2017-06-07  7:50   ` Takashi Sakamoto
2017-06-07  8:09     ` Takashi Iwai
2017-06-07  8:38       ` Takashi Sakamoto
2017-06-07  8:50         ` 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=s5hlgp441wq.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