| /Linux-v5.4/Documentation/power/regulator/ |
| D | regulator.rst | 12 Drivers can register a regulator by calling::
20 Regulators can be unregistered by calling::
29 consumer drivers by calling::
|
| D | consumer.rst | 12 A consumer driver can get access to its supply regulator by calling ::
39 A consumer can enable its power supply by calling::
48 A consumer can determine if a regulator is enabled by calling::
55 A consumer can disable its supply when no longer needed by calling::
80 Consumers can control their supply voltage by calling::
92 The regulators configured voltage output can be found by calling::
111 Consumers can control their supply current limit by calling::
124 A regulators current limit can be found by calling::
146 by calling::
167 calling::
[all …]
|
| /Linux-v5.4/Documentation/powerpc/ |
| D | syscall64-abi.rst | 8 syscall calling sequence\ [1]_ 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
82 vsyscall calling sequence matches the syscall calling sequence, with the
83 following differences. Some vsyscalls may have different calling sequences.
|
| /Linux-v5.4/Documentation/media/kapi/ |
| D | mc-core.rst | 45 Drivers register media device instances by calling
47 and unregistered by calling :c:func:`media_device_unregister()`.
58 Drivers initialize entity pads by calling
61 Drivers register entities with a media device by calling
63 and unregistered by calling
75 Drivers initialize and create device node interfaces by calling
77 and remove them by calling:
117 Drivers create pad to pad links by calling:
125 Drivers create interface to entity links by calling:
166 Drivers initiate a graph traversal by calling
[all …]
|
| D | v4l2-device.rst | 10 You must register the device instance by calling:
28 If you set it up before calling :c:func:`v4l2_device_register` then it will
30 :c:type:`v4l2_dev <v4l2_device>`\ ->name before calling
49 V4L2 devices are unregistered by calling:
128 decrease the refcount manually as well by calling:
|
| /Linux-v5.4/Documentation/media/uapi/cec/ |
| D | cec-ioc-adap-g-caps.rst | 83 - Userspace has to configure the physical address by calling
92 - Userspace has to configure the logical addresses by calling
100 - Userspace can transmit CEC messages by calling
110 - Userspace can use the passthrough mode by calling
|
| /Linux-v5.4/Documentation/pcmcia/ |
| D | driver-changes.rst | 37 are reserved, after calling pcmcia_request_configuration(), they may
52 - calling request_irq/free_irq directly. Use the IRQ from `*p_dev->irq`.
70 By calling pcmcia_loop_config(), a driver can iterate over all available
76 Instead of calling pcmcia_release_{configuration,io,irq,win}, all that's
77 necessary now is calling pcmcia_disable_device. As there is no valid
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | dell-smbios-wmi | 13 first determine the minimum size of the calling interface
22 2) After you've determined the minimum size of the calling
|
| /Linux-v5.4/Documentation/core-api/ |
| D | gfp_mask-from-fs-io.rst | 15 memory reclaim calling back into the FS or IO paths and blocking on
21 the gfp mask when calling an allocator. GFP_NOFS respectively GFP_NOIO can be
60 to fix up. That means that calling ``vmalloc`` with GFP_NOFS/GFP_NOIO is
|
| D | xarray.rst | 41 a value entry by calling xa_is_value(), and convert it back to
42 an integer by calling xa_to_value().
75 use xa_erase() instead of calling xa_store() with a
93 calling xa_clear_mark(). You can ask whether any entry in the
94 XArray has a particular mark set by calling xa_marked().
96 You can copy entries out of the XArray into a plain array by calling
98 the XArray by calling xa_for_each(). You may prefer to use
122 Finally, you can remove all entries from an XArray by calling
223 before calling xa_load(), then take a reference count on the
224 object you have found before calling xa_unlock(). This will
[all …]
|
| D | idr.rst | 28 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-v5.4/Documentation/isdn/ |
| D | avmb1.rst | 63 and add the card by calling::
67 and load the firmware by calling::
72 and add the card by calling::
76 and load the firmware by calling::
|
| D | interface_capi.rst | 29 CAPI drivers optionally register themselves with Kernel CAPI by calling the
33 registration can be revoked by calling the function unregister_capi_driver()
37 CAPI by calling the Kernel CAPI function attach_capi_ctr() with a pointer to a
41 driver. The registration can be revoked by calling the function
46 structure of the device, and signal its readiness by calling capi_ctr_ready().
59 operation CAPI_REGISTER) to an appropriate hardware driver by calling its
85 the following non-private fields, all to be set by the driver before calling
106 to be set by the driver before calling attach_capi_ctr():
191 to be filled in before calling capi_ctr_ready():
|
| /Linux-v5.4/arch/arm/kernel/ |
| D | entry-header.S | 332 load_user_sp_lr r2, r3, \offset + S_SP @ calling sp, lr
333 ldr r1, [sp, #\offset + S_PSR] @ get calling cpsr
344 ldmdb sp, {r1 - r12} @ get calling r1 - r12
346 ldmdb sp, {r0 - r12} @ get calling r0 - r12
|
| /Linux-v5.4/net/x25/ |
| D | af_x25.c | 121 char *called, *calling; in x25_addr_ntoa() local
128 calling = calling_addr->x25_addr; in x25_addr_ntoa()
141 *calling++ = ((*p >> 0) & 0x0F) + '0'; in x25_addr_ntoa()
144 *calling++ = ((*p >> 4) & 0x0F) + '0'; in x25_addr_ntoa()
149 *called = *calling = '\0'; in x25_addr_ntoa()
158 char *called, *calling; in x25_addr_aton() local
162 calling = calling_addr->x25_addr; in x25_addr_aton()
165 calling_len = strlen(calling); in x25_addr_aton()
180 *p |= (*calling++ - '0') << 0; in x25_addr_aton()
184 *p |= (*calling++ - '0') << 4; in x25_addr_aton()
|
| /Linux-v5.4/Documentation/bpf/ |
| D | bpf_design_QA.rst | 26 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-v5.4/Documentation/PCI/ |
| D | pci.rst | 172 decrement the reference count on these devices by calling pci_dev_put().
199 the PCI device by calling pci_enable_device(). This will:
211 pci_request_resources() before calling pci_enable_device().
248 calling pci_disable_device().
253 determine MMIO and IO Port resource availability _after_ calling
275 to "register" this capability by calling pci_set_dma_mask() with
284 address by calling pci_set_consistent_dma_mask().
308 While calling request_irq() is the last step described here,
331 MSI capability can be enabled by calling pci_alloc_irq_vectors() with the
332 PCI_IRQ_MSI and/or PCI_IRQ_MSIX flags before calling request_irq(). This
[all …]
|
| /Linux-v5.4/Documentation/media/uapi/mediactl/ |
| D | media-ioc-request-alloc.rst | 70 In addition, the request can be queued by calling
71 :ref:`MEDIA_REQUEST_IOC_QUEUE` and re-initialized by calling
|
| /Linux-v5.4/Documentation/devicetree/bindings/arm/firmware/ |
| D | linaro,optee-tz.txt | 14 - method : The method of calling the OP-TEE Trusted OS. Permitted
|
| /Linux-v5.4/Documentation/devicetree/bindings/firmware/xilinx/ |
| D | xlnx,zynqmp-firmware.txt | 15 - method: The method of calling the PM-API firmware layer.
|
| /Linux-v5.4/security/tomoyo/ |
| D | Kconfig | 43 bool "Activate without calling userspace policy loader."
69 string "Trigger for calling userspace policy loader"
|
| /Linux-v5.4/arch/unicore32/kernel/ |
| D | entry.S | 68 ldw r1, [sp+], #\offset + S_PSR @ get calling asr
73 ldm.w (r1 - r15), [sp]+ @ get calling r1 - r15
74 ldur (r16 - lr), [sp]+ @ get calling r16 - lr
76 ldm.w (r0 - r15), [sp]+ @ get calling r0 - r15
77 ldur (r16 - lr), [sp]+ @ get calling r16 - lr
596 stw lr, [sp+], #S_PC @ Save calling PC
|
| /Linux-v5.4/Documentation/sound/soc/ |
| D | jack.rst | 36 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-v5.4/Documentation/security/keys/ |
| D | request-key.rst | 9 The process starts by either the kernel requesting a service by calling
188 a) If extant, the calling process's thread keyring is searched.
190 b) If extant, the calling process's process keyring is searched.
192 c) The calling process's session keyring is searched.
|
| /Linux-v5.4/drivers/net/wireless/st/cw1200/ |
| D | Kconfig | 20 the default platform data by calling cw1200_sdio_set_platform_data()
|
