| /openbmc/u-boot/Documentation/devicetree/bindings/ram/ |
| H A D | fsl,mpc83xx-mem-controller.txt | 19 - p_impedance_override: DDR driver software p-impedance override; possible
26 - n_impedance_override: DDR driver software n-impedance override; possible
33 - odt_termination_value: ODT termination value for I/Os; possible values:
36 - ddr_type: Selects voltage level for DDR pads; possible
41 possible values:
44 - m_odr: Disable memory transaction reordering; possible
48 - clock_adjust: Clock adjust; possible values:
53 - ext_refresh_rec: Extended refresh recovery time; possible values:
55 - read_to_write: Read-to-write turnaround; possible values:
57 - write_to_read: Write-to-read turnaround; possible values:
[all …]
|
| /openbmc/openbmc/poky/meta/lib/oeqa/core/tests/cases/ |
| H A D | depends.py | 13 self.assertTrue(True, msg='How is this possible?')
17 self.assertTrue(True, msg='How is this possible?')
21 self.assertTrue(True, msg='How is this possible?')
25 self.assertTrue(True, msg='How is this possible?')
29 self.assertTrue(True, msg='How is this possible?')
33 self.assertTrue(True, msg='How is this possible?')
37 self.assertTrue(True, msg='How is this possible?')
41 self.assertTrue(True, msg='How is this possible?')
|
| H A D | oetag.py | 13 self.assertTrue(True, msg='How is this possible?')
17 self.assertTrue(True, msg='How is this possible?')
21 self.assertTrue(True, msg='How is this possible?')
24 self.assertTrue(True, msg='How is this possible?')
30 self.assertTrue(True, msg='How is this possible?')
34 self.assertTrue(True, msg='How is this possible?')
37 self.assertTrue(True, msg='How is this possible?')
|
| H A D | timeout.py | 17 self.assertTrue(True, msg='How is this possible?')
22 self.assertTrue(True, msg='How is this possible?')
31 self.assertTrue(False, msg='How is this possible?')
|
| /openbmc/pldm/pldmtool/oem/ibm/ |
| H A D | oem_ibm_state_set.hpp | 9 /** @brief PLDM OEM IBM Code Update possible state set values
21 /** @brief PLDM OEM IBM Verification possible state set values
31 /** @brief PLDM OEM IBM system power state possible state set values
38 /** @brief PLDM OEM IBM boot state possible state set values
60 /** @brief Map for PLDM OEM IBM firmware update possible state values
70 /** @brief Map for PLDM OEM IBM verification state possible state values
79 /** @brief Map for PLDM OEM IBM systerm power state possible state values
84 /** @brief Map for PLDM OEM IBM boot state possible state values
90 /** @brief Map for populating PLDM OEM IBM state sets with possible state values
|
| /openbmc/pldm/libpldmresponder/ |
| H A D | bios_enum_attribute.hpp | 75 /** @brief Get index of the given value in possible values
77 * @param[in] pVs - The possible values
78 * @return Index of the given value in possible values
83 /** @brief Get handles of possible values
85 * @param[in] pVs - The possible values
107 /** @brief Get index of the current value in possible values
108 * @return The index of the current value in possible values
112 /** @brief Get index of the property value in possible values
115 * @return The index of the property value in possible values
|
| /openbmc/qemu/tests/qapi-schema/ |
| H A D | enum-bad-name.json | 2 # FIXME reports 'not\possible' instead of 'not\\possible'
3 { 'enum': 'MyEnum', 'data': [ 'not\\possible' ] }
|
| /openbmc/phosphor-settingsd/ |
| H A D | README-settings-manager.md | 9 - The above makes it possible to not even create settings objects that do not
12 - It should be possible, for example, for host0/ and host1/ on a system with two
16 - It should be possible to specify default settings for a system at build-time,
41 It is possible to specify this policy file via a bitbake recipe for a system
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/Item/ |
| H A D | Accelerator.interface.yaml | 3 used to perform some functions more efficiently than is possible in software
4 running on a general-purpose CPU. Examples of possible hardware accelerators
17 Possible accelerator type
|
| H A D | Drive.interface.yaml | 49 Possible communication protocol types
71 Possible Drive type
89 Possible encryption states drives could have
102 Possible lock states drives could have
|
| /openbmc/u-boot/board/bachmann/ot1200/ |
| H A D | README | 9 port is always up and auto-negotiation is not possible.
12 FEC is connected to a normal phy and auto-negotiation is possible.
16 make is possible to boot the linux kernel and make use variant specific
|
| /openbmc/openpower-hw-diags/ |
| H A D | config.h.in | 6 // Use constexpr and avoid #define whenever possible. This has the benefit of
7 // compiling as much code as possible, regardless if it is actually used. Thus
19 // Avoid using #define whenever possible. See note above for reason.
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/tipcutils/tipcutils/ |
| H A D | 0001-test-ptts-Set-recv-buffer-size-too-max-to-receive-as.patch | 5 packets as possible
13 packets as possible, and give a hint to user when possible overrun occurs. Note
55 + * Set SO_RCVBUF to max int value to receive as many packets as possible.
|
| /openbmc/phosphor-state-manager/target_files/ |
| H A D | obmc-fan-watchdog-takeover.target | 2 #is no longer desired or possible. It should also add units to this target
4 #desired or possible.
|
| /openbmc/u-boot/doc/ |
| H A D | README.commands | 106 maxv: Maximum number of possible completions that may be returned by
109 cmdv: Used to return possible values for the last argument. The last
110 possible completion must be followed by NULL.
112 The function returns the number of possible completions (without the terminating
122 This makes it possible for the final link to extract all commands
|
| /openbmc/qemu/tests/tcg/s390x/ |
| H A D | add-logical-with-carry.c | 24 /* cc0->cc2 is not possible */
25 /* cc0->cc3 is not possible */
26 /* cc1->cc0 is not possible */
30 /* cc2->cc0 is not possible */
33 /* cc2->cc3 is not possible */
34 /* cc3->cc0 is not possible */
|
| /openbmc/pldm/libpldmresponder/test/ |
| H A D | libpldmresponder_bios_enum_attribute_test.cpp | 108 2, /* number of possible value */ in TEST_F()
109 2, 0, /* possible value handle */ in TEST_F()
110 3, 0, /* possible value handle */ in TEST_F()
213 2, /* number of possible value */ in TEST_F()
214 2, 0, /* possible value handle */ in TEST_F()
215 3, 0, /* possible value handle */ in TEST_F()
|
| /openbmc/u-boot/drivers/sysreset/ |
| H A D | sysreset_mpc83xx.h | 11 * String array for all possible event types; indexed by the EVENT field of the
26 * String array for all possible master IDs, which reflects the source of the
66 * String array for all possible transfer types; indexed by the TTYPE field of
|
| /openbmc/u-boot/board/synopsys/emsdp/ |
| H A D | README | 11 Since this board is based on FPGA it's possible to load and use different
13 possible configuration which means the same one binary will work on more
18 - The first channel is used for serial debug port (which makes it possible
29 - Also with help of this FTDI chip it is possible to reset entire
76 2. Though it is possible to load U-Boot as a simple Elf file via JTAG right
|
| /openbmc/u-boot/fs/fat/ |
| H A D | Kconfig | 17 int "Set maximum possible clustersize"
21 Set the maximum possible clustersize for the FAT filesytem. This
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | Control.v1_7_0.json | 86 "description": "The maximum possible setting for this control.",
88 …"longDescription": "This property shall indicate the maximum possible value of the `SetPoint` or `…
96 "description": "The minimum possible setting for this control.",
98 …"longDescription": "This property shall indicate the minimum possible value of the `SetPoint` or `…
412 "description": "The maximum possible setting for this control.",
414 …"longDescription": "This property shall indicate the maximum possible value of the `SetPoint` or `…
422 "description": "The minimum possible setting for this control.",
424 …"longDescription": "This property shall indicate the minimum possible value of the `SetPoint` or `…
567 "description": "The maximum possible setting for this control.",
569 …"longDescription": "This property shall indicate the maximum possible value of the `SetPoint` or `…
[all …]
|
| /openbmc/qemu/include/hw/riscv/ |
| H A D | boot_opensbi.h | 19 /** Possible next mode values */
46 * It is possible that the previous booting stage uses same link
76 * It is possible that the previous booting stage uses same link
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Telemetry/ |
| H A D | ReportManager.interface.yaml | 27 Indicates when readings should be updated. Possible values are
32 Indicates how readings should be updated. Possible values are
41 Possible additional actions to trigger after readings' update,
|
| /openbmc/docs/process/ |
| H A D | subproject-maintainership.md | 44 (BMCs). While it exploits existing open-source projects where possible, the
179 Security concerns cut both ways. It's possible that:
192 it may be possible to quickly revert the problematic code once its existence is
220 Maintainers are people: Life happens. Sometimes it is possible to communicate
241 at least possible to discuss on-boarding new maintainers to affected
242 subprojects. Where possible, this is the preferred route to enabling forward
247 regard to reason it is not possible to hold discussion with the maintainers in
261 If any maintainer of a subproject is responsive in the project it's possible to
|
| /openbmc/u-boot/arch/x86/include/asm/acpi/ |
| H A D | irqlinks.asl | 34 /* Possible Resource Settings for this Link */
92 /* Possible Resource Settings for this Link */
150 /* Possible Resource Settings for this Link */
208 /* Possible Resource Settings for this Link */
266 /* Possible Resource Settings for this Link */
324 /* Possible Resource Settings for this Link */
382 /* Possible Resource Settings for this Link */
440 /* Possible Resource Settings for this Link */
|