From: Takashi Iwai <tiwai@suse.de>
To: sylvain.bertrand@gmail.com
Cc: alsa-devel@alsa-project.org,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Kai Vehmanen <kai.vehmanen@linux.intel.com>
Subject: Re: sw_params for a direct-ed(dmix) hw pcm
Date: Wed, 01 Apr 2020 17:59:52 +0200 [thread overview]
Message-ID: <s5hwo6z2o3r.wl-tiwai@suse.de> (raw)
In-Reply-To: <20200401152538.GA11377@freedom>
On Wed, 01 Apr 2020 17:25:38 +0200,
sylvain.bertrand@gmail.com wrote:
>
> Hi,
>
> Lol, I was working on it too. I got almost exactly the same code related to the
> addition of a configuration variable:
> - in 'struct snd_pcm_direct_open_conf' I used the type 'snd_pcm_tstamp_type_t'
> instead of 'int' for the added tstamp_type field.
> - idem for the 'struct snd_pcm_direct' tstamp_type field.
Heh, my initial patch was also with that strong type, but I changed it
because I wanted to allow the "system default" value, which isn't
represented with that type.
thanks,
Takashi
next prev parent reply other threads:[~2020-04-01 16:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-21 15:53 monotonic raw setup seems buggy sylvain.bertrand
2020-03-25 17:44 ` sw_params for a direct-ed(dmix) hw pcm sylvain.bertrand
2020-03-26 12:02 ` Kai Vehmanen
2020-03-26 14:36 ` Jaroslav Kysela
2020-03-26 20:04 ` sylvain.bertrand
2020-03-27 8:08 ` Takashi Iwai
2020-03-27 9:40 ` Jaroslav Kysela
2020-03-28 18:26 ` sylvain.bertrand
2020-03-28 19:15 ` Pierre-Louis Bossart
2020-03-28 20:37 ` sylvain.bertrand
2020-03-28 21:34 ` Pierre-Louis Bossart
2020-03-28 22:20 ` sylvain.bertrand
2020-03-29 7:43 ` Takashi Iwai
2020-03-31 11:32 ` Takashi Iwai
2020-04-01 15:25 ` sylvain.bertrand
2020-04-01 15:59 ` Takashi Iwai [this message]
2020-04-01 20:21 ` sylvain.bertrand
2020-04-02 19:03 ` sylvain.bertrand
2020-04-06 13:49 ` sylvain.bertrand
2020-04-14 15:18 ` Takashi Iwai
2020-04-14 23:20 ` sylvain.bertrand
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=s5hwo6z2o3r.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=kai.vehmanen@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=sylvain.bertrand@gmail.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 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.