From: Daniel Mack <zonque@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: blablack@gmail.com, alsa-devel@alsa-project.org,
clemens@ladisch.de, gdiffey@gmail.com, linuxaudio@showlabor.de
Subject: Re: [PATCH 0/5] RFC for snd-usb: rework usb endpoint logic
Date: Wed, 02 Nov 2011 09:27:30 +0100 [thread overview]
Message-ID: <4EB0FEF2.9000205@gmail.com> (raw)
In-Reply-To: <s5haa8fn7cg.wl%tiwai@suse.de>
Hi Takashi,
On 11/01/2011 05:19 PM, Takashi Iwai wrote:
> The overall design looks good to me. Nice work!
> A few nitpicking:
Thanks for your review!
> - No need for check of activated flags at starting streams?
Such a condition would be a bug in the driver. But I'll add a check.
> - Better to clear subs->data_endpoint& co at closing.
Jup.
> - There might be unbalances when deactivate_endpoints() isn't called
> in prepare callback before activate_endpoints(). The apps may call
> like
> open -> hw_params -> prepare -> hw_params -> prepare -> trigger
> and
> trigger (stop) -> prepare -> trigger (start)
> So, be careful about refcounting and active flags.
Hmm, I don't think I follow here. snd_usb_endpoint_{de,}activate() don't
actually touch the refcounts but act upon the "activated" flag, and
snd_usb_endpoint_{start,stop}() will touch the refcounts only. Hence, an
unbalanced call to activate() would basically be a noop. Do I miss your
point?
> And, yes, the protection for snd_usb_add_endpoint() would be really
> needed for concurrent access. The card-global mutex would be enough.
Ok. However, there is actually no card-global mutex for that purpose,
right? I'll add one :)
Thanks,
Daniel
prev parent reply other threads:[~2011-11-02 8:27 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 12:10 [PATCH 0/5] RFC for snd-usb: rework usb endpoint logic Daniel Mack
2011-10-31 12:10 ` [PATCH 1/5] ALSA: snd-usb: implement new endpoint streaming model Daniel Mack
2011-11-01 20:57 ` Clemens Ladisch
2011-11-02 8:36 ` Daniel Mack
2011-11-02 10:26 ` Clemens Ladisch
2011-11-02 14:29 ` Daniel Mack
2011-11-02 15:49 ` Clemens Ladisch
2011-11-03 15:21 ` Daniel Mack
2011-11-03 16:42 ` Clemens Ladisch
2011-10-31 12:10 ` [PATCH 2/5] ALSA: snd-usb: switch over to new endpoint streaming logic Daniel Mack
2011-11-01 20:57 ` Clemens Ladisch
2011-11-02 15:58 ` Takashi Iwai
2011-11-02 16:18 ` Clemens Ladisch
2011-11-02 16:18 ` Takashi Iwai
2011-11-02 22:01 ` Torsten Schenk
2011-11-18 14:44 ` Daniel Mack
2011-11-18 14:41 ` Daniel Mack
2011-10-31 12:10 ` [PATCH 3/5] ALSA: snd-usb: remove old " Daniel Mack
2011-10-31 12:10 ` [PATCH 4/5] ALSA: snd-usb: set MAX_URBS to 16 Daniel Mack
2011-11-01 20:57 ` Clemens Ladisch
2011-10-31 12:10 ` [PATCH 5/5] ALSA: snd-usb: add support for implicit feedback Daniel Mack
2011-10-31 12:38 ` [PATCH 0/5] RFC for snd-usb: rework usb endpoint logic Daniel Mack
2011-11-01 8:50 ` Aurélien Leblond
2011-11-01 9:15 ` Daniel Mack
2011-11-01 9:40 ` Felix Homann
2011-11-01 10:25 ` Daniel Mack
2011-11-01 10:39 ` Felix Homann
2011-11-01 12:11 ` Daniel Mack
2011-11-01 13:59 ` Grant Diffey
2011-11-01 15:36 ` Takashi Iwai
2011-11-01 16:19 ` Takashi Iwai
2011-11-01 19:03 ` Felix Homann
2011-11-02 6:49 ` Takashi Iwai
2011-11-02 8:27 ` Daniel Mack [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=4EB0FEF2.9000205@gmail.com \
--to=zonque@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=blablack@gmail.com \
--cc=clemens@ladisch.de \
--cc=gdiffey@gmail.com \
--cc=linuxaudio@showlabor.de \
--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.