Home
last modified time | relevance | path

Searched full:activated (Results 1 – 25 of 795) sorted by relevance

12345678910>>...32

/openbmc/phosphor-net-ipmid/command/
H A Dpayload_cmds.hpp201 uint8_t instance1:1; //!< If true, Instance 1 is activated.
202 uint8_t instance2:1; //!< If true, Instance 2 is activated.
203 uint8_t instance3:1; //!< If true, Instance 3 is activated.
204 uint8_t instance4:1; //!< If true, Instance 4 is activated.
205 uint8_t instance5:1; //!< If true, Instance 5 is activated.
206 uint8_t instance6:1; //!< If true, Instance 6 is activated.
207 uint8_t instance7:1; //!< If true, Instance 7 is activated.
208 uint8_t instance8:1; //!< If true, Instance 8 is activated.
212 uint8_t instance8:1; //!< If true, Instance 8 is activated.
213 uint8_t instance7:1; //!< If true, Instance 7 is activated.
[all …]
H A Dsession_cmds.hpp60 * This command is sent in authenticated format. When a session is activated,
62 * activated at a maximum privilege level of Callback is set to an initial
/openbmc/linux/arch/arm64/boot/dts/renesas/
H A Drzg2l-smarc.dtsi137 * SW1 should be at position 2->3 so that SER0_CTS# line is activated
138 * SW2 should be at position 2->3 so that SER0_TX line is activated
139 * SW3 should be at position 2->3 so that SER0_RX line is activated
140 * SW4 should be at position 2->3 so that SER0_RTS# line is activated
H A Drzg2lc-smarc.dtsi146 * SW1 should be at position 2->3 so that SER0_CTS# line is activated
147 * SW2 should be at position 2->3 so that SER0_TX line is activated
148 * SW3 should be at position 2->3 so that SER0_RX line is activated
149 * SW4 should be at position 2->3 so that SER0_RTS# line is activated
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Software/
H A DREADME.md128 appropriate for any element(s) being Activated.
143 3. _Ready_ - Indicating that the `Software.Version` can be activated.
145 being activated.
161 activated. RequestedApplyTime is a D-Bus property that maps to the "ApplyTime"
165 1. _Immediate_ - Indicating that the `Software.Version` needs to be activated
167 2. _OnReset_ - Indicating that the `Software.Version` needs to be activated on
206 express the relationship between two (or more) software versions activated for a
229 method once the `Version` is successfully activated.
H A DActivation.interface.yaml23 The Software.Version is invalid and unable to be activated.
30 The Software.Version is in the process of being Activated.
/openbmc/linux/Documentation/ABI/testing/
H A Dsysfs-driver-ccp73 whether the HSP TPM has been activated.
75 0: Not activated or present
76 1: Activated
/openbmc/docs/architecture/code-update/
H A Dfirmware-update-over-redfish.md155 to a system, written to flash chip 0, and activated. If another image is
156 uploaded, it will be written to flash chip 1 and activated. The first image
157 still exists in flash chip 0 and could be re-activated by the user.
164 priority 0 (highest) to ensure it is activated during the next activation
210 activated, they are given the highest priority and all other images have their
213 activated.
/openbmc/linux/drivers/ntb/hw/idt/
H A DKconfig16 First of all partitions must be activated and properly assigned to all
17 the ports with NT-functions intended to be activated (see SWPARTxCTL
/openbmc/linux/include/linux/platform_data/
H A Dlp8755.h19 *OCP : over current protect activated
20 *OVP : over voltage protect activated
/openbmc/linux/Documentation/devicetree/bindings/usb/
H A Datmel-usb.txt17 activated for the bus to be powered.
19 activated for the overcurrent detection.
71 activated for the bus to be powered.
/openbmc/linux/fs/ntfs3/
H A DKconfig22 If activated 64 bits per clusters you will be able to use 4k cluster
33 If activated you will be able to read such files correctly.
/openbmc/openbmc/meta-arm/meta-arm/recipes-bsp/trusted-firmware-a/
H A Dtrusted-firmware-a.inc53 # add MBEDTLS to our sources if activated
62 # When U-Boot support is activated BL33 is activated with u-boot.bin file
66 # When UEFI support is activated BL33 is activated with uefi.bin file
/openbmc/telemetry/src/
H A Dstate.hpp15 activated, enumerator
42 return StateEvent::activated; in set()
/openbmc/linux/drivers/gpu/drm/amd/display/amdgpu_dm/
H A Damdgpu_dm_crc.h48 /* CRC window is activated or not*/
49 bool activated; member
/openbmc/openbmc-test-automation/lib/
H A Denergy_scale_utils.robot82 Should Contain ${resp} successfully activated
86 Fail If DCMI Power Is Not Activated
87 [Documentation] Fail if DCMI power limiting is not activated.
/openbmc/u-boot/doc/
H A DREADME.VSC3316-330816 …n is 0x02 for two-wire interface. Also for crosspoint connections to be activated, 01.h value need…
41 …For crosspoint connections to be activated, 01.h value need to be written in 75.h (core configurat…
/openbmc/u-boot/drivers/virtio/
H A Dvirtio_mmio.h36 * Bitmask of features activated by the driver (guest)
41 /* Activated features set selector - Write Only */
/openbmc/linux/Documentation/ABI/obsolete/
H A Dsysfs-driver-hid-roccat-arvo40 When written, the given buttons are activated/deactivated
52 When written, the key is activated/deactivated immediately.
/openbmc/linux/Documentation/leds/
H A Dleds-lm3556.rst23 CONTROL REGISTER(0x09).Flash mode is activated by the ENABLE REGISTER(0x0A),
51 REGISTER(0x09).Torch Mode is activated by the ENABLE REGISTER(0x0A) or by the
/openbmc/linux/drivers/thunderbolt/
H A Dpath.c160 path->activated = true; in tb_path_discover()
479 if (!path->activated) { in tb_path_deactivate()
491 path->activated = false; in tb_path_deactivate()
507 if (path->activated) { in tb_path_activate()
508 tb_WARN(path->tb, "trying to activate already activated path\n"); in tb_path_activate()
582 path->activated = true; in tb_path_activate()
/openbmc/qemu/include/standard-headers/linux/
H A Dvirtio_mmio.h61 /* Bitmask of features activated by the driver (guest)
65 /* Activated features set selector - Write Only */
/openbmc/linux/include/uapi/linux/
H A Dvirtio_mmio.h61 /* Bitmask of features activated by the driver (guest)
65 /* Activated features set selector - Write Only */
/openbmc/qemu/
H A D.exrc1 "VIM settings to match QEMU coding style. They are activated by adding the
/openbmc/u-boot/doc/driver-model/
H A DREADME.txt244 The device is automatically activated ready for use by uclass_get_device().
568 methods to allow it to do some processing before the child is activated or
639 activated (except for the root device). Each bound device that was created
686 unless its predecessors (all the way up to the root device) are activated.
688 be activated.
708 devices which are regularly de/activated).
725 i. The device is marked 'activated'
729 activated and 'known' by the uclass.
733 The device is now activated and can be used. From now until it is removed
783 activated again, then the cycle starts again at step 2 above.

12345678910>>...32