Searched refs:releasing (Results 1 – 25 of 41) sorted by relevance
12
| /Linux-v4.19/drivers/staging/greybus/ |
| D | light.c | 43 bool releasing; member
124 if (channel->releasing) in __gb_lights_flash_intensity_set()
327 if (channel->releasing) in gb_lights_fade_set()
353 if (channel->releasing) in gb_lights_color_set()
423 if (channel->releasing) in __gb_lights_brightness_set()
462 if (channel->releasing) in gb_blink_set()
642 if (channel->releasing) in gb_lights_flash_strobe_set()
683 if (channel->releasing) in gb_lights_flash_timeout_set()
715 if (channel->releasing) in gb_lights_flash_fault_get()
1091 channel->releasing = true; in gb_lights_channel_release()
|
| /Linux-v4.19/Documentation/devicetree/bindings/i2c/ |
| D | i2c-mux-gpmux.txt | 35 + between the child bus I2C transaction and releasing of the multiplexer
36 + during releasing of the multiplexer
|
| /Linux-v4.19/tools/memory-model/litmus-tests/ |
| D | MP+polocks.litmus | 8 * In other words, when holding a given lock (or indeed after releasing a
|
| D | MP+porevlocks.litmus | 8 * In other words, when holding a given lock (or indeed after releasing a
|
| /Linux-v4.19/Documentation/devicetree/bindings/gpio/ |
| D | spear_spics.txt | 8 transfers without releasing their chipselects.
|
| /Linux-v4.19/drivers/scsi/ibmvscsi_tgt/ |
| D | ibmvscsi_tgt.h | 199 bool releasing; member
|
| /Linux-v4.19/include/linux/ |
| D | tee_drv.h | 56 bool releasing; member
|
| /Linux-v4.19/Documentation/fmc/ |
| D | API.txt | 27 The fmc-bus itself takes care of releasing the structure when their use
|
| /Linux-v4.19/Documentation/hwmon/ |
| D | abituguru3 | 53 Despite Abit not releasing any information regarding the uGuru revision 3,
|
| D | abituguru | 85 Despite Abit not releasing any information regarding the uGuru, Olle
|
| /Linux-v4.19/drivers/tee/ |
| D | tee_core.c | 74 if (ctx->releasing) in teedev_ctx_get()
84 ctx->releasing = true; in teedev_ctx_release()
91 if (ctx->releasing) in teedev_ctx_put()
|
| /Linux-v4.19/Documentation/locking/ |
| D | rt-mutex.txt | 68 To prevent a cmpxchg of the owner releasing the lock, we need to
|
| /Linux-v4.19/Documentation/vm/ |
| D | mmu_notifier.rst | 99 releasing page table lock but before call mmu_notifier_invalidate_range_end().
|
| D | page_migration.rst | 243 under page_lock before the releasing the page.
|
| /Linux-v4.19/Documentation/dev-tools/ |
| D | sparse.rst | 69 releasing the lock inside the function in a balanced way, no
|
| /Linux-v4.19/Documentation/ |
| D | DMA-ISA-LPC.txt | 109 The final step is enabling the DMA channel and releasing the DMA
|
| D | DMA-attributes.txt | 93 device domain after releasing a mapping for it. Use this attribute with
|
| D | kref.txt | 126 any more and releasing it. The kref_get() does not require a lock,
|
| /Linux-v4.19/Documentation/fb/ |
| D | sstfb.txt | 12 in progress, I feel uncomfortable with releasing tarballs of something
|
| /Linux-v4.19/Documentation/driver-api/ |
| D | device-io.rst | 117 Generally, one should use :c:func:`mmiowb()` prior to releasing a spinlock
|
| /Linux-v4.19/Documentation/networking/ |
| D | udplite.txt | 203 the last packet before releasing the fragments to the IP module.
|
| /Linux-v4.19/Documentation/filesystems/caching/ |
| D | object.txt | 317 Because the withdrawing releasing/retiring events are all handled by the object
|
| /Linux-v4.19/Documentation/userspace-api/ |
| D | unshare.rst | 201 current task and releasing older shared structures. Failure
|
| /Linux-v4.19/Documentation/isdn/ |
| D | INTERFACE.CAPI | 123 releasing all registered applications
|
| /Linux-v4.19/Documentation/security/ |
| D | self-protection.rst | 305 When releasing memory, it is best to poison the contents (clear stack on
|
12
