All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eldad Zack <eldad@fogrefinery.com>
To: Felix Homann <linuxaudio@showlabor.de>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
	Clemens Ladisch <clemens@ladisch.de>,
	Daniel Mack <zonque@gmail.com>
Subject: Re: How to use implicit feedback with full duplex?
Date: Thu, 7 Feb 2013 21:49:52 +0100 (CET)	[thread overview]
Message-ID: <alpine.LNX.2.00.1302072139480.1138@xoschi> (raw)
In-Reply-To: <CAFz=ag4aVMoEcYiZ4BKbqAoN7PuwvrhDa-162183JdsdYhDK_w@mail.gmail.com>


Hi Felix,

On Thu, 7 Feb 2013, Felix Homann wrote:

> Hi Daniel, Hi Eldad.
> 
> 2013/2/6 Daniel Mack <zonque@gmail.com>
>       I'll look for the FTU and re-try this with Eldad's latest additions once
>       I find some time.
> 
> 
> I'll probably find some time later next week. I haven't followed thoroughly what Eldad did for the C400/C600 but wanted to play around with the FTU anyway (if I
> remember correctly there was a patch dropping the first n implicit feedback packets on the C400 that might possibly be of benefit for the FTUs as well).

I only added C400 - but I hope the asymmetry-related patches will save 
time with the C600.

Do you get different latency every time you start up a stream on the 
FTU? That's the reason for the skip_packet quirk for the C400.

> @Eldad Have your latest additions already made it into Takashi's tree or where can I find them?

Yes and they are all merged upstream by now. But they are mostly 
small things and specific to the C400.

Cheers,
Eldad

  parent reply	other threads:[~2013-02-07 20:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-05 20:44 How to use implicit feedback with full duplex? Clemens Ladisch
2013-02-05 22:50 ` Eldad Zack
2013-02-06 20:13   ` Clemens Ladisch
2013-02-06 20:20     ` Daniel Mack
2013-02-07  9:03       ` Felix Homann
2013-02-07  9:52         ` Takashi Iwai
2013-02-07 20:54           ` Eldad Zack
2013-02-07 20:49         ` Eldad Zack [this message]
2013-02-07 20:39     ` Eldad Zack
2013-03-24 22:49     ` Eldad Zack
2013-03-26 20:06       ` Daniel Mack
2013-04-03 22:08         ` Eldad Zack

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=alpine.LNX.2.00.1302072139480.1138@xoschi \
    --to=eldad@fogrefinery.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    --cc=linuxaudio@showlabor.de \
    --cc=zonque@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.