| /openbmc/linux/Documentation/admin-guide/device-mapper/ |
| H A D | dm-ima.rst | 180 dm_version_str := As described in the 'Table load' section above.
181 device_metadata := As described in the 'Table load' section above.
187 as described in the 'dm_table_load' above.
219 dm_version_str := As described in the 'Table load' section above.
221 … The format is same as 'device_metadata' described in the 'Table load' section above.
223 … The format is same as 'device_metadata' described in the 'Table load' section above.
225 … The format is same as 'active_table_hash' described in the 'Device resume' section above.
227 … The format is same as 'active_table_hash' described in the 'Device resume' section above.
259 dm_version_str := As described in the 'Table load' section above.
261 … The format is same as 'device_metadata' described in the 'Table load' section above.
[all …]
|
| /openbmc/linux/Documentation/arch/arm64/ |
| H A D | elf_hwcaps.rst | 32 Where software relies on a feature described by a hwcap, it should check
46 which are described by architected ID registers inaccessible to
51 Such hwcaps are described below in the form::
62 described by ID registers alone. These may be described without
105 described by Documentation/arch/arm64/cpu-feature-registers.rst.
165 ID_AA64ISAR1_EL1.API == 0b0001, as described by
170 ID_AA64ISAR1_EL1.GPI == 0b0001, as described by
228 Functionality implied by ID_AA64PFR1_EL1.MTE == 0b0010, as described
241 Functionality implied by ID_AA64PFR1_EL1.MTE == 0b0011, as described
245 Functionality implied by ID_AA64PFR1_EL1.SME == 0b0001, as described
|
| /openbmc/linux/tools/perf/pmu-events/arch/s390/cf_z16/ |
| H A D | pai_ext.json | 141 "PublicDescription": "NNPA function with conditions as described in Common Operation"
148 "PublicDescription": "NNPA function with conditions as described in Common Operation"
155 "PublicDescription": "NNPA function with conditions as described in Common Operation"
162 "PublicDescription": "NNPA function with conditions as described in Common Operation"
169 "PublicDescription": "NNPA function with conditions as described in Common Operation"
176 "PublicDescription": "NNPA function with conditions as described in Common Operation"
|
| /openbmc/linux/Documentation/devicetree/bindings/i3c/ |
| H A D | i3c.yaml | 14 I3C busses can be described with a node for the primary I3C controller device
25 Each I2C device connected to the bus should be described in a subnode.
29 described in the device tree. This being said, one might want to attach
31 described in the device tree, which in turn means we have to describe
53 I2C devices described in the device tree to determine the maximum I2C
68 All properties described in Documentation/devicetree/bindings/i2c/i2c.txt
181 * resources described in the DT.
|
| /openbmc/linux/fs/ntfs/ |
| H A D | bitmap.h | 28 * 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 D | index.h | 22 * @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.
|
| /openbmc/linux/Documentation/devicetree/bindings/display/armada/ |
| H A D | marvell,dove-lcd.txt | 7 - 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
|
| /openbmc/linux/drivers/mfd/ |
| H A D | atmel-smc.c | 35 * 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()
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A D | vidioc-g-ext-ctrls.rst | 430 - The class containing user controls. These controls are described
438 described in :ref:`codec-controls`.
441 - The class containing camera controls. These controls are described
446 controls are described in :ref:`fm-tx-controls`.
450 described in :ref:`flash-controls`.
454 described in :ref:`jpeg-controls`.
458 described in :ref:`image-source-controls`.
462 described in :ref:`image-process-controls`.
466 are described in :ref:`fm-rx-controls`.
470 described in :ref:`rf-tuner-controls`.
[all …]
|
| H A D | metafmt-intel-ipu3.rst | 18 interface. They are formatted as described by the :c:type:`ipu3_uapi_stats_3a`
48 formatted as described by the :c:type:`ipu3_uapi_params` structure.
50 Both 3A statistics and pipeline parameters described here are closely tied to
|
| /openbmc/linux/Documentation/userspace-api/media/rc/ |
| H A D | rc-protos.rst | 183 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
|
| /openbmc/linux/Documentation/arch/loongarch/ |
| H A D | irq-chip-model.rst | 149 - CPUINTC is CSR.ECFG/CSR.ESTAT and its interrupt controller described
151 - LIOINTC is "Legacy I/OInterrupts" described in Section 11.1 of
153 - EIOINTC is "Extended I/O Interrupts" described in Section 11.2 of
155 - HTVECINTC is "HyperTransport Interrupts" described in Section 14.3 of
157 - PCH-PIC/PCH-MSI is "Interrupt Controller" described in Section 5 of
159 - PCH-LPC is "LPC Interrupts" described in Section 24.3 of
|
| /openbmc/u-boot/doc/device-tree-bindings/net/ |
| H A D | ethernet.txt | 16 - 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.
|
| /openbmc/linux/Documentation/devicetree/bindings/mmc/ |
| H A D | hi3798cv200-dw-mshc.txt | 8 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.
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | OPL-1.0 | 20 … 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…
84 …described 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…
|
| /openbmc/linux/include/uapi/drm/ |
| H A D | vmwgfx_drm.h | 252 * @rep: Output data as described above.
253 * @req: Input data as described above.
280 * @rep: Output data as described above.
281 * @req: Input data as described above.
438 * @req: Input data as described above.
439 * @rep: Output data as described above.
925 * @drm_surface_flags Flags as described above.
974 * @req: Input argument as described above.
975 * @rep: Output argument as described above.
1001 * @creq: The data used as input when the surface was created, as described
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
| H A D | redfish-error.v1_0_2.json | 10 …"longDescription": "The Redfish Specification-described type shall contain an error payload from a…
15 …"longDescription": "This property, as described by the Redfish Specification, shall contain proper…
26 …"longDescription": "The Redfish Specification-described type shall contain properties that describ…
|
| H A D | Message.v1_3_0.json | 9 …"This type shall contain a message that the Redfish service returns, as described in the Redfish S…
56 …erties contained in this object shall conform to the Redfish Specification-described requirements."
59 "description": "A set of properties described by the message.",
63 …ain an array of RFC6901-defined JSON pointers indicating the properties described by the message, …
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | redfish-error.v1_0_2.json | 10 …"longDescription": "The Redfish Specification-described type shall contain an error payload from a…
15 …"longDescription": "This property, as described by the Redfish Specification, shall contain proper…
26 …"longDescription": "The Redfish Specification-described type shall contain properties that describ…
|
| H A D | Message.v1_3_0.json | 9 …"This type shall contain a message that the Redfish service returns, as described in the Redfish S…
56 …erties contained in this object shall conform to the Redfish Specification-described requirements."
59 "description": "A set of properties described by the message.",
63 …ain an array of RFC6901-defined JSON pointers indicating the properties described by the message, …
|
| H A D | ExternalAccountProvider.v1_8_0.json | 131 …erties contained in this object shall conform to the Redfish Specification-described requirements."
283 …rties that this object contains shall conform to the Redfish Specification-described requirements."
480 …erties contained in this object shall conform to the Redfish Specification-described requirements."
493 …"longDescription": "This Redfish Specification-described type shall contain links to resources tha…
512 …erties contained in this object shall conform to the Redfish Specification-described requirements."
591 …rties contained in this object shall conform to the Redfish Specification-described requirements.",
692 …erties contained in this object shall conform to the Redfish Specification-described requirements."
731 …"ASCII": "This value shall indicate the ASCII Login flow as described under section 5.4.2 of RFC89…
732 …"CHAP": "This value shall indicate the CHAP Login flow as described under section 5.4.2 of RFC8907…
733 …"MSCHAPv1": "This value shall indicate the MS-CHAP v1 Login flow as described under section 5.4.2 …
[all …]
|
| /openbmc/linux/Documentation/admin-guide/pm/ |
| H A D | suspend-flows.rst | 93 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_>`_.
|
| /openbmc/linux/Documentation/networking/ |
| H A D | cdc_mbim.rst | 64 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
|
| /openbmc/u-boot/doc/device-tree-bindings/pinctrl/ |
| H A D | rockchip,pinctrl.txt | 37 Use rockchip,grf and rockchip,pmu described above instead.
50 cells should use the standard two-cell scheme described in
56 rockchip,pmu described above instead
63 to use, as described in pinctrl-bindings.txt in this directory.
|
| /openbmc/linux/Documentation/hwmon/ |
| H A D | abituguru-datasheet.rst | 25 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.
|