From: Muni Sekhar <munisekharrms@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: trigger timestamp
Date: Thu, 8 Jul 2021 17:49:12 +0530 [thread overview]
Message-ID: <CAHhAz+guERMjmT_bRrgWzMoKkH2S0Zv0JatjpbNJZnLj+RyxXw@mail.gmail.com> (raw)
In-Reply-To: <s5hmtqx59hm.wl-tiwai@suse.de>
On Thu, Jul 8, 2021 at 4:59 PM Takashi Iwai <tiwai@suse.de> wrote:
>
> On Thu, 01 Jul 2021 01:41:29 +0200,
> Muni Sekhar wrote:
> >
> > Hi all,
> >
> > >From the user space test application , Is it possible to get the
> > trigger timestamp corresponding to SNDRV_PCM_TRIGGER_START &
> > SNDRV_PCM_TRIGGER_STOP events for audio playback capture?
>
> That's exactly what trigger_tstamp of snd_pcm_status corresponds for.
Does aplay and arecord have any command line options to get the
trigger_tstamp? If not how to get it?
>
>
> HTH,
>
> Takashi
--
Thanks,
Sekhar
WARNING: multiple messages have this Message-ID (diff)
From: Muni Sekhar <munisekharrms@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: trigger timestamp
Date: Thu, 8 Jul 2021 17:49:12 +0530 [thread overview]
Message-ID: <CAHhAz+guERMjmT_bRrgWzMoKkH2S0Zv0JatjpbNJZnLj+RyxXw@mail.gmail.com> (raw)
In-Reply-To: <s5hmtqx59hm.wl-tiwai@suse.de>
On Thu, Jul 8, 2021 at 4:59 PM Takashi Iwai <tiwai@suse.de> wrote:
>
> On Thu, 01 Jul 2021 01:41:29 +0200,
> Muni Sekhar wrote:
> >
> > Hi all,
> >
> > >From the user space test application , Is it possible to get the
> > trigger timestamp corresponding to SNDRV_PCM_TRIGGER_START &
> > SNDRV_PCM_TRIGGER_STOP events for audio playback capture?
>
> That's exactly what trigger_tstamp of snd_pcm_status corresponds for.
Does aplay and arecord have any command line options to get the
trigger_tstamp? If not how to get it?
>
>
> HTH,
>
> Takashi
--
Thanks,
Sekhar
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2021-07-08 12:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-30 23:41 trigger timestamp Muni Sekhar
2021-06-30 23:41 ` Muni Sekhar
2021-07-08 11:29 ` Takashi Iwai
2021-07-08 11:29 ` Takashi Iwai
2021-07-08 12:19 ` Muni Sekhar [this message]
2021-07-08 12:19 ` Muni Sekhar
2021-07-08 12:32 ` Takashi Iwai
2021-07-08 12:32 ` Takashi Iwai
2021-07-08 16:11 ` Muni Sekhar
2021-07-08 16:11 ` Muni Sekhar
2021-07-08 16:15 ` Takashi Iwai
2021-07-08 16:15 ` Takashi Iwai
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=CAHhAz+guERMjmT_bRrgWzMoKkH2S0Zv0JatjpbNJZnLj+RyxXw@mail.gmail.com \
--to=munisekharrms@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=kernelnewbies@kernelnewbies.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.