Searched full:called (Results 1 – 25 of 877) sorted by relevance
12345678910>>...36
| /Documentation/filesystems/ |
| D | vfs.rst | 22 are called from a process context. Filesystem locking is described in
70 taken from the inode data. The open() file method is then called so the
288 All methods are called without any locks being held, unless otherwise
290 only called from a process context (i.e. not from an interrupt handler
294 this method is called by alloc_inode() to allocate memory for
301 this method is called by destroy_inode() to release resources
307 this method is called from RCU callback. If you use call_rcu()
312 this method is called by the VFS when an inode is marked dirty.
321 this method is called when the VFS needs to write an inode to
326 called when the last access to the inode is dropped, with the
[all …]
|
| D | netfs_library.rst | 161 If an error occurs, the ->free_request() will be called to clean up the
172 which should be called to complete a read subrequest. This is given the number
311 [Optional] This is called to initialise the request structure. It is given
316 [Optional] This is called as the request is being deallocated so that the
321 [Optional] This is called to allow the filesystem to expand the size of a
333 [Optional] This is called to allow the filesystem to reduce the size of a
347 called to indicate whether or not the operation succeeded and how much data
359 [Optional] This is called to find out if the data just read from the local
365 [Optional] This is called from the netfs_write_begin() helper once it has
376 [Optional] This is called after the folios in the request have all been
[all …]
|
| D | configfs.rst | 168 called on it. This initializes the reference count and sets up the
203 method. This method is called when the config_item's reference count
227 be called whenever userspace asks for a read(2) on the attribute. If an
229 called whenever userspace asks for a write(2) on the attribute.
254 ct_item_ops->read_bin_attribute() method, that method will be called
299 ct_group_ops->make_item() method. If provided, this method is called from
310 ct_group_ops->drop_item() is called. As a config_group is also a
319 is called, configfs WILL remove the item from the filesystem tree
326 When drop_item() is called, the item's linkage has already been torn
330 ct_group_ops->disconnect_notify() method. The method is called after
[all …]
|
| D | porting.rst | 104 and ->readdir() are called without BKL now. Grab it on entry, drop upon return
156 ->setattr() is called without BKL now. Caller _always_ holds ->i_mutex, so
224 should be called on the inode to render it dead, and an appropriate error
251 * we are called from ->rename().
279 ->permission() is called without BKL now. Grab it on entry, drop upon
289 ->statfs() is now called without BKL held. BKL should have been
330 for ATTR_SIZE and must be called in the beginning of ->setattr unconditionally.
335 be used instead. It gets called whenever the inode is evicted, whether it has
339 (or after) ->evict_inode() is called.
341 ->drop_inode() returns int now; it's called on final iput() with
[all …]
|
| /Documentation/core-api/ |
| D | debug-objects.rst | 70 This function is called whenever the initialization function of a real
71 object is called.
93 This function is called whenever the initialization function of a real
94 object which resides on the stack is called.
117 This function is called whenever the activation function of a real
118 object is called.
129 fixup_activate function is called if available. This is necessary to
142 This function is called whenever the deactivation function of a real
143 object is called.
155 This function is called to mark an object destroyed. This is useful to
[all …]
|
| /Documentation/driver-api/usb/ |
| D | callbacks.rst | 18 Called to see if the driver is willing to manage a particular
22 Called when the interface is no longer accessible, usually
37 Called when the device is going to be suspended.
40 Called when the device is being resumed.
43 Called when the suspended device has been reset instead
49 Called when the device is about to be reset.
52 Called after the device has been reset
62 against other USB callbacks. All callbacks are called from a task
89 to the interface you are called for and endpoint 0 of the device. Device
106 If you are called due to a physical disconnection, all your URBs will be
[all …]
|
| D | writing_usb_driver.rst | 71 disconnect function pointers are called when a device that matches the
141 function is called. The :c:type:`usb_device` structure, interface number and
159 function is called with the device pointer. The driver needs to clean
165 that were passed to the USB subsystem will be called from a user program
166 trying to talk to the device. The first function called will be open, as
180 After the open function is called, the read and write functions are
181 called to receive and send data to the device. In the ``skel_write``
217 called when the urb is finished by the USB subsystem. The callback
218 function is called in interrupt context, so caution must be taken not to
255 talk to the device, the release function in the driver is called. In
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-regulator | 6 Some regulator directories will contain a field called
32 Some regulator directories will contain a field called
72 Each regulator directory will contain a field called
96 Some regulator directories will contain a field called
111 Some regulator directories will contain a field called
126 Some regulator directories will contain a field called
151 Some regulator directories will contain a field called
166 Some regulator directories will contain a field called
181 Some regulator directories will contain a field called
196 Some regulator directories will contain a field called
[all …]
|
| D | sysfs-devices-state_synced | 9 .sync_state() callback hasn't been called yet. A value of 1
10 means the .sync_state() callback has been called.
18 this only when the sync_state() callback has been called --
25 sync_state() function if it hasn't been called already. The
|
| /Documentation/networking/ |
| D | strparser.rst | 20 In receive callback mode, the strparser is called from the data_ready
34 callbacks include a parse_msg function that is called to perform
36 that is called when a full message has been completed.
46 Called to initialize a stream parser. strp is a struct of type
50 are called by the stream parser (the callbacks are listed below).
69 strp_stop is called to completely stop stream parser operations.
70 This is called internally when the stream parser encounters an
71 error, and it is called from the upper layer to stop parsing
78 strp_done is called to release any resources held by the stream
79 parser instance. This must be called after the stream processor
[all …]
|
| /Documentation/scheduler/ |
| D | sched-stats.rst | 48 1) # of times sched_yield() was called
54 3) # of times schedule() was called
59 5) # of times try_to_wake_up() was called
60 6) # of times try_to_wake_up() was called to wake up the local cpu
83 1) # of times in this domain sched_balance_rq() was called when the
91 5) # of times in this domain pull_task() was called when the cpu
93 6) # of times in this domain pull_task() was called even though
95 7) # of times in this domain sched_balance_rq() was called but did
99 9) # of times in this domain sched_balance_rq() was called when the
107 13) # of times in this domain pull_task() was called when busy
[all …]
|
| /Documentation/crypto/ |
| D | crypto_engine.rst | 39 * ``prepare_crypt_hardware``: Called once before any prepare functions are
40 called.
42 * ``unprepare_crypt_hardware``: Called once after all unprepare functions have
43 been called.
45 * ``prepare_cipher_request``/``prepare_hash_request``: Called before each
49 * ``unprepare_cipher_request``/``unprepare_hash_request``: Called after each
|
| /Documentation/userspace-api/media/v4l/ |
| D | vidioc-streamon.rst | 45 has been called. Output hardware is disabled and no video signal is
46 produced until ``VIDIOC_STREAMON`` has been called.
49 been called for both the capture and output stream types.
64 ``VIDIOC_STREAMOFF`` is called without ever having called
74 If ``VIDIOC_STREAMON`` is called when streaming is already in progress,
75 or if ``VIDIOC_STREAMOFF`` is called when streaming is already stopped,
|
| /Documentation/trace/ |
| D | ftrace-uses.rst | 27 kernel comes with risks. A callback can be called from any context
28 (normal, softirq, irq, and NMI). Callbacks can also be called just before
31 can be called outside the protective scope of RCU.
41 is used to tell ftrace what function should be called as the callback
70 The registered callback will start being called some time after the
71 register_ftrace_function() is called and before it returns. The exact time
72 that callbacks start being called is dependent upon architecture and scheduling
77 no longer being called by functions after the unregister_ftrace_function()
97 This is the instruction pointer of the function that called the
114 As functions can be called from anywhere, and it is possible that a function
[all …]
|
| /Documentation/ABI/stable/ |
| D | vdso | 8 maps an ELF DSO into that program's address space. This DSO is called
12 These functions are called according to your platform's ABI. On many
13 platforms they are called just like ordinary C function. On other platforms
14 (ex: powerpc) they are called with the same convention as system calls which
|
| /Documentation/driver-api/driver-model/ |
| D | binding.rst | 16 type in the system. When device_register is called for a device, it is
18 list of all drivers of that bus type. When driver_register is called
38 and the driver's probe callback is called. This gives the driver a
48 devclass_add_device is called to enumerate the device within the class
92 go to 0. When it does, the remove callback of the driver is called. It
97 iterated over, and the driver's remove callback is called for each
|
| /Documentation/arch/s390/ |
| D | driver-model.rst | 8 All devices which can be addressed by means of ccws are called 'CCW devices' -
132 This function is called by the device layer for each device the driver
147 This function is called by the device layer upon removal of the driver,
160 This function is called by the common I/O layer when the device is
174 set_offline: This function is called by the common I/O layer when the device is
189 This function is called by the common I/O layer for some state changes
224 before the driver is called, and is deregistered during set_offline() after the
225 driver has been called. Also, after registering / before deregistering, path
232 Parameters: dev - the device the handler is called for
239 The device driver is called from the common ccw_device layer and can retrieve
[all …]
|
| /Documentation/locking/ |
| D | hwspinlock.rst | 24 remote M3 and/or C64x+ slave processors (by an IPC subsystem called Syslink).
50 Should be called from a process context (might sleep).
61 Should be called from a process context (might sleep).
76 Should be called from a process context (might sleep).
86 Should be called from a process context (might sleep).
97 Should be called from a process context (might sleep).
173 This function shall be called only from an atomic context and the timeout
253 This function shall be called only from an atomic context.
263 Unlock a previously-locked hwspinlock. Always succeed, and can be called
373 * assign a specific hwspinlock id - this should be called early
[all …]
|
| /Documentation/mm/ |
| D | hugetlbfs_reserv.rst | 150 reservations is known. The routine hugetlb_acct_memory() is called to check
195 The helper routine vma_needs_reservation() is called to determine if a
207 is called. This routine takes two arguments related to reservations:
239 The routine vma_commit_reservation() is then called to adjust the reserve
250 be possible if hugetlb_reserve_pages was called for the same page in a shared
275 to the folio as it is called from the generic MM code. When a huge page
311 hugetlb_acct_memory(min_hpages) is called to reserve the specified number of
314 The routines hugepage_subpool_get/put_pages() are called when pages are
372 reservation map. Typically, these routines are not called directly. Rather,
373 a reservation map helper routine is called which calls one of these low level
[all …]
|
| /Documentation/devicetree/bindings/arm/ |
| D | arm,integrator.yaml | 15 so the system is modular and can host a variety of CPU tiles called
28 pre-packaged in a PC Tower form factor called Integrator/PP1 or a
29 special metal fixture called Integrator/PP2, see ARM DUI 0169A.
|
| /Documentation/security/tpm/ |
| D | tpm_tis.rst | 12 drivers. Originally Linux had only a driver called tpm_tis, which covered
16 For historical reasons above the original MMIO driver is called tpm_tis and the
25 communication endpoints are called localities in the TCG terminology.
|
| D | tpm_event_log.rst | 40 The firmware provides so called final events configuration table to sort
42 EFI_TCG2_PROTOCOL.GetEventLog() gets called.
44 This introduces another problem: nothing guarantees that it is not called
|
| /Documentation/devicetree/bindings/rtc/ |
| D | rtc-cmos.txt | 11 called "Register B".
13 called "Register A".
|
| /Documentation/livepatch/ |
| D | cumulative-patches.rst | 13 An elegant solution comes with the feature called "Atomic Replace". It allows
14 creation of so called "Cumulative Patches". They include all wanted changes
93 enabled patches were called.
102 callback. It is called only when the livepatch is properly disabled.
|
| /Documentation/driver-api/dmaengine/ |
| D | provider.rst | 36 parameter called the transfer width.
42 using a parameter called the burst size, that defines how many single
49 non-contiguous buffers to a contiguous buffer, which is called
79 These were just the general memory-to-memory (also called mem2mem) or
151 Our ``dma_device structure`` has a field called cap_mask that holds the
211 called on a regular basis through the DMA controller interrupt
355 It is called by the clients after it have placed the metadata to the buffer
360 descriptor is not freed up prior the callback is called.
377 - These functions will be called whenever a driver will call
395 - These functions can be called from an interrupt context
[all …]
|
12345678910>>...36