From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Stefan Richter <stefanr@s5r6.in-berlin.de>,
linux1394-devel@lists.sourceforge.net,
"ffado-devel@lists.sf.net" <ffado-devel@lists.sf.net>
Subject: Re: [RFC] [PATCH] firewire-lib: add support for AV/C deferred transaction
Date: Sat, 15 Mar 2014 22:09:12 +0900 [thread overview]
Message-ID: <532450F8.10202@sakamocchi.jp> (raw)
In-Reply-To: <532381B7.3030903@ladisch.de>
Hi Clemens,
(Mar 15 2014 07:24), Clemens Ladisch wrote:
> Looks OK.
Thanks for your quick review.
> In theory, a device that uses INTERIM is likely to need a larger timeout
> than the FCP default, but as long as 125 ms works for those BeBoB devices,
> increasing the timeout is not necessary.
With this value and BeBoB devices which I own, I have experienced no
retry/timeout.
As long as I know, BeBoB based devices need much time to complete
immediate/deferred transaction for changing sampling rate during
streaming. In this case, immediate transactions need 150 msec or more
and deferred transactions need 40/240msec or more to complete. But BeBoB
driver must not change sampling rate in this case because sampling rate
should not be changed during streaming. The driver should stop streaming
once then change sampling rate.
I suggest that we will change this value when finding devices which need
more timeout.
Thanks
Takashi Sakamoto
o-takashi@sakamocchi.jp
prev parent reply other threads:[~2014-03-15 13:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 14:41 [RFC] [PATCH] firewire-lib: add support for AV/C deferred transaction Takashi Sakamoto
2014-03-14 22:24 ` Clemens Ladisch
2014-03-15 13:09 ` Takashi Sakamoto [this message]
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=532450F8.10202@sakamocchi.jp \
--to=o-takashi@sakamocchi.jp \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=ffado-devel@lists.sf.net \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=stefanr@s5r6.in-berlin.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 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).