Searched full:will (Results 1 – 25 of 6602) sorted by relevance
12345678910>>...265
| /openbmc/u-boot/doc/ |
| H A D | README.POST | 28 2) The results of tests shall be saved so that it will be possible to
56 A new optional module will be added to U-Boot, which will run POST
57 tests and collect their results at boot time. Also, U-Boot will
61 The list of available POST tests will be configured at U-Boot build
62 time. The POST layer will allow the developer to add any custom POST
63 tests. All POST tests will be divided into the following groups:
67 This group will contain those tests that run only once on
72 This group will contain those tests that do not take much
77 This group will contain POST tests that consume much time
82 This group will contain those tests that can be run manually.
[all …]
|
| /openbmc/linux/drivers/media/usb/gspca/ |
| D | Kconfig | |
| /openbmc/docs/designs/oem/ibm/ |
| H A D | system-power-mode.md | 20 thermal monitoring and control. When a system is powered on, the OCCs will go to
21 an Active state. Anytime the OCC state changes to active, the BMC will need to
22 send a mode change and idle power saver (IPS) settings to the OCC. It will also
28 When a system is booted, the OCC will move to an ACTIVE state. In the ACTIVE
31 necessary to reset the OCC. When this happens, the OCC will move out of ACTIVE
32 state. After recovery, the OCC will be put back into the ACTIVE state. Anytime
34 runtime, the BMC will need to send the mode and the idle power saver settings to
40 Current Customer Settable System Power Modes that will be sent to the OCCs:
47 committee and will be used if/when approved.
57 Defaults will need to be configurable by the system owner (via JSON file)
[all …]
|
| /openbmc/linux/drivers/media/test-drivers/vidtv/ |
| D | vidtv_channel.h | |
| /openbmc/linux/Documentation/bpf/ |
| D | bpf_prog_run.rst | |
| /openbmc/linux/sound/pci/ |
| D | Kconfig | |
| /openbmc/docs/designs/ |
| H A D | power-recovery.md | 32 told) that chassis power can no longer be supported, but power to the BMC will
42 The goal of this design document is to describe how OpenBMC firmware will deal
66 - Do nothing when power is lost to the system (this will be the default)
77 policy. This is a separate instance of the `PowerRestorePolicy` which will be
79 setting is not the default, `None`, then software will execute the policy
92 - At a minimum, `PinholeReset` will be added. Others can be added as needed
103 this scenario after a BMC reboot, chassis-state-manager will check to see what
156 entire system is imminent(i.e. a blackout scenario where BMC will also lose
165 An application will be run after the chassis and host states have been
166 determined which will only run if the chassis power is not on.
[all …]
|
| H A D | bmc-reset-with-host-up.md | 69 - Both IPMI and PLDM stacks will give the host a set amount of time to respond.
70 Lack of response within this time limit will result in the BMC potentially
73 - IPMI and PLDM will implement a phosphor-dbus-interface interface,
74 `xyz.openbmc_project.Condition.HostFirmware`, which will have a
80 - IPMI will continue to utilize the SMS_ATN command to indicate to the host that
82 command, it will be considered up and running
86 - PLDM will utilize a GetTID command to the host to determine if it is running
87 - Where applicable, PLDM will provide a mechanism to distinguish between
91 firmware and talking PLDM but the BMC recovery paths will differ based on
107 IPMI and PLDM software will be started as applicable. A combination of systemd
[all …]
|
| /openbmc/linux/Documentation/ABI/testing/ |
| D | sysfs-class-regulator | |
| /openbmc/phosphor-power/phosphor-power-sequencer/docs/ |
| H A D | power_loss.md | 24 `phosphor-power-sequencer` application will take no action.
27 device will normally change the chassis power good (pgood) signal from true to
28 false. `phosphor-power-sequencer` will isolate the failure to the power supply
29 rail. `phosphor-power-sequencer` will log a power supply error. This error will
37 The system loses all power. It will be completely off until utility power is
46 If the blackout affects all chassis, the system loses all power. It will behave
49 If the blackout only affects some chassis, the following steps will occur:
51 - The `phosphor-chassis-power` application will do the following:
56 - The `Available` property will be set to false for chassis that are
60 - If the BMC was reset by hardware due to the blackout, the following will
[all …]
|
| H A D | chassis_status.md | 59 When the system is being powered on, the `state` will be changed to 1 for the
65 that object path will change to 1. When all chassis whose `state` was set to 1
67 will change to 1.
70 `pgood` property for that chassis's object path will change to 0. The `pgood`
71 property for the system object path will remain set to 1 for a period of time.
72 Eventually the system will be powered off due to the power good fault. See
75 When the system is being powered off, the `state` will be changed to 0 for the
79 for that object path will change to 0. When all chassis have successfully
80 powered off, the `pgood` property for the system object path will change to 0.
97 property will be set.
[all …]
|
| /openbmc/u-boot/drivers/serial/ |
| H A D | Kconfig | 44 the full UART driver will be omitted, thus saving space.
54 the full UART driver will be omitted, thus saving space.
64 the full UART driver will be omitted, thus saving space.
180 the drivers may conflict and you will get strange output.
183 prompt "Select which UART will provide the debug UART"
191 You will need to provide parameters to make this work. The driver will
198 You will need to provide parameters to make this work. The driver will
206 You will need to provide parameters to make this work. The
207 driver will be available until the real driver model serial is
215 You will need to provide parameters to make this work. The
[all …]
|
| /openbmc/openbmc/meta-arm/documentation/ |
| H A D | releases.md | 3 …e of the Yocto Project will have a branch named “dunfell” in the official git repository, and laye…
8 …will allow for a more stable software platform for software to be developed, tested, and released.…
14 … in a timely fashion (after the time crunch). Nagging emails will be sent and managers will be inv…
17 …ll code will be compiled as part of the CI process of the gerrit code review. Also, testing on vir…
20 …d branches for meta-arm will be released as close as possible to the release of the YP LTS release…
22 …will only be two active development branches at any given time: master and the most recent Long Te…
24 Named branch release will coincide with Yocto Project releases. These non-LTS branches will be bug …
27 When YP is approaching release, meta-arm will attempt to stabilize master so that the releases can …
30 …master branch. Previous named branches are now frozen and will not accept new patches (but will co…
34 …ag with the Yocto Project version number will be added. For example, `4.3`. Also, this tag versi…
[all …]
|
| /openbmc/linux/drivers/usb/serial/ |
| D | Kconfig | |
| /openbmc/linux/Documentation/arch/s390/ |
| D | common_io.rst | |
| /openbmc/openpower-hw-diags/attn/ |
| H A D | Attention_Handler.md | 24 attention handler will query the state of the host to determine the nature of
69 the host is started. When the attention handler is started it will register
71 resident in memory waiting for attentions. The attention handler will be stopped
74 If the attention handler terminates due to an error condition it will
81 When the attention signal becomes active the attention handler will begin
82 handling attentions. Using the PDBG interface the attention handler will query
84 enabled processor will be queried and a map of active attentions will be
85 created. The first attention of highest priority will be the one that is
94 dump. The attention handler will wait, up to one hour, for the dump to complete
113 will consider two cases namely a TI with SRC and a TI with EID.
[all …]
|
| /openbmc/linux/tools/testing/ktest/ |
| D | sample.conf | |
| /openbmc/linux/sound/isa/ |
| D | Kconfig | |
| /openbmc/linux/drivers/net/wireless/intel/ipw2x00/ |
| D | Kconfig | |
| /openbmc/phosphor-power/phosphor-regulators/docs/ |
| H A D | sensor_monitoring.md | 46 When regulator monitoring is disabled, the following changes will be made to all
49 - The Value property will be set to NaN.
50 - The Available property will be set to false.
56 - The error will be logged. If the same error occurs repeatedly on a rail, it
57 will only be logged once per system boot.
58 - Any remaining actions for the rail will be skipped.
59 - The following changes will be made to all D-Bus sensor objects for this rail:
60 - The Value property will be set to NaN.
61 - The Functional property will be set to false.
62 - Sensor monitoring will continue with the next rail or voltage regulator.
[all …]
|
| /openbmc/linux/Documentation/userspace-api/ |
| D | seccomp_filter.rst | |
| /openbmc/linux/Documentation/filesystems/ |
| D | fiemap.rst | |
| /openbmc/qemu/include/io/ |
| H A D | channel-socket.h | 11 * This library is distributed in the hope that it will be useful,
90 * will run in the foreground so the caller will not regain
106 * context will be used.
109 * will run in the background so the caller will regain
111 * will be invoked on completion or failure. The @addr
112 * parameter will be copied, so may be freed as soon
131 * will run in the foreground so the caller will not regain
149 * context will be used.
152 * will run in the background so the caller will regain
154 * will be invoked on completion or failure. The @addr
[all …]
|
| /openbmc/entity-manager/ |
| H A D | Doxyfile | 9 # All text after a single hash (#) is considered a comment and will be ignored.
51 # pixels and the maximum width should not exceed 200 pixels. Doxygen will copy
57 # into which the generated documentation will be written. If a relative path is
58 # entered, it will be relative to the location where doxygen was started. If
59 # left blank the current directory will be used.
63 # If the CREATE_SUBDIRS tag is set to YES then doxygen will create 4096 sub-
65 # will distribute the generated files over these directories. Enabling this
73 # If the ALLOW_UNICODE_NAMES tag is set to YES, doxygen will allow non-ASCII
75 # characters will be escaped, for example _xE3_x81_x84 will be used for Unicode
82 # documentation generated by doxygen is written. Doxygen will use this
[all …]
|
| /openbmc/linux/drivers/input/serio/ |
| D | Kconfig | |
12345678910>>...265