-
-
- Introduction -
- Sphinx Install -
- Sphinx Build -
- Writing Documentation -
- Figures & Images -
- Writing kernel-doc comments -
- Including kernel-doc comments -
- Including uAPI header files -
- How to help improve kernel documentation -
- Documentation subsystem maintainer entry profile
-
-
- Submit checklist addendum -
- Key cycle dates -
- Review cadence +
- How to write kernel documentation +
- Kernel Hacking Guides +
- Linux Tracing Technologies +
- Kernel Maintainer Handbook -
- Kernel Hacking Guides -
- Linux Tracing Technologies -
- Kernel Maintainer Handbook
- fault-injection
- Kernel Livepatching
The kernel figure (and image) directive support DOT formated files, see
-
/usr/share/doc/kernel/html/rst/driver-api/basics.html differs (HTML document, UTF-8 Unicode text, with very long lines)
--- old//usr/share/doc/kernel/html/rst/driver-api/basics.html 2020-06-24 21:53:44.378378236 +0000
+++ new//usr/share/doc/kernel/html/rst/driver-api/basics.html 2020-06-24 21:53:44.378378236 +0000
@@ -4923,7 +4923,7 @@
-
snd_printk(fmt, …)¶
@@ -379,7 +379,7 @@
- @@ -425,7 +425,7 @@
- @@ -577,9 +577,9 @@
-
snd_pcm_group_for_each_entry(s, substream)¶
@@ -838,7 +838,7 @@
-
-int
snd_pcm_notify(struct snd_pcm_notify * notify, int nfree)¶
+int Add/remove the notify list
- @@ -1523,7 +1523,7 @@
-
int
snd_rawmidi_transmit_peek(struct snd_rawmidi_substream * substream, unsigned char * buffer, int count)¶
@@ -1542,7 +1542,7 @@
-
int
snd_rawmidi_transmit_ack(struct snd_rawmidi_substream * substream, int count)¶
@@ -1635,7 +1635,7 @@
struct snd_pcm_substream * substreamthe substream with a buffer allocated by -
+snd_pcm_lib_alloc_vmalloc_buffer()snd_pcm_lib_alloc_vmalloc_buffer()struct snd_pcm_substream * substreamthe substream with a buffer allocated by /usr/share/doc/kernel/html/rst/gpu/amdgpu.html differs (HTML document, UTF-8 Unicode text, with very long lines) --- old//usr/share/doc/kernel/html/rst/gpu/amdgpu.html 2020-06-24 21:53:44.590379778 +0000 +++ new//usr/share/doc/kernel/html/rst/gpu/amdgpu.html 2020-06-24 21:53:44.590379778 +0000 @@ -2867,7 +2867,7 @@ a DRM hotplug event to alert userspace.
This design approach is required in order to defer hotplug event handling from the IRQ handler to a work handler because hotplug handler has to use -mutexes which cannot be locked in an IRQ handler (since
mutex_lockmay +mutexes which cannot be locked in an IRQ handler (sincemutex_lockmay sleep).- /usr/share/doc/kernel/html/rst/gpu/drm-kms.html differs (HTML document, UTF-8 Unicode text, with very long lines) --- old//usr/share/doc/kernel/html/rst/gpu/drm-kms.html 2020-06-24 21:53:44.946382369 +0000 +++ new//usr/share/doc/kernel/html/rst/gpu/drm-kms.html 2020-06-24 21:53:44.942382339 +0000 @@ -8960,7 +8960,7 @@
-
bool
drm_modeset_is_locked(struct drm_modeset_lock * lock)¶
- equivalent to
+mutex_is_locked()equivalent to
mutex_is_locked()-
int
drm_modeset_lock_single_interruptible(struct drm_modeset_lock * lock)¶
/usr/share/doc/kernel/html/rst/kernel-hacking/locking.html differs (HTML document, UTF-8 Unicode text, with very long lines)
--- old//usr/share/doc/kernel/html/rst/kernel-hacking/locking.html 2020-06-24 21:53:45.010382834 +0000
+++ new//usr/share/doc/kernel/html/rst/kernel-hacking/locking.html 2020-06-24 21:53:45.010382834 +0000
@@ -456,9 +456,9 @@
Parameters
@@ -9180,7 +9180,7 @@DRM_MODESET_ACQUIRE_INTERRUPTIBLE, this function will fail with -ERESTARTSYS when interrupted.If ctx is NULL then the function call behaves like a normal, -uninterruptible non-nesting
+uninterruptible non-nestingmutex_lock()call.mutex_lock()call.If you have a data structure which is only ever accessed from user context, then you can use a simple mutex (
include/linux/mutex.h) to protect it. This is the most trivial case: you initialize the mutex. -Then you can callmutex_lock_interruptible()to grab the -mutex, andmutex_unlock()to release it. There is also a -mutex_lock(), which should be avoided, because it will +Then you can callmutex_lock_interruptible()to grab the +mutex, andmutex_unlock()to release it. There is also a +mutex_lock(), which should be avoided, because it will not return if a signal is received.Example:
-net/netfilter/nf_sockopt.callows registration of new setsockopt() and getsockopt() calls, with @@ -794,7 +794,7 @@ used in all contexts like spin_lock(): you must have disabled the contexts that might interrupt you and acquire the spin lock.mutex_trylock()does not suspend your task but returns +
@@ -1680,11 +1680,11 @@mutex_trylock()does not suspend your task but returns non-zero if it could lock the mutex on the first try or 0 if not. This function cannot be safely used in hardware or software interrupt contexts despite not sleeping.
Description
-Similar to
atomic_dec_and_mutex_lock(), it will WARN on underflow and fail +Similar to
atomic_dec_and_mutex_lock(), it will WARN on underflow and fail to decrement when saturated at REFCOUNT_SATURATED.Provides release memory ordering, such that prior loads and stores are done before, and provides a control dependency such that free() must come after. @@ -5583,7 +5583,7 @@
Description
This is on behalf of the oom reaper, specifically when it is calling the mmu notifiers. The problem is that if the notifier were to block on, for example, -
/usr/share/doc/kernel/html/rst/driver-api/sound.html differs (HTML document, UTF-8 Unicode text, with very long lines) --- old//usr/share/doc/kernel/html/rst/driver-api/sound.html 2020-06-24 21:53:44.482378992 +0000 +++ new//usr/share/doc/kernel/html/rst/driver-api/sound.html 2020-06-24 21:53:44.482378992 +0000 @@ -347,8 +347,8 @@mutex_lock()and if the process which holds that mutex were to perform a +mutex_lock()and if the process which holds that mutex were to perform a sleeping memory allocation, the oom reaper is now blocked on completion of that memory allocation. Other blocking calls likewait_event()pose similar issues.Description
-Call this function for the card object that was obtained via
+snd_card_ref()-orsnd_lookup_minor_data().Call this function for the card object that was obtained via
snd_card_ref()+orsnd_lookup_minor_data().Description
-Works like
snd_printk()for debugging purposes. +Works like
snd_printk()for debugging purposes. Ignored when CONFIG_SND_DEBUG is not set.Description
-Works like
snd_printk()for debugging purposes. +Works like
snd_printk()for debugging purposes. Ignored when CONFIG_SND_DEBUG_VERBOSE is not set.Description
-This locks the PCM stream like
snd_pcm_stream_lock()but with the local +This locks the PCM stream like
+assnd_pcm_stream_lock()but with the local IRQ (only when nonatomic is false). In nonatomic case, this is identical -assnd_pcm_stream_lock().snd_pcm_stream_lock().Description
When multiple substreams of the same card are linked and the hardware supports the single-shot operation, the driver calls this in the loop -in
snd_pcm_group_for_each_entry()for marking the substream as “done”. +insnd_pcm_group_for_each_entry()for marking the substream as “done”. Then most of trigger operations are performed only to the given master substream.The trigger_master mark is cleared at timestamp updates at the end @@ -1004,7 +1004,7 @@
Description
-This function works like
snd_pcm_lib_alloc_vmalloc_buffer(), but uses +This function works like
snd_pcm_lib_alloc_vmalloc_buffer(), but usesvmalloc_32(), i.e., the pages are allocated from 32-bit-addressable memory.Return
1 if the buffer was changed, 0 if not changed, or a negative error @@ -1167,7 +1167,7 @@
Creates a new stream for the pcm. The corresponding stream on the pcm must have been empty before calling this, i.e. zero must be given to the argument of -
+snd_pcm_new().snd_pcm_new().Return
Zero if successful, or a negative error code on failure.
-
@@ -1194,7 +1194,7 @@
Description
Creates a new PCM instance.
The pcm operators have to be set afterwards to the new instance -via
+viasnd_pcm_set_ops().snd_pcm_set_ops().Return
Zero if successful, or a negative error code on failure.
-
@@ -1225,12 +1225,12 @@
by userspace. It provides existing ASoC components drivers with a substream
and access to any private data.
The pcm operators have to be set afterwards to the new instance -via
+viasnd_pcm_set_ops().snd_pcm_set_ops().Return
Zero if successful, or a negative error code on failure.
snd_pcm_notify(struct snd_pcm_notify * notify, int nfree)¶Description
Turns the device into the disconnection state, invoking dev_disconnect callback, if the device was already registered.
-Usually called from
+snd_card_disconnect().Usually called from
snd_card_disconnect().Return
Zero if successful, or a negative error code on failure or if the device not found.
@@ -1322,9 +1322,9 @@Description
Registers the device which was already created via -
+invocation ofsnd_device_new(). Usually this is called fromsnd_card_register(), +snd_device_new(). Usually this is called fromsnd_card_register(), but it can be called later if any new devices are created after -invocation ofsnd_card_register().snd_card_register().Return
Zero if successful, or a negative error code on failure or if the device not found.
@@ -1473,7 +1473,7 @@Description
-This proc file entry will be registered via
snd_card_register()call, and +This proc file entry will be registered via
snd_card_register()call, and it will be removed automatically at the card removal, too.Description
-This is a variant of
+snd_rawmidi_transmit_peek()without spinlock.This is a variant of
snd_rawmidi_transmit_peek()without spinlock.Description
Copies data from the internal output buffer to the given buffer.
Call this in the interrupt handler when the midi output is ready, -and call
snd_rawmidi_transmit_ack()after the transmission is +and callsnd_rawmidi_transmit_ack()after the transmission is finished.Return
The size of copied data, or a negative error code on failure.
@@ -1560,7 +1560,7 @@Description
-This is a variant of
+__snd_rawmidi_transmit_ack()without spinlock.This is a variant of
__snd_rawmidi_transmit_ack()without spinlock.Description
Creates a new rawmidi instance. -Use
+Usesnd_rawmidi_set_ops()to set the operators to the new instance.snd_rawmidi_set_ops()to set the operators to the new instance.Return
Zero if successful, or a negative error code on failure.
-
@@ -1687,7 +1687,7 @@
its user data pointer.
This function increments the reference counter of the card instance if an associated instance with the given minor number and type is found. -The caller must call
+The caller must callsnd_card_unref()appropriately later.snd_card_unref()appropriately later.Return
The user data pointer if the specified device is found.
@@ -1730,7 +1730,7 @@NULLotherwise.Description
Unregisters the device file already registered via -
+snd_register_device().snd_register_device().Return
Zero if successful, or a negative error code on failure.
-
@@ -1909,7 +1909,7 @@
Description
-Releases the DMA buffer allocated via
+snd_pcm_lib_malloc_pages().Releases the DMA buffer allocated via
snd_pcm_lib_malloc_pages().Return
Zero if successful, or a negative error code on failure.
-
@@ -1921,7 +1921,7 @@
Parameters
Return
@@ -1935,7 +1935,7 @@Parameters
kmalloc(GP_KERNEL) <kmalloc>`
-
-mutex_lock_interruptible()and -mutex_lock()There is a
mutex_trylock()which does not sleep. +
+mutex_lock_interruptible()and +mutex_lock()There is a
mutex_trylock()which does not sleep. Still, it must not be used inside interrupt context since its -implementation is not safe for that.mutex_unlock()+implementation is not safe for that.mutex_unlock()will also never sleep. It cannot be used in interrupt context either since a mutex must be released by the same task that acquired it.
@@ -1822,7 +1822,7 @@
-
-struct futex_q *
futex_top_waiter(struct futex_hash_bucket * hb, union futex_key * key)¶
+struct futex_q * Return the highest priority waiter on a futex
-
-void
__unqueue_futex(struct futex_q * q)¶
+void Remove the futex_q from its futex_hash_bucket
-
-void
requeue_futex(struct futex_q * q, struct futex_hash_bucket * hb1, struct futex_hash_bucket * hb2, union futex_key * key2)¶
+void Requeue a futex_q from one hb to another
-
-void
requeue_pi_wake_futex(struct futex_q * q, union futex_key * key, struct futex_hash_bucket * hb)¶
+void Wake a task that acquired the lock during requeue
-
-void
queue_me(struct futex_q * q, struct futex_hash_bucket * hb)¶
+void Enqueue the futex_q on the futex_hash_bucket
-
-int
unqueue_me(struct futex_q * q)¶
+int Remove the futex_q from its futex_hash_bucket
-
-int
fixup_owner(u32 __user * uaddr, struct futex_q * q, int locked)¶
+int Post lock pi_state and corner case management
-
-void
futex_wait_queue_me(struct futex_hash_bucket * hb, struct futex_q * q, struct hrtimer_sleeper * timeout)¶
-
+voidqueue_me()and wait for wakeup, timeout, or signalfutex_wait_queue_me(struct futex_hash_bucket * hb, struct futex_q * q, struct hrtimer_sleeper * timeout)¶ +queue_me()and wait for wakeup, timeout, or signal-
-int
futex_wait_setup(u32 __user * uaddr, u32 val, unsigned int flags, struct futex_q * q, struct futex_hash_bucket ** hb)¶
+int Prepare to wait on a futex
-
-int
handle_early_requeue_pi_wakeup(struct futex_hash_bucket * hb, struct futex_q * q, union futex_key * key2, struct hrtimer_sleeper * timeout)¶
+int Detect early wakeup on the initial futex
Description
-Lock the mutex like mutex_lock(). If a signal is delivered while the
+
Lock the mutex like mutex_lock(). If a signal is delivered while the
process is sleeping, this function will return without acquiring the
mutex.
Context
@@ -1842,7 +1842,7 @@Description
-Lock the mutex like mutex_lock(). If a signal which will be fatal to
+
Lock the mutex like mutex_lock(). If a signal which will be fatal to
the current process is delivered while the process is sleeping, this
function will return without acquiring the mutex.
Context
@@ -1862,7 +1862,7 @@Description
-Lock the mutex like mutex_lock(). While the task is waiting for this
+
Lock the mutex like mutex_lock(). While the task is waiting for this
mutex, it will be accounted as being in the IO wait state by the
scheduler.
Context
@@ -2056,7 +2056,7 @@ calling get_user_pages() right away.futex_top_waiter(struct futex_hash_bucket * hb, union futex_key * key)¶
__unqueue_futex(struct futex_q * q)¶
The q->lock_ptr must not be NULL and must be held by the caller.
requeue_futex(struct futex_q * q, struct futex_hash_bucket * hb1, struct futex_hash_bucket * hb2, union futex_key * key2)¶
requeue_pi_wake_futex(struct futex_q * q, union futex_key * key, struct futex_hash_bucket * hb)¶
Description
Try and get the lock on behalf of the top waiter if we can do it atomically.
Wake the top waiter if we succeed. If the caller specified set_waiters,
-then direct futex_lock_pi_atomic() to force setting the FUTEX_WAITERS bit.
+then direct futex_lock_pi_atomic() to force setting the FUTEX_WAITERS bit.
hb1 and hb2 must be held by the caller.
exiting is only set when the return value is -EBUSY. If so, this holds a refcount on the exiting task on return and the caller needs to drop it @@ -2253,7 +2253,7 @@
queue_me(struct futex_q * q, struct futex_hash_bucket * hb)¶
Description
The hb->lock must be held by the caller, and is released here. A call to
-queue_me() is typically paired with exactly one call to unqueue_me(). The
+queue_me() is typically paired with exactly one call to unqueue_me(). The
exceptions involve the PI related operations, which may use unqueue_me_pi()
or nothing if the unqueue is done as part of the wake process and the unqueue
-state is implicit in the state of woken task (see futex_wait_requeue_pi() for
+state is implicit in the state of woken task (see futex_wait_requeue_pi() for
an example).
unqueue_me(struct futex_q * q)¶
Description
-The q->lock_ptr must not be held by the caller. A call to unqueue_me() must
-be paired with exactly one earlier call to queue_me().
The q->lock_ptr must not be held by the caller. A call to unqueue_me() must
+be paired with exactly one earlier call to queue_me().
Return
@@ -2294,7 +2294,7 @@
fixup_owner(u32 __user * uaddr, struct futex_q * q, int locked)¶
Parameters
@@ -2336,7 +2336,7 @@futex_wait_setup(u32 __user * uaddr, u32 val, unsigned int flags, struct futex_q * q, struct futex_hash_bucket ** hb)¶
handle_early_requeue_pi_wakeup(struct futex_hash_bucket * hb, struct futex_q * q, union futex_key * key2, struct hrtimer_sleeper * timeout)¶
Description
-The caller will wait on uaddr and will be requeued by futex_requeue() to
+
The caller will wait on uaddr and will be requeued by futex_requeue() to
uaddr2 which must be PI aware and unique from uaddr. Normal wakeup will wake
on uaddr2 and complete the acquisition of the rt_mutex prior to returning to
userspace. This ensures the rt_mutex maintains an owner when it has waiters;
without one, the pi logic would not know which task to boost/deboost, if
there was a need to.
We call schedule in futex_wait_queue_me() when we enqueue and return there
/usr/share/doc/kernel/html/rst/locking/locktorture.html differs (HTML document, UTF-8 Unicode text, with very long lines)
--- old//usr/share/doc/kernel/html/rst/locking/locktorture.html 2020-06-24 21:53:45.034383008 +0000
+++ new//usr/share/doc/kernel/html/rst/locking/locktorture.html 2020-06-24 21:53:45.034383008 +0000
@@ -326,7 +326,7 @@
-
-
- “mutex_lock”:
+mutex_lock()andmutex_unlock()pairs.- “mutex_lock”:
mutex_lock()andmutex_unlock()pairs.
Constants
-
-
V4L2_ASYNC_MATCH_CUSTOMMatch will use the logic provided by
struct +V4L2_ASYNC_MATCH_CUSTOMMatch will use the logic provided by
struct v4l2_async_subdev.match opsV4L2_ASYNC_MATCH_DEVNAMEMatch will use the device name
@@ -377,7 +377,7 @@
Description
When this struct is used as a member in a driver specific struct,
-the driver specific struct shall contain the struct
+the driver specific struct shall contain the struct
v4l2_async_subdev as its first member.
- @@ -443,13 +443,13 @@
-
-void
v4l2_async_notifier_init(struct v4l2_async_notifier * notifier)¶
+void Initialize a notifier.
v4l2_async_notifier_init(struct v4l2_async_notifier * notifier)¶
Parameters
-
-
struct v4l2_async_notifier * notifierpointer to
+struct v4l2_async_notifierstruct v4l2_async_notifier * notifierpointer to
struct v4l2_async_notifier
Description
@@ -457,15 +457,15 @@ before the first call to v4l2_async_notifier_add_subdev.-
-int
v4l2_async_notifier_add_subdev(struct v4l2_async_notifier * notifier, struct v4l2_async_subdev * asd)¶
+int Add an async subdev to the notifier’s master asd list.
v4l2_async_notifier_add_subdev(struct v4l2_async_notifier * notifier, struct v4l2_async_subdev * asd)¶
Parameters
-
-
struct v4l2_async_notifier * notifierpointer to
+struct v4l2_async_notifierstruct v4l2_async_notifier * notifierpointer to
struct v4l2_async_notifier
-struct v4l2_async_subdev * asdpointer to
+struct v4l2_async_subdevstruct v4l2_async_subdev * asdpointer to
struct v4l2_async_subdev
Description
@@ -473,18 +473,18 @@ provided asd to the notifiers master asd_list.-
-struct v4l2_async_subdev *
v4l2_async_notifier_add_fwnode_subdev(struct v4l2_async_notifier * notifier, struct fwnode_handle * fwnode, unsigned int asd_struct_size)¶
+struct v4l2_async_subdev * Allocate and add a fwnode async subdev to the notifier’s master asd_list.
v4l2_async_notifier_add_fwnode_subdev(struct v4l2_async_notifier * notifier, struct fwnode_handle * fwnode, unsigned int asd_struct_size)¶
Parameters
-
-
struct v4l2_async_notifier * notifierpointer to
+struct v4l2_async_notifierstruct v4l2_async_notifier * notifierpointer to
struct v4l2_async_notifierstruct fwnode_handle * fwnodefwnode handle of the sub-device to be matched
unsigned int asd_struct_sizesize of the driver’s async sub-device struct, including -sizeof(struct v4l2_async_subdev). The
@@ -496,17 +496,17 @@ is released later at notifier cleanup time.struct +sizeof(struct v4l2_async_subdev). Thestruct v4l2_async_subdevshall be the first member of the driver’s async sub-device struct, i.e. both begin at the same memory address.-
-int
v4l2_async_notifier_add_fwnode_remote_subdev(struct v4l2_async_notifier * notif, struct fwnode_handle * endpoint, struct v4l2_async_subdev * asd)¶
+int Allocate and add a fwnode remote async subdev to the notifier’s master asd_list.
v4l2_async_notifier_add_fwnode_remote_subdev(struct v4l2_async_notifier * notif, struct fwnode_handle * endpoint, struct v4l2_async_subdev * asd)¶Parameters
-
-
struct v4l2_async_notifier * notifpointer to
+struct v4l2_async_notifierstruct v4l2_async_notifier * notifpointer to
struct v4l2_async_notifierstruct fwnode_handle * endpointlocal endpoint pointing to the remote sub-device to be matched
-struct v4l2_async_subdev * asdAsync sub-device struct allocated by the caller. The
struct +struct v4l2_async_subdev * asdAsync sub-device struct allocated by the caller. The
struct v4l2_async_subdevshall be the first member of the driver’s async sub-device struct, i.e. both begin at the same memory address.-
-struct v4l2_async_subdev *
v4l2_async_notifier_add_i2c_subdev(struct v4l2_async_notifier * notifier, int adapter_id, unsigned short address, unsigned int asd_struct_size)¶
+struct v4l2_async_subdev * Allocate and add an i2c async subdev to the notifier’s master asd_list.
v4l2_async_notifier_add_i2c_subdev(struct v4l2_async_notifier * notifier, int adapter_id, unsigned short address, unsigned int asd_struct_size)¶Parameters
-
-
struct v4l2_async_notifier * notifierpointer to
+struct v4l2_async_notifierstruct v4l2_async_notifier * notifierpointer to
struct v4l2_async_notifierint adapter_idI2C adapter ID to be matched
unsigned short addressI2C address of sub-device to be matched
unsigned int asd_struct_sizesize of the driver’s async sub-device struct, including -sizeof(struct v4l2_async_subdev). The
@@ -544,18 +544,18 @@struct +sizeof(struct v4l2_async_subdev). Thestruct v4l2_async_subdevshall be the first member of the driver’s async sub-device struct, i.e. both begin at the same memory address.Same as above but for I2C matched sub-devices.
-
-struct v4l2_async_subdev *
v4l2_async_notifier_add_devname_subdev(struct v4l2_async_notifier * notifier, const char * device_name, unsigned int asd_struct_size)¶
+struct v4l2_async_subdev * Allocate and add a device-name async subdev to the notifier’s master asd_list.
v4l2_async_notifier_add_devname_subdev(struct v4l2_async_notifier * notifier, const char * device_name, unsigned int asd_struct_size)¶Parameters
-
-
struct v4l2_async_notifier * notifierpointer to
+struct v4l2_async_notifierstruct v4l2_async_notifier * notifierpointer to
struct v4l2_async_notifierconst char * device_namedevice name string to be matched
unsigned int asd_struct_sizesize of the driver’s async sub-device struct, including -sizeof(struct v4l2_async_subdev). The
@@ -565,7 +565,7 @@struct +sizeof(struct v4l2_async_subdev). Thestruct v4l2_async_subdevshall be the first member of the driver’s async sub-device struct, i.e. both begin at the same memory address.Same as above but for device-name matched sub-devices.
-
-int
v4l2_async_notifier_register(struct v4l2_device * v4l2_dev, struct v4l2_async_notifier * notifier)¶
+int registers a subdevice asynchronous notifier
v4l2_async_notifier_register(struct v4l2_device * v4l2_dev, struct v4l2_async_notifier * notifier)¶struct v4l2_device * v4l2_devpointer to
struct v4l2_device
-struct v4l2_async_notifier * notifierpointer to
+struct v4l2_async_notifierstruct v4l2_async_notifier * notifierpointer to
struct v4l2_async_notifier
-
-int
v4l2_async_subdev_notifier_register(struct v4l2_subdev * sd, struct v4l2_async_notifier * notifier)¶
+int registers a subdevice asynchronous notifier for a sub-device
v4l2_async_subdev_notifier_register(struct v4l2_subdev * sd, struct v4l2_async_notifier * notifier)¶struct v4l2_subdev * sdpointer to
struct v4l2_subdev
-struct v4l2_async_notifier * notifierpointer to
+struct v4l2_async_notifierstruct v4l2_async_notifier * notifierpointer to
struct v4l2_async_notifier
-
-void
v4l2_async_notifier_unregister(struct v4l2_async_notifier * notifier)¶
+void unregisters a subdevice asynchronous notifier
v4l2_async_notifier_unregister(struct v4l2_async_notifier * notifier)¶Parameters
-
-
struct v4l2_async_notifier * notifierpointer to
+struct v4l2_async_notifierstruct v4l2_async_notifier * notifierpointer to
struct v4l2_async_notifier
-
-void
v4l2_async_notifier_cleanup(struct v4l2_async_notifier * notifier)¶
+void clean up notifier resources
v4l2_async_notifier_cleanup(struct v4l2_async_notifier * notifier)¶-
-int
Description
/usr/share/doc/kernel/html/rst/media/kapi/v4l2-fwnode.html differs (HTML document, UTF-8 Unicode text, with very long lines) --- old//usr/share/doc/kernel/html/rst/media/kapi/v4l2-fwnode.html 2020-06-24 21:53:45.102383504 +0000 +++ new//usr/share/doc/kernel/html/rst/media/kapi/v4l2-fwnode.html 2020-06-24 21:53:45.102383504 +0000 @@ -764,7 +764,7 @@-
-struct v4l2_async_subdev *
struct v4l2_fwnode_endpoint * veppointer to
struct v4l2_fwnode_endpoint
-struct v4l2_async_subdev * asdpointer to
+struct v4l2_async_subdevstruct v4l2_async_subdev * asdpointer to
struct v4l2_async_subdev
Return
@@ -776,7 +776,7 @@
-
-int