Home
last modified time | relevance | path

Searched full:specify (Results 1 – 25 of 3286) sorted by relevance

12345678910>>...132

/openbmc/linux/include/uapi/linux/
H A Damt.h26 /* This attribute specify mode etier Gateway or Relay. */
28 /* This attribute specify Relay port.
30 * to specify relay(remote) port.
35 /* This attribute specify Gateway port.
41 /* This attribute specify physical device */
43 /* This attribute specify local ip address */
45 /* This attribute specify Relay ip address.
49 /* This attribute specify Discovery ip address.
55 /* This attribute specify number of maximum tunnel. */
/openbmc/linux/tools/perf/pmu-events/arch/x86/goldmontplus/
H A Dcache.json189 …"BriefDescription": "Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplica…
201 …n responses from the uncore subsystem. Requires MSR_OFFCORE_RESP[0,1] to specify request type and …
211 … (demand & prefetch) hit the L2 cache. Requires MSR_OFFCORE_RESP[0,1] to specify request type and …
221 …r module, data forwarding is required. Requires MSR_OFFCORE_RESP[0,1] to specify request type and …
231 …p miss in the other processor module. Requires MSR_OFFCORE_RESP[0,1] to specify request type and …
241 …miss to when any response is received. Requires MSR_OFFCORE_RESP[0,1] to specify request type and …
251 …n responses from the uncore subsystem. Requires MSR_OFFCORE_RESP[0,1] to specify request type and …
261 …L1 or L2 prefetchers hit the L2 cache. Requires MSR_OFFCORE_RESP[0,1] to specify request type and …
271 …r module, data forwarding is required. Requires MSR_OFFCORE_RESP[0,1] to specify request type and …
281 …p miss in the other processor module. Requires MSR_OFFCORE_RESP[0,1] to specify request type and …
[all …]
/openbmc/linux/tools/perf/pmu-events/arch/x86/goldmont/
H A Dcache.json189 …"BriefDescription": "Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplica…
201 …and & prefetch) that hit the L2 cache. Requires MSR_OFFCORE_RESP[0,1] to specify request type and …
211 …nd & prefetch) that miss the L2 cache. Requires MSR_OFFCORE_RESP[0,1] to specify request type and …
221 …r module, data forwarding is required. Requires MSR_OFFCORE_RESP[0,1] to specify request type and …
231 …odule, no data forwarding is required. Requires MSR_OFFCORE_RESP[0,1] to specify request type and …
241 …p miss in the other processor module. Requires MSR_OFFCORE_RESP[0,1] to specify request type and …
251 … L2 prefetchers that hit the L2 cache. Requires MSR_OFFCORE_RESP[0,1] to specify request type and …
261 …L2 prefetchers that miss the L2 cache. Requires MSR_OFFCORE_RESP[0,1] to specify request type and …
271 …r module, data forwarding is required. Requires MSR_OFFCORE_RESP[0,1] to specify request type and …
281 …odule, no data forwarding is required. Requires MSR_OFFCORE_RESP[0,1] to specify request type and …
[all …]
/openbmc/linux/Documentation/devicetree/bindings/mmc/
H A Dnvidia,tegra20-sdhci.yaml69 description: specify GPIOs for power control
92 description: Specify the default inbound sampling clock trimmer value for
105 description: Specify the default outbound clock trimmer value.
109 description: Specify DQS trim value for HS400 timing.
113 description: Specify drive strength calibration offsets for 1.8 V
118 description: Specify drive strength used as a fallback in case the
123 description: Specify drive strength calibration offsets for 3.3 V
128 description: Specify drive strength used as a fallback in case the
133 description: Specify drive strength calibration offsets for SDR104 mode.
137 description: Specify drive strength calibration offsets for HS400 mode.
[all …]
/openbmc/linux/tools/perf/Documentation/
H A Dperf-bench.txt21 Specify number of times to repeat the run (default 10).
25 Specify format style.
94 Specify number of groups
98 Specify number of loops
125 Specify number of loops.
163 Specify size of memory to copy (default: 1MB).
168 Specify function to copy (default: default).
187 Specify size of memory to set (default: 1MB).
192 Specify function to set (default: default).
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/
H A DMetricReportDefinition.v1_4_6.json13 "description": "This property shall specify a valid odata or Redfish property.",
54 …"longDescription": "This type shall specify the function to apply to the list of metric properties…
70 …alue in the metric report shall specify the end of the time interval and the `CollectionDuration` …
71 …lue instances, the `Timestamp` property value in the metric report shall specify the point in time…
72 …ue in the metric report shall specify the end of the time interval. The `CollectionDuration` prop…
74 … "longDescription": "This type shall specify the time scope of the corresponding metric values.",
83 "description": "This property shall specify a valid odata or Redfish property.",
120 …"longDescription": "The properties shall specify a set of metrics to include in the metric report.…
123 "description": "This property shall specify a valid odata or Redfish property.",
138 …"longDescription": "This property shall specify the duration over which the function is computed.",
[all …]
H A DOperatingConfig.v1_0_4.json13 "description": "This property shall specify a valid odata or Redfish property.",
37 "longDescription": "This type shall specify the clock speed for a set of cores.",
40 "description": "This property shall specify a valid odata or Redfish property.",
95 "description": "This property shall specify a valid odata or Redfish property.",
116 "description": "This property shall specify a valid odata or Redfish property.",
169 …"longDescription": "This property shall contain an array of objects that specify the clock speed f…
250 …"longDescription": "The property shall contain an array of objects that specify the turbo profile …
265 … "longDescription": "This type shall specify the turbo profile for a set of active cores.",
268 "description": "This property shall specify a valid odata or Redfish property.",
H A DMetricDefinition.v1_3_4.json13 "description": "This property shall specify a valid odata or Redfish property.",
79 "description": "This property shall specify a valid odata or Redfish property.",
155 "description": "This property shall specify a valid odata or Redfish property.",
204 … "longDescription": "This property shall specify whether the metric can be used in a calculation.",
237 …"longDescription": "This property shall specify the time interval over the metric calculation is p…
273 …"longDescription": "The values of the property shall specify the possible values of the discrete m…
291 … "longDescription": "This property shall specify the implementation of the metric.",
332 "longDescription": "This property shall specify the data-type of the metric.",
358 "longDescription": "This property shall specify the type of metric.",
404 …"longDescription": "This property shall specify the number of significant digits in the metric rea…
[all …]
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/
H A DMetricReportDefinition.v1_4_6.json13 "description": "This property shall specify a valid odata or Redfish property.",
54 …"longDescription": "This type shall specify the function to apply to the list of metric properties…
70 …alue in the metric report shall specify the end of the time interval and the `CollectionDuration` …
71 …lue instances, the `Timestamp` property value in the metric report shall specify the point in time…
72 …ue in the metric report shall specify the end of the time interval. The `CollectionDuration` prop…
74 … "longDescription": "This type shall specify the time scope of the corresponding metric values.",
83 "description": "This property shall specify a valid odata or Redfish property.",
120 …"longDescription": "The properties shall specify a set of metrics to include in the metric report.…
123 "description": "This property shall specify a valid odata or Redfish property.",
138 …"longDescription": "This property shall specify the duration over which the function is computed.",
[all …]
H A DOperatingConfig.v1_0_4.json13 "description": "This property shall specify a valid odata or Redfish property.",
37 "longDescription": "This type shall specify the clock speed for a set of cores.",
40 "description": "This property shall specify a valid odata or Redfish property.",
95 "description": "This property shall specify a valid odata or Redfish property.",
116 "description": "This property shall specify a valid odata or Redfish property.",
169 …"longDescription": "This property shall contain an array of objects that specify the clock speed f…
250 …"longDescription": "The property shall contain an array of objects that specify the turbo profile …
265 … "longDescription": "This type shall specify the turbo profile for a set of active cores.",
268 "description": "This property shall specify a valid odata or Redfish property.",
H A DMetricDefinition.v1_3_4.json13 "description": "This property shall specify a valid odata or Redfish property.",
79 "description": "This property shall specify a valid odata or Redfish property.",
155 "description": "This property shall specify a valid odata or Redfish property.",
204 … "longDescription": "This property shall specify whether the metric can be used in a calculation.",
237 …"longDescription": "This property shall specify the time interval over the metric calculation is p…
273 …"longDescription": "The values of the property shall specify the possible values of the discrete m…
291 … "longDescription": "This property shall specify the implementation of the metric.",
332 "longDescription": "This property shall specify the data-type of the metric.",
358 "longDescription": "This property shall specify the type of metric.",
404 …"longDescription": "This property shall specify the number of significant digits in the metric rea…
[all …]
/openbmc/phosphor-host-ipmid/docs/
H A Dipmi-network-format.md13 Specify 'chassis bootdev', field 96, data1 0x00 0x08 0x61 0x80
24 Specify 'chassis bootdev', field 96, data1 0x00 0x08 0x61 0x80
28 Specify the version (only 1 at the moment) 0x00 0x01
30 Specify the size of the MAC address and IP address. This is used to
37 Specify 'ignore' or 'static/dynamic' flags. The second byte specifies to use
/openbmc/linux/Documentation/admin-guide/cgroup-v1/
H A Dblkio-controller.rst14 specify upper IO rate limits on devices. This policy is implemented in
35 Specify a bandwidth rate on particular device for root group. The format
140 two fields specify the major and minor number of the device and
146 two fields specify the major and minor number of the device and
153 or async. First two fields specify the major and minor number of the
160 or async. First two fields specify the major and minor number of the
174 specify the major and minor number of the device, third field
189 read or write, sync or async. First two fields specify the major and
241 from service tree of the device. First two fields specify the major
286 or async. First two fields specify the major and minor number of the
[all …]
/openbmc/linux/Documentation/devicetree/bindings/gpio/
H A Dgpio-xgene-sb.txt24 - second cell is used to specify the gpio polarity:
31 - second cell is used to specify flags.
33 - apm,nr-gpios: Optional, specify number of gpios pin.
34 - apm,nr-irqs: Optional, specify number of interrupt pins.
35 - apm,irq-start: Optional, specify lowest gpio pin support interrupt.
H A D8xxx_gpio.txt8 See bindings/gpio/gpio.txt for details of how to specify GPIO
13 interrupt client nodes section) for details how to specify this GPIO
26 and the second cell is used to specify optional
35 cells required to specify an interrupt within
/openbmc/openbmc/poky/meta/conf/machine/include/mips/
H A DREADME45 MIPSPKGSFX_ABI - This is used to specify an alternative ABI when the previous
49 MIPSPKGSFX_R6 - This is used to specify the presence of release 6.
52 MIPSPKGSFX_64R6 - This is used to specify "isa" in the tuple.
55 MIPSPKGSFX_32R6 - This is used to specify "isa32" in the tuple.
/openbmc/linux/Documentation/devicetree/bindings/powerpc/fsl/
H A Dpamu.txt59 Two cells that specify the geometry of the primary PAMU
62 specify a value of 1.
65 Two cells that specify the geometry of the secondary PAMU
68 specify a value of 1.
72 Devices that have LIODNs need to specify links to the parent PAMU controller
84 Two cells that specify the location of the LIODN register
/openbmc/linux/Documentation/devicetree/bindings/sound/
H A Dmt8195-afe-pcm.yaml88 description: Specify which input channel should be disabled.
93 description: Specify which input channel should be disabled.
97 description: Specify etdm in mclk output rate for always on case.
100 description: Specify etdm out mclk output rate for always on case.
113 etdm modules can share the same external clock pin. Specify
124 etdm modules can share the same external clock pin. Specify
/openbmc/openbmc/meta-openembedded/meta-initramfs/recipes-bsp/kexecboot/
H A Dkexecboot-cfg_0.2.bb20 # Specify full kernel path on target.
23 # Specify which device tree blob to use
32 # Specify optional initrd/initramfs.
35 # Specify full path for a custom icon for the menu-item.
/openbmc/qemu/docs/system/s390x/
H A Dbootdevices.rst8 have to explicitly specify the disk where you want to boot from (or "IPL" from,
24 information in order to be bootable), it is recommended to specify a ``scsi-cd``
41 not specify a boot device with the ``bootindex`` property, there is still a
45 It is really recommended to always specify the boot device with the
50 specify the ``bootindex`` with these commands. Note that the convenience
55 recommended to specify a CD-ROM device via ``-device scsi-cd`` (as mentioned
112 important for booting via the network. If you don't specify the ``bootindex``
/openbmc/linux/arch/s390/include/asm/fpu/
H A Dapi.h11 * 2. For kernel_fpu_begin(), specify the vector register range you want to
15 * half of the vector registers, for example, specify KERNEL_VXR_LOW.
18 * specify KERNEL_VXR_HIGH.
32 * 5. To use vector floating-point instructions, specify the KERNEL_FPC
36 * 6. To use floating-point registers and instructions only, specify the
/openbmc/linux/Documentation/filesystems/
H A Dceph.rst97 You only need to specify a single monitor, as the client will get the
98 full list when it connects. (However, if the monitor you specify
133 Specify the IP and/or port the client should bind to locally.
139 Specify the maximum write size in bytes. Default: 64 MB.
142 Specify the maximum read size in bytes. Default: 64 MB.
145 Specify the maximum readahead size in bytes. Default: 8 MB.
148 Specify the timeout value for mount (in seconds), in the case
153 Specify the maximum number of caps to hold. Unused caps are released
/openbmc/linux/Documentation/devicetree/bindings/net/nfc/
H A Dti,trf7970a.yaml20 Specify autosuspend delay in milliseconds.
24 Set to specify that the input frequency to the trf7970a is 13560000Hz or
30 Specify that the trf7970a being used has the "EN2 RF" erratum
38 Specify that the trf7970a being used has the "IRQ Status Read" erratum
/openbmc/qemu/docs/
H A Dqemu-option-trace.rst.inc2 Specify tracing options.
9 or ``ftrace`` tracing backend. To specify multiple events or patterns,
10 specify the :option:`-trace` option multiple times.
/openbmc/entity-manager/
H A DDoxyfile49 # With the PROJECT_LOGO tag one can specify a logo or an icon that is included
56 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path
81 # The OUTPUT_LANGUAGE tag is used to specify the language in which all
96 # The OUTPUT_TEXT_DIRECTION tag is used to specify the direction in which all
169 # Note that you can specify absolute paths here, but also relative paths, which
179 # specify the list of include paths that are normally passed to the compiler
249 # This tag can be used to specify a number of aliases that act as commands in
717 # The FILE_VERSION_FILTER tag can be used to specify a program or script that
727 # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
731 # optionally specify a file name after the option, if omitted DoxygenLayout.xml
[all …]

12345678910>>...132