Searched full:operate (Results 1 – 25 of 669) sorted by relevance
12345678910>>...27
| /linux-5.10/drivers/staging/media/atomisp/pci/runtime/queue/src/ |
| D | queue.c | 99 * operate on the queue in ia_css_queue_enqueue()
119 /* b. Operate on the queue */ in ia_css_queue_enqueue()
158 * operate on the queue in ia_css_queue_dequeue()
178 /* b. Operate on the queue */ in ia_css_queue_dequeue()
215 * operate on the queue in ia_css_queue_is_full()
229 /* b. Operate on the queue */ in ia_css_queue_is_full()
249 * operate on the queue in ia_css_queue_get_free_space()
263 /* b. Operate on the queue */ in ia_css_queue_get_free_space()
283 * operate on the queue in ia_css_queue_get_used_space()
297 /* b. Operate on the queue */ in ia_css_queue_get_used_space()
[all …]
|
| /linux-5.10/drivers/regulator/ |
| D | helpers.c | 21 * @rdev: regulator to operate on
53 * @rdev: regulator to operate on
79 * @rdev: regulator to operate on
122 * @rdev: regulator to operate on
165 * @rdev: regulator to operate on
229 * @rdev: regulator to operate on
254 * @rdev: regulator to operate on
283 * @rdev: Regulator to operate on
323 * @rdev: Regulator to operate on
354 * @rdev: Regulator to operate on
[all …]
|
| /linux-5.10/Documentation/mips/ |
| D | ingenic-tcu.rst | 29 operate.
35 - On the oldest SoCs (up to JZ4740), all of the eight channels operate in
37 - On JZ4725B, channel 5 operates as TCU2, the others operate as TCU1.
38 - On newest SoCs (JZ4750 and above), channels 1-2 operate as TCU2, the
39 others operate as TCU1.
|
| /linux-5.10/arch/mips/include/asm/octeon/ |
| D | cvmx-spi.h | 89 * can operate as a full duplex (both Tx and Rx data paths
107 * can operate as a full duplex (both Tx and Rx data paths
176 * can operate as a full duplex (both Tx and Rx data paths
192 * can operate as a full duplex (both Tx and Rx data paths
209 * can operate as a full duplex (both Tx and Rx data paths
226 * can operate as a full duplex (both Tx and Rx data paths
243 * can operate as a full duplex (both Tx and Rx data paths
260 * can operate as a full duplex (both Tx and Rx data paths
|
| /linux-5.10/drivers/clk/qcom/ |
| D | clk-regmap.c | 16 * @hw: clk to operate on
42 * @hw: clk to operate on
66 * @hw: clk to operate on
90 * @rclk: clk to operate on
|
| /linux-5.10/Documentation/devicetree/bindings/power/supply/ |
| D | qcom_smbb.txt | 51 Description: Battery voltage limit above which fast charging may operate;
53 will operate.
58 Description: Battery voltage limit below which fast charging may operate;
86 Description: Input voltage level above which charging may operate
|
| /linux-5.10/lib/ |
| D | lru_cache.c | 188 * @lc: the lru cache to operate on
442 * @lc: the lru cache to operate on
487 * @lc: the lru cache to operate on
507 * @lc: the lru cache to operate on
528 * @lc: the lru cache to operate on
552 * @lc: the lru cache to operate on
576 * @lc: the lru cache to operate on
589 * @lc: the lru cache to operate on
600 * @lc: the lru cache to operate on
631 * @lc: the lru cache to operate on
|
| /linux-5.10/arch/arm/mach-omap2/ |
| D | clkt2xxx_dpll.c | 22 * @clk: struct clk * of the DPLL to operate on
39 * @clk: struct clk * of the DPLL to operate on
|
| /linux-5.10/drivers/infiniband/core/ |
| D | rw.c | 296 * @qp: queue pair to operate on
302 * @rkey: remote key to operate on
362 * @qp: queue pair to operate on
370 * @rkey: remote key to operate on
492 * @ctx: context to operate on
493 * @qp: queue pair to operate on
550 * @ctx: context to operate on
551 * @qp: queue pair to operate on
575 * @qp: queue pair to operate on
611 * @qp: queue pair to operate on
|
| /linux-5.10/arch/mips/cavium-octeon/executive/ |
| D | cvmx-spi.c | 97 * can operate as a full duplex (both Tx and Rx data paths
143 * can operate as a full duplex (both Tx and Rx data paths
188 * can operate as a full duplex (both Tx and Rx data paths
303 * can operate as a full duplex (both Tx and Rx data paths
422 * can operate as a full duplex (both Tx and Rx data paths
439 * present for the SPI interface to operate. in cvmx_spi_clock_detect_cb()
500 * can operate as a full duplex (both Tx and Rx data paths
569 * can operate as a full duplex (both Tx and Rx data paths
626 * can operate as a full duplex (both Tx and Rx data paths
|
| /linux-5.10/include/linux/ |
| D | drbd_genl_api.h | 8 * For admin requests (user -> kernel): which minor device to operate on.
11 * If we do not operate on minors, but on connections or resources,
|
| /linux-5.10/Documentation/devicetree/bindings/serial/ |
| D | nxp,sc16is7xx.txt | 25 should operate in IrDA mode.
61 should operate in IrDA mode.
|
| /linux-5.10/include/crypto/ |
| D | ecdh.h | 20 * To use ECDH with KPP, the following functions should be used to operate on
62 * The ECDH implementations operate on a packet representation of the private
|
| D | dh.h | 17 * To use DH with KPP, the following functions should be used to operate on
65 * The DH implementations operate on a packet representation of the private
|
| /linux-5.10/drivers/usb/dwc2/ |
| D | Kconfig | 35 driver to operate in Host-only mode.
45 driver to operate in Peripheral-only mode. This option requires
|
| /linux-5.10/drivers/pci/ |
| D | irq.c | 16 * @dev: PCI device to operate on
58 * @dev: PCI device to operate on
|
| /linux-5.10/Documentation/scsi/ |
| D | bnx2fc.rst | 13 depend on the state of the network interfaces to operate. As such, the network
28 2. Configure the interfaces on which bnx2fc driver has to operate on.
|
| /linux-5.10/include/uapi/linux/ |
| D | fcntl.h | 49 * Set/Get write life time hints. {GET,SET}_RW_HINT operate on the
50 * underlying inode, while {GET,SET}_FILE_RW_HINT operate only on
|
| /linux-5.10/tools/include/uapi/linux/ |
| D | fcntl.h | 49 * Set/Get write life time hints. {GET,SET}_RW_HINT operate on the
50 * underlying inode, while {GET,SET}_FILE_RW_HINT operate only on
|
| /linux-5.10/Documentation/devicetree/bindings/phy/ |
| D | nvidia,tegra20-usb-phy.txt | 60 operate in legacy mode (as APX 2500 / 2600). In legacy mode some
69 otg means it can operate as either ("on the go")
|
| /linux-5.10/drivers/watchdog/ |
| D | bd70528_wdt.c | 35 * @data: device data for the PMIC instance we want to operate on
100 * @data: device data for the PMIC instance we want to operate on
117 * @data: device data for the PMIC instance we want to operate on
|
| /linux-5.10/Documentation/driver-api/media/drivers/ |
| D | pvrusb2.rst | 153 operate corresponding chips within the pvrusb2 device. It is
155 operate specific pieces (and those modules are in turn driven by
190 applications can open and operate the driver in the usual V4L
|
| /linux-5.10/Documentation/power/ |
| D | opp.rst | 70 As the system proceeds to operate, SoC framework may choose to make certain
77 operational functions operate only on available opps:
152 /* dont operate on the pointer.. just do a sanity check.. */
347 for the OPP library to operate on. Pointer to this structure is
|
| /linux-5.10/fs/ |
| D | anon_inodes.c | 69 * that do not need to have a full-fledged inode in order to operate correctly.
120 * that do not need to have a full-fledged inode in order to operate correctly.
|
| /linux-5.10/Documentation/driver-api/ |
| D | mailbox.rst | 43 The client might want to operate in blocking mode (synchronously
106 dc_sync->cl.tx_done = NULL; /* operate in blocking mode */
|
12345678910>>...27