Home
last modified time | relevance | path

Searched full:obtained (Results 1 – 25 of 1503) sorted by relevance

12345678910>>...61

/kernel/liteos_a/kernel/include/
Dlos_cpup.h146 * obtained.</li>
150 …* obtained, and the parameter value 1 indicates that the CPU usage i…
151 …* be obtained. Other values indicate that the CPU usage in all time …
171 * the CPU usage fails to be obtained.</li>
173 * the CPU usage fails to be obtained.</li>
178 …* obtained, and the parameter value 1 indicates that the CPU usage in…
179 …* be obtained. Other values indicate that the CPU usage in the period…
180 * 1s will be obtained.
201 * the CPU usage fails to be obtained.</li>
203 * the CPU usage fails to be obtained.</li>
[all …]
Dlos_sys.h147 * @retval UINT32 Number of cycles obtained in one second.
162 * <li>The number of milliseconds obtained through the conversion is 32-bit.</li>
167 …* @retval UINT32 Number of milliseconds obtained through the conversion. Ticks are successfully co…
189 * @retval UINT32 Number of Ticks obtained through the conversion.
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/memory-controllers/ddr/
Djedec,lpddr2.yaml37 Revision 1 value of SDRAM chip. Obtained from device datasheet.
45 Revision 2 value of SDRAM chip. Obtained from device datasheet.
54 Obtained from device datasheet.
61 Obtained from device datasheet.
68 cycles. Obtained from device datasheet.
75 cycles. Obtained from device datasheet.
82 of clock cycles. Obtained from device datasheet.
89 Obtained from device datasheet.
95 RAS-to-CAS delay in terms of number of clock cycles. Obtained from
102 WRITE recovery time in terms of number of clock cycles. Obtained from
[all …]
/kernel/liteos_m/components/cpup/
Dlos_cpup.h254 * to be obtained.</li>
258 …* obtained, and the parameter value 1 indicates that the CPU usage in the former 1s will be obtain…
259 * indicate that the CPU usage in the period that is less than 1s will be obtained.
278 * to be obtained.</li>
280 * the CPU usage fails to be obtained.</li>
304 * the CPU usage fails to be obtained.</li>
306 * the CPU usage fails to be obtained.</li>
311 …* will be obtained, and the parameter value 1 indicates that the CPU usage in the former 1s will b…
312 * Other values indicate that the CPU usage in the period that is less than 1s will be obtained.
333 * to be obtained.</li>
[all …]
/kernel/linux/linux-5.10/Documentation/admin-guide/cgroup-v1/
Dcpuacct.rst19 /sys/fs/cgroup/cpuacct.usage gives the CPU time (in nanoseconds) obtained
20 by this group which is essentially the CPU time obtained by all the tasks
31 can be obtained from g1/cpuacct.usage and the same is accumulated in
35 CPU time obtained by the cgroup into user and system times. Currently
/kernel/linux/linux-6.6/Documentation/admin-guide/cgroup-v1/
Dcpuacct.rst19 /sys/fs/cgroup/cpuacct.usage gives the CPU time (in nanoseconds) obtained
20 by this group which is essentially the CPU time obtained by all the tasks
31 can be obtained from g1/cpuacct.usage and the same is accumulated in
35 CPU time obtained by the cgroup into user and system times. Currently
/kernel/linux/linux-5.10/drivers/net/ethernet/qlogic/qed/
Dqed_ll2.h139 * @param connection_handle LL2 connection's handle obtained from
150 * @param connection_handle LL2 connection's handle obtained from
184 * @param connection_handle LL2 connection's handle obtained from
196 * obtained from
213 * obtained from
225 * @param connection_handle LL2 connection's handle obtained from
/kernel/linux/linux-6.6/include/linux/
Dcgroup_refcnt.h39 * count was successfully obtained; %false otherwise. in CGROUP_REF_EXPORT()
57 * function. Returns %true if a reference count was successfully obtained; in CGROUP_REF_EXPORT()
73 * Put a reference obtained via css_get() and css_tryget_online(). in CGROUP_REF_EXPORT()
88 * Put references obtained via css_get() and css_tryget_online(). in CGROUP_REF_EXPORT()
/kernel/linux/linux-6.6/drivers/net/ethernet/qlogic/qed/
Dqed_ll2.h137 * @connection_handle: LL2 connection's handle obtained from
148 * @connection_handle: LL2 connection's handle obtained from
183 * @connection_handle: LL2 connection's handle obtained from
196 * @connection_handle: LL2 connection's handle obtained from
211 * @connection_handle: LL2 connection's handle obtained from
222 * @connection_handle: LL2 connection's handle obtained from
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/serial/
Dsnps-dw-apb-uart.yaml74 always be reported as active instead of being obtained from the modem
81 always be reported as active instead of being obtained from the modem
88 always be reported as active instead of being obtained from the modem
95 be reported as inactive instead of being obtained from the modem status
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/serial/
Dsnps-dw-apb-uart.yaml92 always be reported as active instead of being obtained from the modem
99 always be reported as active instead of being obtained from the modem
106 always be reported as active instead of being obtained from the modem
113 be reported as inactive instead of being obtained from the modem status
/kernel/linux/linux-5.10/arch/x86/lib/
Dinsn-eval.c273 * selector needs to be obtained using get_segment_selector() and passing the
332 * registers. In CONFIG_X86_32, the segment is obtained from either pt_regs or
333 * kernel_vm86_regs as applicable. In CONFIG_X86_64, CS and SS are obtained
334 * from pt_regs. DS, ES, FS and GS are obtained by reading the actual CPU
652 * pointed by the segment selector. The segment selector is obtained from the
719 * pointed by the segment selector. The segment selector is obtained from the
766 * Obtain address and operand sizes of the code segment. It is obtained from the
833 * register is obtained as an offset from the base of pt_regs. In specific
850 * register is obtained as an offset from the base of pt_regs.
862 * @base: Obtained segment base
[all …]
/kernel/linux/linux-6.6/Documentation/userspace-api/media/v4l/
Dmetafmt-rkisp1.rst18 ``rkisp1-config.h``. So the structure can be obtained from the buffer by:
30 Those statistics are obtained from the :ref:`rkisp1_stats <rkisp1_stats>`
34 ``rkisp1-config.h``. So the structure can be obtained from the buffer by:
/kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/
Dpixfmt-meta-rkisp1.rst17 ``rkisp1-config.h``. So the structure can be obtained from the buffer by:
29 Those statistics are obtained from the :ref:`rkisp1_stats <rkisp1_stats>`
33 ``rkisp1-config.h``. So the structure can be obtained from the buffer by:
/kernel/linux/linux-6.6/arch/x86/lib/
Dinsn-eval.c271 * selector needs to be obtained using get_segment_selector() and passing the
330 * registers. In CONFIG_X86_32, the segment is obtained from either pt_regs or
331 * kernel_vm86_regs as applicable. In CONFIG_X86_64, CS and SS are obtained
332 * from pt_regs. DS, ES, FS and GS are obtained by reading the actual CPU
670 * pointed by the segment selector. The segment selector is obtained from the
737 * pointed by the segment selector. The segment selector is obtained from the
784 * Obtain address and operand sizes of the code segment. It is obtained from the
851 * register is obtained as an offset from the base of pt_regs. In specific
868 * register is obtained as an offset from the base of pt_regs.
883 * The register is obtained as a pointer within pt_regs.
[all …]
/kernel/linux/linux-6.6/fs/ntfs/
Daops.h24 * Unpin, unmap and release a page that was obtained from ntfs_map_page().
56 * The above means that page_address(page) can be used on all pages obtained
70 * obtained using PTR_ERR() on the return value of ntfs_map_page().
/kernel/linux/linux-5.10/fs/ntfs/
Daops.h24 * Unpin, unmap and release a page that was obtained from ntfs_map_page().
56 * The above means that page_address(page) can be used on all pages obtained
70 * obtained using PTR_ERR() on the return value of ntfs_map_page().
/kernel/linux/linux-5.10/Documentation/ABI/stable/
Dsysfs-bus-mhi5 Description: The file holds the serial number of the client device obtained
17 obtained using a BHI (Boot Host Interface) register read after
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/cpu/
Dcpu-capacity.txt25 CPU capacities are obtained by running a suitable benchmark. This binding makes
36 CPU capacities are obtained by running the Dhrystone benchmark on each CPU at
37 max frequency (with caches enabled). The obtained DMIPS score is then divided
39 DMIPS/MHz are obtained. Such values are then normalized w.r.t. the highest
40 score obtained in the system.
/kernel/linux/linux-5.10/include/linux/
Dptp_clock_kernel.h204 * @ptp: The clock obtained from ptp_clock_register().
214 * @ptp: The clock obtained from ptp_clock_register().
236 * @ptp: The clock obtained from ptp_clock_register().
262 * @ptp: The clock obtained from ptp_clock_register().
272 * @ptp: The clock obtained from ptp_clock_register().
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/
Dcpu-capacity.txt25 CPU capacities are obtained by running a suitable benchmark. This binding makes
36 CPU capacities are obtained by running the Dhrystone benchmark on each CPU at
37 max frequency (with caches enabled). The obtained DMIPS score is then divided
39 DMIPS/MHz are obtained. Such values are then normalized w.r.t. the highest
40 score obtained in the system.
/kernel/linux/linux-6.6/Documentation/ABI/stable/
Dsysfs-bus-mhi5 Description: The file holds the serial number of the client device obtained
17 obtained using a BHI (Boot Host Interface) register read after
/kernel/linux/linux-5.10/Documentation/filesystems/
Dautofs-mount-control.rst274 the autofs mount. The device number can be obtained from the mount options
276 autofs_dev_ioct with the ioctlfd field set to the descriptor obtained
288 with the ioctlfd field set to the descriptor obtained from the open
306 ioctlfd field set to the descriptor obtained from the open call and
321 ioctlfd field set to the descriptor obtained from the open call.
330 ioctlfd field set to the descriptor obtained from the open call.
358 ioctlfd field set to the descriptor obtained from the open call. In
376 ioctlfd field set to the descriptor obtained from the open call and
/kernel/linux/linux-6.6/Documentation/filesystems/
Dautofs-mount-control.rst274 the autofs mount. The device number can be obtained from the mount options
276 autofs_dev_ioct with the ioctlfd field set to the descriptor obtained
288 with the ioctlfd field set to the descriptor obtained from the open
306 ioctlfd field set to the descriptor obtained from the open call and
321 ioctlfd field set to the descriptor obtained from the open call.
330 ioctlfd field set to the descriptor obtained from the open call.
358 ioctlfd field set to the descriptor obtained from the open call. In
376 ioctlfd field set to the descriptor obtained from the open call and
/kernel/linux/linux-5.10/Documentation/ABI/testing/
Dsysfs-platform-dptf80 (RO) The high frequency impedance value that can be obtained from battery
88 (RO) The no-load voltage that can be obtained from battery fuel gauge in
96 (RO) The battery discharge current capability obtained from battery fuel gauge in

12345678910>>...61