From: Mark Brown <broonie@kernel.org>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Cc: Takashi Iwai <tiwai@suse.de>,
Liam Girgwood <liam.r.girdwood@linux.intel.com>,
alsa-devel@alsa-project.org
Subject: Re: Audio miniconference at LPC/KS confirmed-
Date: Sun, 23 Oct 2016 00:30:55 +0100 [thread overview]
Message-ID: <20161022233055.GS10208@sirena.org.uk> (raw)
In-Reply-To: <6cfff6e4-5aaa-d4e6-8d78-18207788ef9c@sakamocchi.jp>
[-- Attachment #1.1: Type: text/plain, Size: 1201 bytes --]
On Sat, Oct 22, 2016 at 08:42:15AM +0900, Takashi Sakamoto wrote:
> 1. Add tracepoints to pcm parameter processing in ALSA PCM core
> In my memory of our previous mini audio conference, some issuers are
> addressed about pcm parameters. This is my WIP related to it. The aim is
> to monitor changes of pcm parameter refinement processing just after
> calling ioctl(HW_REFINE/HW_PARAMS). See my working branch:
> https://github.com/takaswie/sound/tree/trace-rules
Do we need to discuss this face to face - are there concerns people have
about adding tracepoints or something? I think it's a good idea to do
the tracepoints, I'm just wondering if we're going to have much of a
discussion or if it'd be a very brief thing.
> 3. Dropping dice driver from ALSA firewire stack
> A fatal quirk apperard that the most of TCAT ASIC called as 'DICE'
> breaks the least significant protocol as a sound device[1][2]. The
> chipsets don't transfer PCM frames as the same as current sampling
> frequency (it's sampling transfer frequency in IEC 61883-6 word).
> This is my suggestion to drop dice driver from ALSA firewire stack.
I guess this is something that is mainly going to be discussed by a few
people?
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2016-10-22 23:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 15:54 Potential Audio miniconference at LPC/KS Mark Brown
2016-07-08 8:59 ` Vinod Koul
2016-07-08 8:54 ` Mark Brown
2016-08-11 6:13 ` Takashi Iwai
2016-08-12 11:26 ` Mark Brown
2016-08-12 12:06 ` Takashi Iwai
2016-08-22 4:59 ` Vinod Koul
2016-08-22 10:35 ` Mark Brown
2016-08-25 10:38 ` Mark Brown
2016-08-25 15:39 ` Audio miniconference at LPC/KS confirmed- Mark Brown
2016-10-20 13:30 ` Takashi Sakamoto
2016-10-20 14:11 ` Mark Brown
2016-10-21 23:42 ` Takashi Sakamoto
2016-10-22 23:30 ` Mark Brown [this message]
2016-10-24 12:57 ` Takashi Sakamoto
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=20161022233055.GS10208@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=o-takashi@sakamocchi.jp \
--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.