Home
last modified time | relevance | path

Searched +full:three +full:- +full:state (Results 1 – 25 of 1016) sorted by relevance

12345678910>>...41

/openbmc/linux/Documentation/devicetree/bindings/mux/
H A Dadi,adg792a.txt4 - compatible : "adi,adg792a" or "adi,adg792g"
5 - #mux-control-cells : <0> if parallel (the three muxes are bound together
6 with a single mux controller controlling all three muxes), or <1> if
8 * Standard mux-controller bindings as described in mux-controller.yaml
11 - gpio-controller : if present, #gpio-cells below is required.
12 - #gpio-cells : should be <2>
13 - First cell is the GPO line number, i.e. 0 or 1
14 - Second cell is used to specify active high (0)
18 - idle-state : if present, array of states that the mux controllers will have
19 when idle. The special state MUX_IDLE_AS_IS is the default and
[all …]
/openbmc/openbmc/meta-ibm/recipes-phosphor/dbus/fan-policy/swift/
H A Dwater-cooled.yaml3 # A water cooled Swift requires a minimum of three functional fan
4 # enclosures. If the number of functional fan enclosures is below three,
7 - name: fan enclosures
13 - meta: FAN
15 - meta: FAN
17 - meta: FAN
19 - meta: FAN
22 - name: chassis state
28 - meta: CHASSISSTATE
29 path: /xyz/openbmc_project/state/chassis0
[all …]
H A Dair-cooled.yaml3 # An air cooled Swift requires a minimum of three functional fan enclosures.
4 # If the number of functional fan enclosures is below three, soft poweroff
7 - name: fan enclosures
13 - meta: FAN
15 - meta: FAN
17 - meta: FAN
19 - meta: FAN
22 - name: chassis state
28 - meta: CHASSISSTATE
29 path: /xyz/openbmc_project/state/chassis0
[all …]
/openbmc/qemu/docs/devel/
H A Dreset.rst18 ----------------
26 instantly reset an object, without keeping it in reset state, just call
34 to the initial state corresponding to the start of QEMU; this might differ
40 clean state prior to loading a snapshot. (This corresponds to a reset
43 have some non-deterministic state they want to reinitialize to a different
45 must not reinitialize on a snapshot-load reset.
48 If the machine supports waking up from a suspended state and needs to reset
49 its devices during wake-up (from the ``MachineClass::wakeup()`` method), this
51 type to differentiate the reset requested during machine wake-up from other
52 reset requests. For example, RAM content must not be lost during wake-up, and
[all …]
/openbmc/openbmc/meta-ibm/recipes-phosphor/dbus/fan-policy/witherspoon/
H A Dair-cooled.yaml3 # An air cooled Witherspoon requires a minimum of three functional fans
5 # If the number of functional fan enclosures is below three, soft poweroff
9 - name: fan enclosures
15 - meta: FAN
17 - meta: FAN
19 - meta: FAN
21 - meta: FAN
24 - name: fan rotors
30 - meta: FAN
32 - meta: FAN
[all …]
/openbmc/linux/Documentation/devicetree/bindings/phy/
H A Dphy-mapphone-mdm6600.txt4 - compatible Must be "motorola,mapphone-mdm6600"
5 - enable-gpios GPIO to enable the USB PHY
6 - power-gpios GPIO to power on the device
7 - reset-gpios GPIO to reset the device
8 - motorola,mode-gpios Two GPIOs to configure MDM6600 USB start-up mode for
10 - motorola,cmd-gpios Three GPIOs to control the power state of the MDM6600
11 - motorola,status-gpios Three GPIOs to read the power state of the MDM6600
15 usb-phy {
16 compatible = "motorola,mapphone-mdm6600";
17 enable-gpios = <&gpio3 31 GPIO_ACTIVE_LOW>;
[all …]
/openbmc/docs/designs/
H A Dbmc-boot-ready.md28 The mailing list discussion can be found [here][1]. The BMC currently has three
29 major [state][2] management interfaces in a system. The BMC, Chassis, and Host.
30 Within each state interface, the current state and requested state are tracked.
32 The [BMC][3] state object is considered `Ready` once the systemd
33 `multi-user.target` has successfully started all if its services.
35 There are three options that have been discussed to solve this issue:
37 1. D-Bus objects don't exist until the backend is prepared to handle them.
38 2. If a user tries something that system is not in proper state to handle then
40 3. If a user tries something that system is not in proper state to handle then
43 Option 1 is challenging because D-Bus interfaces provided by OpenBMC state
[all …]
/openbmc/linux/Documentation/admin-guide/mm/damon/
H A Dusage.rst1 .. SPDX-License-Identifier: GPL-2.0
9 - *DAMON user space tool.*
11 system administrators who want a just-working human-friendly interface.
12 Using this, users can use the DAMON’s major features in a human-friendly way.
16 - *sysfs interface.*
23 - *debugfs interface. (DEPRECATED!)*
28 linux-mm@kvack.org.
29 - *Kernel Space Programming Interface.*
54 # echo on > kdamonds/0/state
57 ---------------
[all …]
/openbmc/linux/lib/xz/
H A Dxz_lzma2.h5 * Igor Pavlov <https://7-zip.org/>
23 * Maximum number of position states. A position state is the lowest pb
34 * - Literal: One 8-bit byte
35 * - Match: Repeat a chunk of data at some distance
36 * - Long repeat: Multi-byte match at a recently seen distance
37 * - Short repeat: One-byte repeat at a recently seen distance
40 * either short or long repeated match, and NONLIT means any non-literal.
60 /* The lowest 7 states indicate that the previous state was a literal. */
64 static inline void lzma_state_literal(enum lzma_state *state) in lzma_state_literal() argument
66 if (*state <= STATE_SHORTREP_LIT_LIT) in lzma_state_literal()
[all …]
/openbmc/linux/Documentation/devicetree/bindings/hwmon/
H A Dadt7475.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jean Delvare <jdelvare@suse.com>
17 control up to three). They support reading a single on chip temperature
19 supports measuring up to three current external temperature sensors with
23 https://www.onsemi.com/pub/Collateral/ADT7473-D.PDF
24 https://www.onsemi.com/pub/Collateral/ADT7475-D.PDF
25 https://www.onsemi.com/pub/Collateral/ADT7476-D.PDF
26 https://www.onsemi.com/pub/Collateral/ADT7490-D.PDF
[all …]
/openbmc/phosphor-led-manager/test/
H A Dutest.cpp1 #include "led-test-map.hpp"
153 {"Three", phosphor::led::Layout::Action::On, 0, 0, in TEST_F()
189 {"Three", phosphor::led::Layout::Action::Blink, 0, 0, in TEST_F()
225 {"Three", phosphor::led::Layout::Action::Blink, 0, 0, in TEST_F()
255 {"Three", phosphor::led::Layout::Action::Blink, 0, 0, in TEST_F()
291 {"Three", phosphor::led::Layout::Action::Blink, 0, 0, in TEST_F()
321 {"Three", phosphor::led::Layout::Action::Blink, 0, 0, in TEST_F()
370 {"Three", phosphor::led::Layout::Action::Blink, 0, 0, in TEST_F()
394 // Assert Set-A in TEST_F()
410 {"Three", phosphor::led::Layout::Action::On, 0, 0, in TEST_F()
[all …]
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/State/
H A DREADME.md1 # BMC, Host, and Chassis State Management
5 The goal of the phosphor-state-manager repository is to control and track the
7 implement the BMC state interfaces, and some, when creating servers will do the
8 Host and Chassis state interfaces. These interfaces will be the mechanism by
9 which you determine the state of their corresponding instances, as well as
14 There are three states to track and control on a BMC based server. The states
16 `/xyz/openbmc_project/state/`+`/bmcX,/hostY,/chassisZ` where X,Y,Z are the
17 instances (in most cases 0). For all three states, the software tracks a current
18 state, and a requested transition.
26 request the host be in a (Off), (On), or (Reboot) state. More details on
[all …]
/openbmc/bmcweb/redfish-core/schema/dmtf/csdl/
H A DCircuit_v1.xml1 <?xml version="1.0" encoding="UTF-8"?>
2 <!---->
3 <!--################################################################################ -->
4 <!--# Redfish Schema: Circuit v1.8.1 -->
5 <!--# -->
6 <!--# For a detailed change log, see the README file contained in the DSP8010 bundle, -->
7 <!--# available at http://www.dmtf.org/standards/redfish -->
8 <!--# Copyright 2014-2024 DMTF. -->
9 <!--# For the full DMTF copyright policy, see http://www.dmtf.org/about/policies/copyright -->
10 <!--################################################################################ -->
[all …]
/openbmc/openbmc/meta-inventec/conf/machine/include/
H A Dinventec.inc2 obmc-phosphor-fan-mgmt \
3 obmc-phosphor-chassis-mgmt \
4 obmc-phosphor-flash-mgmt \
5 obmc-host-ipmi \
6 obmc-host-state-mgmt \
7 obmc-chassis-state-mgmt \
8 obmc-bmc-state-mgmt \
10 # since we use x86-power-control service, we don't need below three services
11 VIRTUAL-RUNTIME_obmc-host-state-manager = "x86-power-control"
12 VIRTUAL-RUNTIME_obmc-chassis-state-manager = "x86-power-control"
[all …]
/openbmc/linux/lib/zlib_inflate/
H A Dinffast.c1 /* inffast.c -- fast decoding
2 * Copyright (C) 1995-2004 Mark Adler
33 available, an end-of-block is encountered, or a data error is encountered.
40 state->mode == LEN
41 strm->avail_in >= 6
42 strm->avail_out >= 258
43 start >= strm->avail_out
44 state->bits < 8
46 On return, state->mode is one of:
48 LEN -- ran out of enough output space or enough available input
[all …]
/openbmc/linux/arch/m68k/ifpsp060/
H A Dfskeleton.S3 |M68000 Hi-Performance Microprocessor Division
5 |Production Release P1.00 -- October 10, 1994
32 | (1) example "Call-out"s
34 | (3) example "Call-out" table
40 | (1) EXAMPLE CALL-OUTS #
58 | This is the main exit point for the 68060 Floating-Point
60 | routine. The operating system can do system dependent clean-up or
73 | stack frame. The FP state frame holds the EXCEPTIONAL OPERAND.
80 fsave -(%sp)
92 | stack frame. The FP state frame holds the EXCEPTIONAL OPERAND.
[all …]
/openbmc/linux/Documentation/trace/rv/
H A Dda_monitor_instrumentation.rst51 --------------------------
53 The first three functions are the starting point of the callback *handler
54 functions* for each of the three events from the wip model. The developer
81 Initially, the *model* is placed in the initial state. However, the *system*
82 might or might not be in the initial state. The monitor cannot start
83 processing events until it knows that the system has reached the initial state.
84 Otherwise, the monitor and the system could be out-of-sync.
87 and the model are expected to return to the initial state after the
113 ----------------------------
136 -----------------------
H A Dda_monitor_synthesis.rst16 of the monitor (per-cpu monitor, per-task monitor, and so on), the helper
21 Linux +----- RV Monitor ----------------------------------+ Formal
23 +-------------------+ +----------------+ +-----------------+
25 | Tracing | -> | Instance(s) | <- | Model |
27 +-------------------+ +----------------+ +-----------------+
30 | +----------+ |
32 | +--+--+--+-+ |
34 | | | +-> trace output ? |
35 +------------------------|--|----------------------+
36 | +----> panic ?
[all …]
/openbmc/u-boot/lib/zlib/
H A Dinffast.c1 /* inffast.c -- fast decoding
2 * Copyright (C) 1995-2004 Mark Adler
6 /* U-Boot: we already included these
15 /* Allow machine dependent optimization for post-increment or pre-increment.
17 Pre-increment preferred for:
18 - PowerPC G3 (Adler)
19 - MIPS R5000 (Randers-Pehrson)
20 Post-increment preferred for:
21 - none
23 - Pentium III (Anderson)
[all …]
/openbmc/linux/Documentation/hwmon/
H A Dw83792d.rst10 Addresses scanned: I2C 0x2c - 0x2f
19 -----------------
35 -----------
40 internal state that allows no clean access (Bank with ID register is not
42 parameter; this will put it into a more well-behaved state first.
44 The driver implements three temperature sensors, seven fan rotation speed
48 The driver also implements up to seven fan control outputs: pwm1-7. Pwm1-7
53 Automatic fan control mode is possible only for fan1-fan3.
116 ----------------
118 - This driver is only for Winbond W83792D C version device, there
[all …]
/openbmc/linux/tools/include/uapi/sound/
H A Dasound.h1 /* SPDX-License-Identifier: GPL-2.0+ WITH Linux-syscall-note */
3 * Advanced Linux Sound Architecture - ALSA - Driver
4 * Copyright (c) 1994-2003 by Jaroslav Kysela <perex@perex.cz>,
5 * Abramo Bagnara <abramo@alsa-project.org>
54 * CEA-861 Audio InfoFrame. Used in HDMI and DisplayPort *
63 unsigned char db5_dminh_lsv; /* downmix inhibit & level-shit values */
68 * Section for driver hardware dependent interface - /dev/snd/hw? *
91 SNDRV_HWDEP_IFACE_HDA, /* HD-audio */
118 unsigned int version; /* R: driver-specific version */
119 unsigned char id[32]; /* R: driver-specific ID string */
[all …]
/openbmc/linux/include/uapi/sound/
H A Dasound.h1 /* SPDX-License-Identifier: GPL-2.0+ WITH Linux-syscall-note */
3 * Advanced Linux Sound Architecture - ALSA - Driver
4 * Copyright (c) 1994-2003 by Jaroslav Kysela <perex@perex.cz>,
5 * Abramo Bagnara <abramo@alsa-project.org>
54 * CEA-861 Audio InfoFrame. Used in HDMI and DisplayPort *
63 unsigned char db5_dminh_lsv; /* downmix inhibit & level-shit values */
68 * Section for driver hardware dependent interface - /dev/snd/hw? *
91 SNDRV_HWDEP_IFACE_HDA, /* HD-audio */
118 unsigned int version; /* R: driver-specific version */
119 unsigned char id[32]; /* R: driver-specific ID string */
[all …]
/openbmc/linux/Documentation/filesystems/
H A Dgfs2-glocks.rst1 .. SPDX-License-Identifier: GPL-2.0
7 This documents the basic principles of the glock state machine
11 1. A spinlock (gl_lockref.lock) which protects the internal state such
13 2. A non-blocking bit lock, GLF_LOCK, which is used to prevent other
25 There are three lock states that users of the glock layer can request,
61 go_xmote_th Called before remote state change (e.g. to sync dirty data)
62 go_xmote_bh Called after remote state change (e.g. to refill cache)
63 go_inval Called if remote state change requires invalidating the cache
110 Note that go_dump will only be called if the glock's state
121 5. Transaction glock (via gfs2_trans_begin) for non-read operations
[all …]
/openbmc/linux/drivers/input/mouse/
H A Dvsxxxaa.c1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * Driver for DEC VSXXX-AA mouse (hockey-puck mouse, ball or two rollers)
4 * DEC VSXXX-GA mouse (rectangular mouse, with ball)
5 * DEC VSXXX-AB tablet (digitizer with hair cross or stylus)
7 * Copyright (C) 2003-2004 by Jan-Benedict Glaw <jbglaw@lug-owl.de>
24 * supply at +5V and -12V.
30 * | 4 --- 3 |
32 * -------
35 * 1 (GND) 5 7 -
36 * 2 (RxD) 2 3 -
[all …]
/openbmc/linux/Documentation/w1/slaves/
H A Dw1_ds2413.rst7 * Maxim DS2413 1-Wire Dual Channel Addressable Switch
18 -----------
20 The DS2413 chip has two open-drain outputs (PIO A and PIO B).
21 Support is provided through the sysfs files "output" and "state".
23 Reading state
24 -------------
25 The "state" file provides one-byte value which is in the same format as for
29 Bit 0: PIOA Pin State
30 Bit 1: PIOA Output Latch State
31 Bit 2: PIOB Pin State
[all …]

12345678910>>...41