alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Jaroslav Kysela <perex@perex.cz>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	alsa-devel@alsa-project.org
Subject: Re: [PATCH v2 00/10]  audio timestamping evolutions
Date: Fri, 19 Dec 2014 21:38:41 +0100	[thread overview]
Message-ID: <54948CD1.4080309@perex.cz> (raw)
In-Reply-To: <1419009913-3686-1-git-send-email-pierre-louis.bossart@linux.intel.com>

Dne 19.12.2014 v 18:25 Pierre-Louis Bossart napsal(a):
> This series of patches was inspired by recent threads on the alsa
> mailing list, as well issues detected with existing and upcoming
> hardware:

I don't like some aspects in the interface:

1) ext_info member is not required - the standard info field
   has enough free bits
2) the whole struct snd_pcm_status is R/O -
   _IOR('A', 0x20, struct snd_pcm_status); I believe that it's much
   better to add new audio_tstamp_type to sw_params, but see (4)
3) accuracy - I would use uint64_t and report accuracy in pico-seconds
   (range from 0 picoseconds to 18446744 seconds); yes, use next bytes
   from the reserved part of status struct. the __u32 might be used only
   for flags
4) if there is a motivation to call / obtain timestamps for multiple
   purposes (audio tstamp types), then offer to return all these
   timestamps in one shot rather than do multiple queries (again, use
   reserved bytes)

			Thanks,
				Jaroslav

-- 
Jaroslav Kysela <perex@perex.cz>
Linux Kernel Sound Maintainer
ALSA Project; Red Hat, Inc.

  parent reply	other threads:[~2014-12-19 20:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-19 17:25 [PATCH v2 00/10] audio timestamping evolutions Pierre-Louis Bossart
2014-12-19 17:25 ` [PATCH v2 01/10] ALSA: core: don't override timestamp unconditionally Pierre-Louis Bossart
2014-12-19 17:25 ` [PATCH v2 02/10] ALSA: core: allow for trigger_tstamp snapshot in .trigger Pierre-Louis Bossart
2014-12-19 17:25 ` [PATCH v2 03/10] ALSA: hda: read trigger_timestamp immediately after starting DMA Pierre-Louis Bossart
2014-12-19 17:25 ` [PATCH v2 04/10] ALSA: usb: update trigger timestamp on first non-zero URB submitted Pierre-Louis Bossart
2014-12-19 17:25 ` [PATCH v2 05/10] ALSA: core: add info_ext field in hw_params and pcm_hardware Pierre-Louis Bossart
2014-12-19 17:25 ` [PATCH v2 06/10] ALSA: core: selection of audio_tstamp type and accuracy reports Pierre-Louis Bossart
2014-12-19 17:25 ` [PATCH v2 07/10] ALSA: core: pass audio tstamp config from userspace Pierre-Louis Bossart
2014-12-19 17:25 ` [PATCH v2 08/10] ALSA: core: pass audio tstamp config from userspace in compat mode Pierre-Louis Bossart
2014-12-19 17:25 ` [PATCH v2 09/10] ALSA: core: replace .wall_clock by .get_time_info Pierre-Louis Bossart
2014-12-19 17:25 ` [PATCH v2 10/10] ALSA: hda: replace .wallclock " Pierre-Louis Bossart
2014-12-20  6:07   ` Raymond Yau
2014-12-20 17:50     ` Pierre-Louis Bossart
2014-12-19 20:38 ` Jaroslav Kysela [this message]
2014-12-19 21:17   ` [PATCH v2 00/10] audio timestamping evolutions Pierre-Louis Bossart
2014-12-21 13:14     ` Jaroslav Kysela
2014-12-26 11:12       ` Takashi Iwai
2015-01-05 21:11       ` 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=54948CD1.4080309@perex.cz \
    --to=perex@perex.cz \
    --cc=alsa-devel@alsa-project.org \
    --cc=pierre-louis.bossart@linux.intel.com \
    /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;
as well as URLs for NNTP newsgroup(s).