From cccb74800012899baf85926e2e73b8bd790ecacb Mon Sep 17 00:00:00 2001 From: Laurent Pinchart Date: Sat, 22 May 2021 00:17:23 +0300 Subject: libcamera: thread: Drop doc of asynchronous signals delivery to applications MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The asynchronous signal delivery mechanism can't be used by application, as it requires libcamera to be aware of the application event loop, which has been dropped a long time ago. Drop the corresponding documentation paragraph. Signed-off-by: Laurent Pinchart Reviewed-by: Niklas Söderlund Reviewed-by: Umang Jain Reviewed-by: Hirokazu Honda --- src/libcamera/thread.cpp | 8 -------- 1 file changed, 8 deletions(-) (limited to 'src') diff --git a/src/libcamera/thread.cpp b/src/libcamera/thread.cpp index bc1dcede..d59e4396 100644 --- a/src/libcamera/thread.cpp +++ b/src/libcamera/thread.cpp @@ -64,14 +64,6 @@ * be overridden by selecting a different connection type when calling * Signal::connect(). * - * Asynchronous signal delivery is used internally in libcamera, but is also - * available to applications if desired. To use this feature, applications - * shall create receiver classes that inherit from the Object class, and - * provide an event loop to the CameraManager as explained above. Note that - * Object instances created by the application are limited to living in the - * application's main thread. Creating Object instances from another thread of - * an application causes undefined behaviour. - * * \section thread-reentrancy Reentrancy and Thread-Safety * * Through the documentation, several terms are used to define how classes and -- cgit v1.2.1