Home
last modified time | relevance | path

Searched full:described (Results 1 – 25 of 4373) sorted by relevance

12345678910>>...175

/OK3568_Linux_fs/kernel/Documentation/arm64/
H A Delf_hwcaps.rst30 Where software relies on a feature described by a hwcap, it should check
44 which are described by architected ID registers inaccessible to
49 Such hwcaps are described below in the form::
60 described by ID registers alone. These may be described without
103 described by Documentation/arm64/cpu-feature-registers.rst.
163 ID_AA64ISAR1_EL1.API == 0b0001, as described by
168 ID_AA64ISAR1_EL1.GPI == 0b0001, as described by
245 Functionality implied by ID_AA64PFR1_EL1.MTE == 0b0010, as described
H A Dbooting.rst148 Any memory described to the kernel (even that below the start of the
273 The requirements described above for CPU mode, caches, MMUs, architected
283 enable-methods are described below.
304 the kernel (i.e. outside of the regions of memory described to the
305 kernel in the memory node, or in a reserved area of memory described
307 kernel will issue CPU_ON calls as described in ARM document number ARM
311 The device tree should contain a 'psci' node, as described in
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/regulator/
H A Dqcom,spmi-regulator.txt44 described in the data sheet.
59 described in the data sheet.
77 described in the data sheet.
97 described in the data sheet
128 described in the data sheet.
137 described in the data sheet.
152 described in the data sheet.
166 described in the data sheet.
183 described in the data sheet.
222 see regulator.txt - with additional custom properties described below:
/OK3568_Linux_fs/kernel/Documentation/userspace-api/media/v4l/
H A Dvidioc-g-ext-ctrls.rst328 - The class containing user controls. These controls are described
336 described in :ref:`mpeg-controls`.
339 - The class containing camera controls. These controls are described
344 controls are described in :ref:`fm-tx-controls`.
348 described in :ref:`flash-controls`.
352 described in :ref:`jpeg-controls`.
356 described in :ref:`image-source-controls`.
360 described in :ref:`image-process-controls`.
364 are described in :ref:`fm-rx-controls`.
368 described in :ref:`rf-tuner-controls`.
[all …]
/OK3568_Linux_fs/kernel/fs/ntfs/
H A Dbitmap.h28 * Set @count bits starting at bit @start_bit in the bitmap described by the
46 * Set @count bits starting at bit @start_bit in the bitmap described by the
63 * Clear @count bits starting at bit @start_bit in the bitmap described by the
79 * Set bit @bit in the bitmap described by the vfs inode @vi.
93 * Clear bit @bit in the bitmap described by the vfs inode @vi.
H A Dindex.h22 * @idx_ni: index inode containing the @entry described by this context
35 * @entry is the index entry described by this context. @data and @data_len
39 * If @is_in_root is 'true', @entry is in the index root attribute @ir described
109 * Mark the index entry described by the index entry context @ictx dirty.
/OK3568_Linux_fs/kernel/drivers/mfd/
H A Datmel-smc.c35 * This function encodes the @ncycles value as described in the datasheet
86 * This function encodes the @ncycles value as described in the datasheet
107 * The formula described in atmel datasheets (section "HSMC Timings in atmel_smc_cs_conf_set_timing()
128 * This function encodes the @ncycles value as described in the datasheet
146 * The formula described in atmel datasheets (section "SMC Setup in atmel_smc_cs_conf_set_setup()
167 * This function encodes the @ncycles value as described in the datasheet
185 * The formula described in atmel datasheets (section "SMC Pulse in atmel_smc_cs_conf_set_pulse()
206 * This function encodes the @ncycles value as described in the datasheet
223 * The formula described in atmel datasheets (section "SMC Cycle in atmel_smc_cs_conf_set_cycle()
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/i3c/
H A Di3c.txt29 values of I2C devices described in the device tree to determine
35 Each I2C device connected to the bus should be described in a subnode. All
36 properties described in Documentation/devicetree/bindings/i2c/i2c.txt are
72 are thus discoverable. So, by default, I3C devices do not have to be described
75 and those resources may have to be described in the device tree, which in turn
134 * resources described in the DT.
/OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/arm-none-linux-gnueabihf/libc/usr/include/sys/
H A Duio.h34 buffers described by IOVEC, which is a vector of COUNT 'struct iovec's.
44 /* Write data pointed by the buffers described by IOVEC, which
60 described by IOVEC, which is a vector of COUNT 'struct iovec's.
70 /* Write data pointed by the buffers described by IOVEC, which is a
99 described by IOVEC, which is a vector of COUNT 'struct iovec's.
109 /* Write data pointed by the buffers described by IOVEC, which is a
/OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/aarch64-none-linux-gnu/libc/usr/include/sys/
H A Duio.h34 buffers described by IOVEC, which is a vector of COUNT 'struct iovec's.
44 /* Write data pointed by the buffers described by IOVEC, which
60 described by IOVEC, which is a vector of COUNT 'struct iovec's.
70 /* Write data pointed by the buffers described by IOVEC, which is a
99 described by IOVEC, which is a vector of COUNT 'struct iovec's.
109 /* Write data pointed by the buffers described by IOVEC, which is a
/OK3568_Linux_fs/kernel/Documentation/userspace-api/media/rc/
H A Drc-protos.rst183 described here https://www.sbprojects.net/knowledge/ir/jvc.php.
279 described here https://www.sbprojects.net/knowledge/ir/nec.php. Note
354 This is the rc-6 in mode 0. rc-6 is described here
362 This is the rc-6 in mode 6a, 20 bits. rc-6 is described here
370 This is the rc-6 in mode 6a, 24 bits. rc-6 is described here
378 This is the rc-6 in mode 6a, 32 bits. rc-6 is described here
397 This is a protocol used by Sharp VCRs, is described here
431 The rc-mm protocol is described here
438 The rc-mm protocol is described here
445 The rc-mm protocol is described here
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/video/
H A Drockchip_hdmi.txt21 - rockchip,hdmi_audio_source: hdmi audio source that is described as follow
24 - rockchip,hdmi_video_source: hdmi video source that is described as follow
27 - rockchip,hdcp_enable: hdmi hdcp function is described as follow
30 - rockchip,cec_enable: hdmi cec function is described as follow
/OK3568_Linux_fs/yocto/poky/meta/files/common-licenses/
H A DOPL-1.020 … 1.8. "License" means this document and the corresponding addendum described in section 6.4 below.
28 …1.10. "Original Code" means Source Code of computer software code which is described in the Source…
52 …er, You may include an additional document offering the additional rights described in Section 3.5.
60 …you obtain such knowledge after You make Your Modification available as described in Section 3.2, …
64 …e Modification(s), You may add your name as a Contributor to the notice described in Exhibit A. If…
72 …e code they affect. Such description must be included in the LEGAL file described in Section 3.4 a…
84described in section 6.4, (which you may only do in order to apply it to code which is not already…
124 …y left blank. The contents of this section are found in the corresponding addendum described above.
132 Text for this Exhibit A is found in the corresponding addendum, described in section 6.4 above, tex…
136 Text for this Exhibit B is found in the corresponding addendum, described in section 6.4 above, tex…
/OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/aarch64-none-linux-gnu/libc/usr/include/drm/
H A Dvmwgfx_drm.h236 * @rep: Output data as described above.
237 * @req: Input data as described above.
264 * @rep: Output data as described above.
265 * @req: Input data as described above.
422 * @req: Input data as described above.
423 * @rep: Output data as described above.
907 * @drm_surface_flags Flags as described above.
956 * @req: Input argument as described above.
957 * @rep: Output argument as described above.
983 * @creq: The data used as input when the surface was created, as described
[all …]
/OK3568_Linux_fs/kernel/include/uapi/drm/
H A Dvmwgfx_drm.h241 * @rep: Output data as described above.
242 * @req: Input data as described above.
269 * @rep: Output data as described above.
270 * @req: Input data as described above.
427 * @req: Input data as described above.
428 * @rep: Output data as described above.
914 * @drm_surface_flags Flags as described above.
963 * @req: Input argument as described above.
964 * @rep: Output argument as described above.
990 * @creq: The data used as input when the surface was created, as described
[all …]
/OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/arm-none-linux-gnueabihf/libc/usr/include/drm/
H A Dvmwgfx_drm.h236 * @rep: Output data as described above.
237 * @req: Input data as described above.
264 * @rep: Output data as described above.
265 * @req: Input data as described above.
422 * @req: Input data as described above.
423 * @rep: Output data as described above.
907 * @drm_surface_flags Flags as described above.
956 * @req: Input argument as described above.
957 * @rep: Output argument as described above.
983 * @creq: The data used as input when the surface was created, as described
[all …]
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/display/armada/
H A Dmarvell,dove-lcd.txt7 - port: video output port with endpoints, as described by graph.txt
11 - clocks: as described by clock-bindings.txt
12 - clock-names: as described by clock-bindings.txt
/OK3568_Linux_fs/kernel/Documentation/admin-guide/pm/
H A Dsuspend-flows.rst93 deferred till the subsequent system resume transition as described
173 described `above <s2idle_suspend_>`_.
178 described `above <s2idle_suspend_>`_.
183 described `above <s2idle_suspend_>`_, but the arming of IRQs for system
260 described `above <s2idle_resume_>`_.
265 described `above <s2idle_resume_>`_.
270 described `above <s2idle_resume_>`_.
/OK3568_Linux_fs/kernel/Documentation/networking/
H A Dcdc_mbim.rst64 The driver <-> userspace interfaces are described below. The MBIM
65 control channel protocol is described in [1].
103 configuration descriptor kernel interfaces described in [6] or [7].
111 fragmentation and defragmentaion, as described in section 9.5 of [1].
181 described in section 10.5.1 of [1].
205 structure described in section 10.5.29 of [1].
271 As described above, MBIM IP session 0 is treated as special by the
300 Summarizing the cdc_mbim driver mapping described above, we have this
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/mmc/
H A Dhi3798cv200-dw-mshc.txt8 differences between the core Synopsys dw mshc controller properties described
17 "ciu" - The ciu clock described in synopsys-dw-mshc.txt.
18 "biu" - The biu clock described in synopsys-dw-mshc.txt.
/OK3568_Linux_fs/u-boot/doc/device-tree-bindings/net/
H A Dethernet.txt16 - phy-connection-type: the same as "phy-mode" property but described in ePAPR;
18 device; this property is described in ePAPR and so preferred;
25 They are described in the phy.txt file in this same directory.
/OK3568_Linux_fs/external/xserver/hw/xfree86/man/
H A Dxorg.conf.man17 described in the Xserver(@appmansuffix@) and
19 parameters, with their defaults, are described below. Driver and module
20 specific configuration parameters are described in the relevant driver
207 The input devices are described in the
220 The graphics boards are described in the
222 sections, and the monitors are described in the
471 In addition to options specific to this section (described below), the
700 keyword, as described here:
892 which are described here.
1366 which are described here.
[all …]
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/media/
H A Dvideo-mux.txt5 on the active input port is passed through to the output port. Muxes described
6 by this binding are controlled by a multiplexer controller that is described by
19 ports node as described in Documentation/devicetree/bindings/graph.txt.
/OK3568_Linux_fs/buildroot/package/tpm2-tss/
H A DConfig.in12 * System API (SAPI) as described in the system level API and
22 * TPM Command Transmission Interface (TCTI) that is described
45 API (FAPI) as described in the "TSS 2.0 Feature API
/OK3568_Linux_fs/kernel/Documentation/hwmon/
H A Dabituguru-datasheet.rst25 described here and not the CPU / RAM / etc voltage & frequency control.
103 First the uGuru must be in "ready" mode as described above, DATA should hold
116 First send the bank and sensor addresses as described above.
128 algorithm described above will still work.
135 First send the bank and sensor addresses as described above.
148 algorithm described above will still work.
220 Alarm behaviour for the selected sensor. A 1 enables the described
311 Alarm behaviour for the selected sensor. A 1 enables the described behaviour.

12345678910>>...175