Home
last modified time | relevance | path

Searched refs:calling (Results 1 – 25 of 312) sorted by relevance

12345678910>>...13

/Linux-v4.19/Documentation/power/regulator/
Dregulator.txt11 Drivers can register a regulator by calling :-
19 Regulators can be unregistered by calling :-
27 consumer drivers by calling :-
Dconsumer.txt11 A consumer driver can get access to its supply regulator by calling :-
37 A consumer can enable its power supply by calling:-
45 A consumer can determine if a regulator is enabled by calling :-
52 A consumer can disable its supply when no longer needed by calling :-
75 Consumers can control their supply voltage by calling :-
87 The regulators configured voltage output can be found by calling :-
105 Consumers can control their supply current limit by calling :-
117 A regulators current limit can be found by calling :-
138 by calling :-
158 calling :-
[all …]
/Linux-v4.19/Documentation/powerpc/
Dsyscall64-abi.txt8 syscall calling sequence[*] matches the Power Architecture 64-bit ELF ABI
9 specification C function calling sequence, including register preservation
13 different calling sequences (e.g., rt_sigreturn).
33 Register preservation rules match the ELF ABI calling sequence with the
80 vsyscall calling sequence matches the syscall calling sequence, with the
81 following differences. Some vsyscalls may have different calling sequences.
/Linux-v4.19/Documentation/media/kapi/
Dmc-core.rst43 Drivers register media device instances by calling
45 and unregistered by calling :c:func:`media_device_unregister()`.
56 Drivers initialize entity pads by calling
59 Drivers register entities with a media device by calling
61 and unregistred by calling
73 Drivers initialize and create device node interfaces by calling
75 and remove them by calling:
115 Drivers create pad to pad links by calling:
123 Drivers create interface to entity links by calling:
164 Drivers initiate a graph traversal by calling
[all …]
Dv4l2-device.rst8 You must register the device instance by calling:
26 If you set it up before calling :c:func:`v4l2_device_register` then it will
28 :c:type:`v4l2_dev <v4l2_device>`\ ->name before calling
47 V4L2 devices are unregistered by calling:
126 decrease the refcount manually as well by calling:
/Linux-v4.19/Documentation/media/uapi/cec/
Dcec-ioc-adap-g-caps.rst76 - Userspace has to configure the physical address by calling
85 - Userspace has to configure the logical addresses by calling
93 - Userspace can transmit CEC messages by calling
103 - Userspace can use the passthrough mode by calling
/Linux-v4.19/Documentation/ABI/testing/
Ddell-smbios-wmi13 first determine the minimum size of the calling interface
22 2) After you've determined the minimum size of the calling
/Linux-v4.19/Documentation/pcmcia/
Ddriver-changes.txt31 are reserved, after calling pcmcia_request_configuration(), they may
45 - calling request_irq/free_irq directly. Use the IRQ from *p_dev->irq.
63 By calling pcmcia_loop_config(), a driver can iterate over all available
69 Instead of calling pcmcia_release_{configuration,io,irq,win}, all that's
70 necessary now is calling pcmcia_disable_device. As there is no valid
/Linux-v4.19/Documentation/core-api/
Dgfp_mask-from-fs-io.rst13 memory reclaim calling back into the FS or IO paths and blocking on
19 the gfp mask when calling an allocator. GFP_NOFS respectively GFP_NOIO can be
58 to fix up. That means that calling ``vmalloc`` with GFP_NOFS/GFP_NOIO is
Didr.rst28 the pointer you associated with the ID by calling :c:func:`idr_find`
29 and free the ID by calling :c:func:`idr_remove`.
/Linux-v4.19/Documentation/bpf/
Dbpf_design_QA.rst26 BPF is generic instruction set *with* C calling convention.
29 Q: Why C calling convention was chosen?
36 defines calling convention that is compatible with C calling
45 A: NO. BPF calling convention only allows registers R1-R5 to be used
62 Q: Does C-calling convention diminishes possible use cases?
/Linux-v4.19/Documentation/isdn/
DREADME.avmb155 and add the card by calling
57 and load the firmware by calling
61 and add the card by calling
63 and load the firmware by calling
DINTERFACE.CAPI26 CAPI drivers optionally register themselves with Kernel CAPI by calling the
30 registration can be revoked by calling the function unregister_capi_driver()
34 CAPI by calling the Kernel CAPI function attach_capi_ctr() with a pointer to a
38 driver. The registration can be revoked by calling the function
43 structure of the device, and signal its readiness by calling capi_ctr_ready().
55 operation CAPI_REGISTER) to an appropriate hardware driver by calling its
79 the following non-private fields, all to be set by the driver before calling
99 - to be set by the driver before calling attach_capi_ctr():
165 - to be filled in before calling capi_ctr_ready():
DREADME.diversion34 Tracing calling and diversion information
36 4. Tracing calling and diversion information
92 Tracing calling and diversion information
110 4. Tracing calling and diversion information
/Linux-v4.19/arch/arm/kernel/
Dentry-header.S331 load_user_sp_lr r2, r3, \offset + S_SP @ calling sp, lr
332 ldr r1, [sp, #\offset + S_PSR] @ get calling cpsr
343 ldmdb sp, {r1 - r12} @ get calling r1 - r12
345 ldmdb sp, {r0 - r12} @ get calling r0 - r12
/Linux-v4.19/net/x25/
Daf_x25.c126 char *called, *calling; in x25_addr_ntoa() local
133 calling = calling_addr->x25_addr; in x25_addr_ntoa()
146 *calling++ = ((*p >> 0) & 0x0F) + '0'; in x25_addr_ntoa()
149 *calling++ = ((*p >> 4) & 0x0F) + '0'; in x25_addr_ntoa()
154 *called = *calling = '\0'; in x25_addr_ntoa()
163 char *called, *calling; in x25_addr_aton() local
167 calling = calling_addr->x25_addr; in x25_addr_aton()
170 calling_len = strlen(calling); in x25_addr_aton()
185 *p |= (*calling++ - '0') << 0; in x25_addr_aton()
189 *p |= (*calling++ - '0') << 4; in x25_addr_aton()
/Linux-v4.19/security/tomoyo/
DKconfig42 bool "Activate without calling userspace policy loader."
68 string "Trigger for calling userspace policy loader"
/Linux-v4.19/Documentation/security/keys/
Drequest-key.rst9 The process starts by either the kernel requesting a service by calling
182 a) If extant, the calling process's thread keyring is searched.
184 b) If extant, the calling process's process keyring is searched.
186 c) The calling process's session keyring is searched.
/Linux-v4.19/Documentation/arm64/
Dsve.txt147 Sets the vector length of the calling thread and related flags, where
148 arg == vl | flags. Other threads of the calling process are unaffected.
185 * Either the calling thread's vector length or the deferred vector length
192 * Any previously outstanding deferred vector length change in the calling
199 vector length that will be applied at the next execve() by the calling
205 vector length, or calling PR_SVE_SET_VL with the PR_SVE_SET_VL_ONEXEC
211 Gets the vector length of the calling thread.
362 calling thread, or
/Linux-v4.19/Documentation/PCI/
Dpci.txt230 decrement the reference count on these devices by calling pci_dev_put().
258 the PCI device by calling pci_enable_device(). This will:
267 pci_request_resources() before calling pci_enable_device().
304 calling pci_disable_device().
308 determine MMIO and IO Port resource availability _after_ calling
329 to "register" this capability by calling pci_set_dma_mask() with
338 address by calling pci_set_consistent_dma_mask().
362 While calling request_irq() is the last step described here,
385 MSI capability can be enabled by calling pci_alloc_irq_vectors() with the
386 PCI_IRQ_MSI and/or PCI_IRQ_MSIX flags before calling request_irq(). This
[all …]
/Linux-v4.19/Documentation/devicetree/bindings/arm/firmware/
Dlinaro,optee-tz.txt14 - method : The method of calling the OP-TEE Trusted OS. Permitted
/Linux-v4.19/arch/unicore32/kernel/
Dentry.S71 ldw r1, [sp+], #\offset + S_PSR @ get calling asr
76 ldm.w (r1 - r15), [sp]+ @ get calling r1 - r15
77 ldur (r16 - lr), [sp]+ @ get calling r16 - lr
79 ldm.w (r0 - r15), [sp]+ @ get calling r0 - r15
80 ldur (r16 - lr), [sp]+ @ get calling r16 - lr
599 stw lr, [sp+], #S_PC @ Save calling PC
/Linux-v4.19/Documentation/media/uapi/v4l/
Dvidioc-streamon.rst59 the same state as after calling
67 calling :ref:`VIDIOC_REQBUFS` and can be restarted
/Linux-v4.19/Documentation/sound/soc/
Djack.rst36 Jacks are created by the machine driver calling snd_soc_jack_new().
53 input to the system and update a jack by calling snd_soc_jack_report(),
/Linux-v4.19/drivers/net/wireless/st/cw1200/
DKconfig19 the default platform data by calling cw1200_sdio_set_platform_data()

12345678910>>...13