mirror of
https://gitlab.freedesktop.org/pulseaudio/pulseaudio.git
synced 2025-11-02 09:01:46 -05:00
thread-mainloop: Extend the locking documentation a bit
Make it more clear which objects require locking. I remember talking to multiple people for whom that wasn't immediately clear from the documentation.
This commit is contained in:
parent
36a4923f9b
commit
3dc525df5d
1 changed files with 5 additions and 3 deletions
|
|
@ -66,9 +66,11 @@ PA_C_DECL_BEGIN
|
||||||
* number of times you called pa_threaded_mainloop_lock().
|
* number of times you called pa_threaded_mainloop_lock().
|
||||||
*
|
*
|
||||||
* The lock needs to be held whenever you call any PulseAudio function that
|
* The lock needs to be held whenever you call any PulseAudio function that
|
||||||
* uses an object associated with this main loop. Make sure you do not hold
|
* uses an object associated with this main loop. Those objects include
|
||||||
* on to the lock more than necessary though, as the threaded main loop stops
|
* pa_mainloop, pa_context, pa_stream and pa_operation, and the various event
|
||||||
* while the lock is held.
|
* objects (pa_io_event, pa_time_event, pa_defer_event). Make sure you do not
|
||||||
|
* hold on to the lock more than necessary though, as the threaded main loop
|
||||||
|
* stops while the lock is held.
|
||||||
*
|
*
|
||||||
* Example:
|
* Example:
|
||||||
*
|
*
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue