| /openbmc/linux/Documentation/admin-guide/pm/ |
| H A D | strategies.rst | 20 designated devices, triggering a transition to the ``working state`` in which
25 The other strategy, referred to as the :doc:`working-state power management
26 <working-state>`, is based on adjusting the power states of individual hardware
27 components of the system, as needed, in the working state. In consequence, if
28 this strategy is in use, the working state of the system usually does not
44 back to the working state can only be started by a limited set of devices, so
53 away from the laptop keyboard, it probably should stay in the working state and
54 use the working-state power management in case it becomes idle, because the user
|
| H A D | suspend-flows.rst | 13 system to get from the working state into one of the supported
19 For those sleep states, the transition from the working state of the system into
23 working state is referred to as *system resume*.
45 The following steps are taken in order to transition the system from the working
54 up after getting back to the working state.
92 would be triggered in the working state of the system (those actions are
124 :ref:`suspend-to-idle <s2idle>` sleep state into the working state:
137 2. Resuming devices and restoring the working-state configuration of IRQs.
146 The working-state configuration of IRQs is restored after the *noirq* resume
167 The following steps are taken in order to transition the system from the working
[all …]
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | Community-Spec-1.0 | 6 similar materials under this Working Group, and 2) how the materials
18 materials. Contributor also acknowledges that the Working Group may
23 copyright license must include attribution to the Working Group in any
24 derivative work based on materials developed by the Working Group.
102 2.3. Effect of Withdrawal. Contributor may withdraw from the Working Group
104 the Working Group repository’s Notices.md file. All of Contributor’s
105 existing commitments and obligations with respect to the Working Group
129 4. Source Code License. Any source code developed by the Working Group is
130 solely subject the source code license included in the Working Group’s
151 among competitors under the auspices of the Working Group.
[all …]
|
| /openbmc/linux/drivers/ufs/host/ |
| H A D | ufshcd-pltfrm.h | 20 u32 rx_pwr_pwm; /* rx pwm working pwr */
21 u32 tx_pwr_pwm; /* tx pwm working pwr */
22 u32 rx_pwr_hs; /* rx hs working pwr */
23 u32 tx_pwr_hs; /* tx hs working pwr */
|
| /openbmc/u-boot/board/keymile/scripts/ |
| H A D | README | 14 This file defines variables for working with rootfs via nfs for powerpc and
19 This file defines architecture specific variables for working with rootfs via
25 This file defines variables for working with rootfs inside the ram for powerpc
30 This file defines architecture specific variables for working with rootfs inside
|
| /openbmc/linux/Documentation/bpf/standardization/ |
| H A D | index.rst | 8 standardization effort with the IETF. See the `IETF BPF Working Group`_ page
9 for the working group charter, documents, and more.
18 .. _IETF BPF Working Group: https://datatracker.ietf.org/wg/bpf/about/
|
| /openbmc/linux/Documentation/power/ |
| H A D | tricks.rst | 7 If you want to trick swsusp/S3 into working, you might want to try:
14 * use ext2. At least it has working fsck. [If something seems to go
25 * due to video issues, swsusp should be easier to get working than
|
| H A D | video.rst | 26 whitelist of systems, and automatically selects working method for a
29 whitelist, please try to find a working solution, and submit whitelist
62 to life. It needs text console to be working. Do vbetool vbestate
75 the display working in graphical mode again.
87 chance of working.
89 Table of known working notebooks:
198 Known working desktop systems
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-kernel/oprofile/oprofile/ |
| H A D | 0010-oprofile-Determine-the-root-home-directory-dynamical.patch | 27 - with this option, your current working directory should be <filename>/root</filename> or a subdi…
29 + with this option, your current working directory should be <filename>~root</filename> or a subdi…
40 - with this option, your current working directory should be <code class="filename">/root</code> o…
42 + with this option, your current working directory should be <code class="filename">~root</code> o…
|
| /openbmc/linux/Documentation/admin-guide/mm/ |
| H A D | multigen_lru.rst | 71 Users can write ``N`` to ``min_ttl_ms`` to prevent the working set of
73 if this working set cannot be kept in memory. In other words, this
94 Working set estimation
96 Working set estimation measures how much memory an application needs
103 scheduler needs to estimate the working sets of the existing jobs.
160 server according to the ranking result obtained from the working set
|
| /openbmc/linux/drivers/media/platform/mediatek/mdp3/ |
| H A D | mtk-mdp3-vpu.h | 30 u32 work_addr; /* [in] working buffer address */
31 u32 work_size; /* [in] working buffer size */
41 /* synchronization protect for accessing vpu working buffer info */
|
| /openbmc/openbmc-test-automation/gui/gui_test/security_and_access_menu/ |
| H A D | test_policies_sub_menu.robot | 70 ... verify that SSH to BMC starts working after enabling SSH.
79 ... verify that SSH to BMC stops working after disabling SSH.
90 ... msg=SSH login still working after disabling SSH.
105 ... msg=IPMI command is working after disabling IPMI.
144 ... verify that SSH to BMC stops working after disabling SSH on BMC reboot.
157 ... msg=SSH login still working after disabling SSH.
176 ... msg=IPMI command is working after disabling IPMI.
|
| /openbmc/openbmc/poky/documentation/overview-manual/ |
| H A D | development-environment.rst | 83 are several ways of working in the Yocto Project environment:
264 with whatever upstream branch they are working against. They are also
306 local branches in your working Git repository on the development
309 which you are working. Once you are done with a feature or change and
316 be working on different parts of the same feature. Merging changes
424 local working area (also called a branch) that tracks a specific
442 working branch based on a branch name, your local environment matches
464 create and checkout a local working Git branch based on a tag name. When
467 The most common use is to checkout a working branch that matches a
486 checkout a local working branch based on a tag, your environment matches
[all …]
|
| /openbmc/u-boot/arch/riscv/include/asm/ |
| H A D | ptrace.h | 59 /* Helpers for working with the instruction pointer */
75 /* Helpers for working with the user stack pointer */
89 /* Helpers for working with the frame pointer */
|
| /openbmc/openbmc/poky/meta/recipes-devtools/python/ |
| H A D | python3-xmltodict_0.14.2.bb | 1 SUMMARY = "Makes working with XML feel like you are working with JSON"
|
| /openbmc/linux/arch/m68k/fpsp040/ |
| H A D | decbin.S | 124 | 1. Copy bcd value in memory for use as a working copy.
138 | ( ) a0: pointer to working bcd value
140 | (*) FP_SCR1: working copy of original bcd value
166 orl #0x40000000,(%a0) |and in working bcd
184 | ( ) a0: pointer to working bcd value
187 | ( ) FP_SCR1: working copy of original bcd value
275 | ( ) a0: pointer to working bcd value
276 | ( ) FP_SCR1: working copy of original bcd value
403 | ( ) a0: pointer to working copy of bcd
477 | ( ) a0: pointer to working bcd value
|
| /openbmc/openbmc-test-automation/redfish/managers/ |
| H A D | test_bmc_protocol_settings.robot | 59 ... msg=SSH Login and commands are working after disabling SSH.
97 ... msg=SSH Login and commands are working after disabling SSH.
145 # Check if IPMI commands starts working.
164 ... msg=IPMI commands are working after disabling IPMI.
201 ... msg=IPMI commands are working after disabling IPMI.
|
| /openbmc/linux/lib/ |
| H A D | test_linear_ranges.c | 27 * Problem is that testing working code is pointless. And if it is not
28 * working, your test must not assume it is working. You won't catch any bugs
47 * working.
51 * working. And I definitely don't want to add 500+ test cases that break when
|
| /openbmc/openbmc/poky/meta/recipes-devtools/desktop-file-utils/ |
| H A D | desktop-file-utils_0.28.bb | 1 SUMMARY = "Command line utilities for working with *.desktop files"
2 DESCRIPTION = "desktop-file-utils contains a few command line utilities for working with desktop en…
|
| /openbmc/openbmc/poky/meta/recipes-core/sysfsutils/ |
| H A D | sysfsutils_2.1.1.bb | 1 SUMMARY = "Tools for working with sysfs"
2 DESCRIPTION = "Tools for working with the sysfs virtual filesystem. The tool 'systool' can query d…
|
| /openbmc/linux/drivers/net/ethernet/netronome/nfp/nfpcore/ |
| H A D | crc32.h | 10 * crc32_posix_end() - Finalize POSIX CRC32 working state
11 * @crc: Current CRC32 working state
|
| /openbmc/linux/Documentation/driver-api/media/drivers/ |
| H A D | dvb-usb.rst | 111 first almost working version for HanfTek UMT-010
144 - first working version of the dib3000mc/p frontend driver.
194 - firmware-extraction-2.422-problem solved, driver is now working
218 - firmware loader is working
231 working.
307 working like charm now with VDR. Sometimes I even was able to record a channel
|
| /openbmc/linux/Documentation/process/ |
| H A D | 6.Followthrough.rst | 22 Working with reviewers
26 developers as they review the code. Working with reviewers can be, for
49 be working on the kernel years from now, but they understand that their
51 working toward the creation of the best kernel they can; they are not
128 patch. Now other developers working with that tree will get the patch by
138 Other times, conflict resolution will involve working with the other
|
| /openbmc/u-boot/drivers/ddr/altera/ |
| H A D | sequencer.c | 1547 * @working: If 1, look for working phase/delay, if 0, look for non-working
1550 * @work: Working window position
1551 * @work_inc: Working window increment
1554 * Find working or non-working DQS enable phase setting.
1556 static int sdr_find_phase_delay(int working, int delay, const u32 grp, in sdr_find_phase_delay() argument
1571 if (!working) in sdr_find_phase_delay()
1585 * @working: If 1, look for working phase, if 0, look for non-working phase
1587 * @work: Working window position
1591 * Find working or non-working DQS enable phase setting.
1593 static int sdr_find_phase(int working, const u32 grp, u32 *work, in sdr_find_phase() argument
[all …]
|
| /openbmc/openbmc-test-automation/bin/plug_ins/Stop/ |
| H A D | cp_stop_check | 46 + " no longer working.",
92 …P_REST_FAIL, then this function will determine whether REST commands to the target are working. If
108 print_timen("Checking to see whether %s commands are working." % interface)
153 "%s commands are working so no reason as of yet to stop the test."
|