| /openbmc/u-boot/doc/device-tree-bindings/memory-controllers/ |
| H A D | st,stm32mp1-ddr.txt | 25 - st,ctl-reg : controleur values depending of the DDR type
54 - st,ctl-timing : controleur values depending of frequency and timing parameter
70 - st,ctl-map : controleur values depending of address mapping
82 - st,ctl-perf : controleur values depending of performance and scheduling
104 - st,phy-reg : phy values depending of the DDR type (DDR3/LPDDR2/LPDDR3)
118 - st,phy-timing : phy values depending of frequency and timing parameter of DDR
131 - st,phy-cal : phy cal depending of calibration or tuning of DDR
|
| /openbmc/qemu/qapi/ |
| H A D | machine-target.json | 142 # * QEMU version: CPU models may look different depending on the QEMU
145 # * machine-type: CPU model may look different depending on the
149 # CPU models may look different depending on machine and accelerator
200 # * QEMU version: CPU models may look different depending on the QEMU
203 # * machine-type: CPU model may look different depending on the
207 # CPU models may look different depending on machine and accelerator
278 # * QEMU version: CPU models may look different depending on the QEMU
281 # * machine-type: CPU model may look different depending on the
285 # CPU models may look different depending on machine and accelerator
335 # depending on QEMU version, machine type, machine options and
[all …]
|
| /openbmc/linux/Documentation/hwmon/ |
| H A D | gsc-hwmon.rst | 21 The voltage inputs are scaled either internally or by the driver depending
33 either internally or by the driver depending on the GSC version and firmware.
44 PWM value will be scaled depending on 6 temperature boundaries.
|
| H A D | adm1275.rst | 103 inX_label "vin1" or "vout1" depending on chip variant and
118 curr1_lcrit Critical minimum current. Depending on the chip
122 curr1_crit Critical maximum current. Depending on the chip
|
| H A D | nct6775.rst | 103 PCH, and SMBUS. Depending on the chip type, 2 to 6 of the temperature sources
114 either 1 degC or 0.5 degC, depending on the temperature source and
117 value. Alarms are only supported for temp1 to temp6, depending on the chip type.
251 There are up to seven data points depending on the chip type. Subsequent data
|
| /openbmc/linux/drivers/mtd/spi-nor/ |
| H A D | Kconfig | 17 Many flash memories support erasing small (4096 B) sectors. Depending
37 Depending on the flash chip this either clears the block protection
54 If the software write protection will be disabled depending on
|
| /openbmc/hiomapd/vpnor/ |
| H A D | partition.hpp | 66 * 1. Depending on the partition type,tries to open the file
76 * 1. Depending on the partition type tries to open the file
80 * partition depending on the partition type.
|
| /openbmc/linux/Documentation/driver-api/thermal/ |
| H A D | nouveau_thermal.rst | 41 Some of these thresholds may not be used by Nouveau depending
79 * 2; The fan is driven automatically depending on the temperature.
87 depending on your hardware.
|
| /openbmc/linux/include/uapi/linux/ |
| H A D | falloc.h | 22 * smaller depending on the filesystem and/or the configuration of the
53 * boundaries, but this boundary may be larger or smaller depending on
71 * depending on the filesystem and/or the configuration of the filesystem
|
| /openbmc/openbmc/meta-arm/documentation/ |
| H A D | quick-start.md | 36 …inutes depending on your internet connection speed. Also, it only fetches what is available. The…
40 Depending on what software you are building, fvp-base might not be the machine you want to build fo…
61 This will download the source, hopefully in git (depending on how the Yocto Project recipe was writ…
|
| /openbmc/u-boot/doc/device-tree-bindings/adc/ |
| H A D | st,stm32-adc.txt | 32 - clocks: Core can use up to two clocks, depending on part used:
39 - clock-names: Must be "adc" and/or "bus" depending on part used.
70 Depending on part used, some channels can be configured as differential
91 Depending on hardware (board) e.g. high/low analog input source impedance,
|
| /openbmc/u-boot/board/ti/omap5_uevm/ |
| H A D | README | 10 It is possible, depending on SYSBOOT configuration to boot from the eMMC
11 boot partitions using (name depending on documentation referenced)
|
| /openbmc/u-boot/board/ti/dra7xx/ |
| H A D | README | 10 It is possible, depending on SYSBOOT configuration to boot from the eMMC
11 boot partitions using (name depending on documentation referenced)
|
| /openbmc/linux/Documentation/PCI/endpoint/function/binding/ |
| H A D | pci-test.rst | 22 msi_interrupts Should be 1 to 32 depending on the number of MSI interrupts
24 msix_interrupts Should be 1 to 2048 depending on the number of MSI-X
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-bus-iio-adc-hi8435 | 18 Depending on in_voltageY_sensing_mode the low voltage threshold
37 Depending on in_voltageY_sensing_mode the high voltage threshold
|
| /openbmc/openpower-vpd-parser/vpd-manager/include/ |
| H A D | parser_interface.hpp | 24 * @return parsed format for VPD data, depending upon the
52 * @throw May throw exception depending on the implementation of derived
|
| /openbmc/phosphor-mboxd/vpnor/ |
| H A D | pnor_partition.hpp | 96 * 1. Depending on the partition type,tries to open the file
106 * 1. Depending on the partition type tries to open the file
110 * partition depending on the partition type.
|
| /openbmc/linux/include/linux/ |
| H A D | iosys-map.h | 16 * When accessing a memory region, depending on its location, users may have to
89 * buffer memory. Depending on the location of the memory, the provided helpers
229 * Depending on the state of struct iosys_map.is_iomem, tests if the
246 * Depending on the state of struct iosys_map.is_iomem, tests if the
283 * system memory. Depending on the buffer's location, the helper picks the
303 * system memory. Depending on the mapping location, the helper picks the
320 * Increments the address stored in a iosys mapping. Depending on the
338 * Set value in iosys_map. Depending on the buffer's location, the helper
|
| /openbmc/u-boot/doc/ |
| H A D | README.sched | 37 changing "#define MAX_THREADS" depending on the available memory.
40 increased depending on the requirement and the available memory,
|
| /openbmc/linux/Documentation/sound/soc/ |
| H A D | clocking.rst | 18 their speed can be altered by software (depending on the system use and to save
39 it is best to configure BCLK to the lowest possible speed (depending on your
|
| H A D | pops-clicks.rst | 12 depending on the audio usage and this can subsequently cause a small pop or
39 playback in that components are powered in a sequence depending upon stream
|
| /openbmc/openbmc/poky/meta/recipes-devtools/valgrind/valgrind/ |
| H A D | valgrind-make-ld-XXX.so-strlen-intercept-optional.patch | 6 Hack: Depending on how glibc was compiled (e.g. optimised for size or
27 + /* Hack: Depending on how glibc was compiled (e.g. optimised for size or
|
| /openbmc/linux/Documentation/devicetree/bindings/interconnect/ |
| H A D | interconnect.txt | 15 depending on the use case. Interconnect providers can also be interconnect
42 multiple paths from different providers depending on use case and the
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-graphics/libsdl/libsdl-1.2.15/ |
| H A D | 0001-stdlib-Make-iconv-use-portable-across-glibc-musl.patch | 22 -/* Depending on which standard the iconv() was implemented with,
43 + /* iconv's second parameter may or may not be `const char const *` depending on the
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | Manifest.v1_1_2.json | 96 …e the request details of a stanza within a manifest. Its contents vary depending on the value of …
117 … the response details of a stanza within a manifest. Its contents vary depending on the value of …
173 …shall contain the request details for the stanza, and the contents vary depending on the value of …
185 …hall contain the response details for the stanza, and the contents vary depending on the value of …
|