| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/User/ |
| H A D | TOTPAuthenticator.interface.yaml | 2 This interface defines methods and properties required for Time-based
3 One-time Password (TOTP) multi-factor authentication at user level to
4 support multi-factor authentication secret key setup for each user. This
9 - name: CreateSecretKey
11 This method setup Time-based One-time Password (TOTP) authenticator
15 - name: SecretKey
21 - xyz.openbmc_project.Common.Error.UnsupportedRequest
22 - xyz.openbmc_project.Common.Error.NotAllowed
24 - name: VerifyOTP
26 This method verifies OTP with Time-based One-time Password
[all …]
|
| /openbmc/linux/Documentation/admin-guide/pm/ |
| H A D | cpuidle.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 CPU Idle Time Management
27 CPU idle time management is an energy-efficiency feature concerned about using
31 ------------
33 CPU idle time management operates on CPUs as seen by the *CPU scheduler* (that
37 software as individual single-core processors. In other words, a CPU is an
38 entity which appears to be fetching instructions that belong to one sequence
42 First, if the whole processor can only follow one sequence of instructions (one
43 program) at a time, it is a CPU. In that case, if the hardware is asked to
46 Second, if the processor is multi-core, each core in it is able to follow at
[all …]
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/jaketown/ |
| H A D | uncore-interconnect.json | 147 "BriefDescription": "BL Ingress Occupancy - DRS",
169 "BriefDescription": "BL Ingress Occupancy - NCB",
191 "BriefDescription": "BL Ingress Occupancy - NCS",
228 …ddition to the source queue. Note the special filtering equation. We do OR-reduction on the requ…
237 …ddition to the source queue. Note the special filtering equation. We do OR-reduction on the requ…
246 …ddition to the source queue. Note the special filtering equation. We do OR-reduction on the requ…
295 …er of cycles when there are pending write ACK's in the switch but the switch->IRP pipeline is not …
315 "BriefDescription": "Direct 2 Core Spawning; Spawn Failure - Egress Credits",
324 "BriefDescription": "Direct 2 Core Spawning; Spawn Failure - Egress and RBT",
333 "BriefDescription": "Direct 2 Core Spawning; Spawn Failure - RBT Not Set",
[all …]
|
| H A D | uncore-memory.json | 7 …page on the DRAM devices so that it can be read or written to with a CAS. One can calculate the n…
11 … "BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; All DRAM WR_CAS (w/ and w/out auto-pre)",
27 … "BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; All DRAM RD_CAS (w/ and w/out auto-pre)",
51 …"BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; DRAM WR_CAS (w/ and w/out auto-pre) in Read…
59 …"BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; DRAM WR_CAS (w/ and w/out auto-pre) in Writ…
70 "PublicDescription": "Uncore Fixed Counter - uclks",
104 …ounter is only useful with ECC DRAM devices. This count will increment one time for each correcti…
112 …ected by a filter) on the given channel. Major modea are channel-wide, and not a per-rank (or di…
121 …ected by a filter) on the given channel. Major modea are channel-wide, and not a per-rank (or di…
130 …ected by a filter) on the given channel. Major modea are channel-wide, and not a per-rank (or di…
[all …]
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | debugfs-scmi-raw | 7 in little-endian binary format to have it sent to the configured
11 Each write to the entry causes one command request to be built
12 and sent while the replies are read back one message at time
22 in little-endian binary format to have it sent to the configured
29 Each write to the entry causes one command request to be built
30 and sent while the replies are read back one message at time
38 Description: SCMI Raw message errors facility; any kind of timed-out or
41 Each read gives back one message at time (receiving an EOF at
52 Each read gives back one message at time (receiving an EOF at
65 different test-run.
[all …]
|
| /openbmc/linux/Documentation/driver-api/ |
| H A D | ptp.rst | 1 .. SPDX-License-Identifier: GPL-2.0
18 - Set time
19 - Get time
20 - Shift the clock by a given offset atomically
21 - Adjust clock frequency
24 - Time stamp external events
25 - Period output signals configurable from user space
26 - Low Pass Filter (LPF) access from user space
27 - Synchronization of the Linux system time via the PPS subsystem
36 driver of asynchronous events (alarms and external time stamps) via
[all …]
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | rtc.rst | 2 Real Time Clock (RTC) Drivers for Linux
5 When Linux developers talk about a "Real Time Clock", they usually mean
6 something that tracks wall clock time and is battery backed so that it
8 the local time zone or daylight savings time -- unless they dual boot
9 with MS-Windows -- but will instead be set to Coordinated Universal Time
10 (UTC, formerly "Greenwich Mean Time").
12 The newest non-PC hardware tends to just count seconds, like the time(2)
13 system call reports, but RTCs also very commonly represent time using
14 the Gregorian calendar and 24 hour time, as reported by gmtime(3).
16 Linux has two largely-compatible userspace RTC API families you may
[all …]
|
| /openbmc/linux/Documentation/arch/ia64/ |
| H A D | efirtc.rst | 2 EFI Real Time Clock driver
13 the IA-64 platform.
16 to get access to the Time Service offered by EFI version 0.92.
18 EFI provides 4 calls one can make once the OS is booted: GetTime(),
27 at first, the time of day service. This is required in order to access, in a
29 to initialize the system view of the time during boot.
31 Because we wanted to minimize the impact on existing user-level apps using
32 the CMOS clock, we decided to expose an API that was very similar to the one
38 EFI uses a slightly different way of representing the time, noticeably
39 the reference date is different. Year is the using the full 4-digit format.
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | ManagerAccount.v1_13_0.json | 4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2024 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
40 "description": "The available OEM-specific actions for this resource.",
41 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
66 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
82 "format": "uri-reference",
95 …"description": "This action clears the secret key for Time-based One-Time Password (TOTP) multi-fa…
96 …"This action shall clear the secret key for RFC6238-defined Time-based One-Time Password (TOTP) mu…
99 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
| H A D | ManagerAccount.v1_13_0.json | 4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2024 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
40 "description": "The available OEM-specific actions for this resource.",
41 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
66 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
82 "format": "uri-reference",
95 …"description": "This action clears the secret key for Time-based One-Time Password (TOTP) multi-fa…
96 …"This action shall clear the secret key for RFC6238-defined Time-based One-Time Password (TOTP) mu…
99 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
[all …]
|
| /openbmc/linux/drivers/net/wireless/intel/iwlwifi/fw/api/ |
| H A D | binding.h | 1 /* SPDX-License-Identifier: GPL-2.0 OR BSD-3-Clause */
3 * Copyright (C) 2012-2014, 2020, 2022 Intel Corporation
4 * Copyright (C) 2013-2015 Intel Mobile Communications GmbH
5 * Copyright (C) 2016-2017 Intel Deutschland GmbH
17 * struct iwl_binding_cmd_v1 - configuring bindings
37 * struct iwl_binding_cmd - configuring bindings
66 * struct iwl_time_quota_data_v1 - configuration of time quota per binding
69 * @quota: absolute time quota in TU. The scheduler will try to divide the
70 * remainig quota (after Time Events) according to this quota.
80 * struct iwl_time_quota_cmd - configuration of time quota between bindings
[all …]
|
| H A D | dbg-tlv.h | 1 /* SPDX-License-Identifier: GPL-2.0 OR BSD-3-Clause */
3 * Copyright (C) 2018-2022 Intel Corporation
34 * struct iwl_fw_ini_header - Common Header for all ini debug TLV's structures
37 * @domain: domain of the TLV. One of &enum iwl_fw_ini_dbg_domain
46 * struct iwl_fw_ini_region_dev_addr - Configuration to read device addresses
57 * struct iwl_fw_ini_region_fifos - Configuration to read Tx/Rx fifos
70 * struct iwl_fw_ini_region_err_table - error table region data
87 * struct iwl_fw_ini_region_special_device_memory - special device memory
106 * struct iwl_fw_ini_region_internal_buffer - internal buffer region data
110 * @alloc_id: allocation id one of &enum iwl_fw_ini_allocation_id
[all …]
|
| /openbmc/linux/Documentation/leds/ |
| H A D | ledtrig-transient.rst | 6 a one shot timer. The current support allows for setting two timers, one for
8 to be off. The delay_on value specifies the time period an LED should stay
11 gets deactivated. There is no provision for one time activation to implement
15 Without one shot timer interface, user space can still use timer trigger to
20 Transient trigger addresses the need for one shot timer activation. The
36 that are active at the time driver gets suspended, continue to run, without
56 non-transient state. When driver gets suspended, irrespective of the transient
71 - duration allows setting timer value in msecs. The initial value is 0.
72 - activate allows activating and deactivating the timer specified by
75 - state allows user to specify a transient state to be held for the specified
[all …]
|
| /openbmc/openbmc-test-automation/ffdc/lib/ |
| H A D | telnet_utility.py | 7 import time
25 read_timeout New read timeout value to override default one
44 self.tnclient.write(self.username.encode("utf-8") + b"\n")
49 self.tnclient.write(self.password.encode("utf-8") + b"\n")
88 # the telnet object might not exist yet, so ignore this one
101 # Wait time for command execution before reading the output.
102 # Use user input wait time for command execution if one exists.
112 # Do at least one non-blocking read.
118 self.tnclient.write(cmd.encode("utf-8") + b"\n")
119 time.sleep(execution_time)
[all …]
|
| /openbmc/linux/Documentation/driver-api/usb/ |
| H A D | usb.rst | 1 .. _usb-hostside-api:
4 The Linux-USB Host Side API
18 That master/slave asymmetry was designed-in for a number of reasons, one
22 distributed auto-configuration since the pre-designated master node
37 USB Host-Side API Model
40 Host-side drivers for USB devices talk to the "usbcore" APIs. There are
41 two. One is intended for *general-purpose* drivers (exposed through
49 - USB supports four kinds of data transfers (control, bulk, interrupt,
54 - The device description model includes one or more "configurations"
55 per device, only one of which is active at a time. Devices are supposed
[all …]
|
| /openbmc/linux/include/xen/interface/ |
| H A D | vcpu.h | 1 /* SPDX-License-Identifier: MIT */
18 * @extra_args == Operation-specific extra arguments (NULL if none).
23 * newly-initialised VCPU will not run until it is brought up by VCPUOP_up.
37 * Bring down a VCPU (i.e., make it non-runnable).
41 * idea to ensure that the VCPU has entered a non-critical loop before
56 * Return information about the state and running time of a VCPU.
63 /* When was current state entered (system time, ns)? */
72 * Time spent in each RUNSTATE_* (ns). The sum of these times is
73 * guaranteed not to drift from system time.
75 uint64_t time[4]; member
[all …]
|
| /openbmc/u-boot/doc/ |
| H A D | README.i2c | 4 While I2C supports multi-master buses this is difficult to get right.
6 Clock-stretching and the arbitrary time that an I2C transaction can take
8 When one or more masters can be reset independently part-way through a
11 U-Boot provides a scheme based on two 'claim' GPIOs, one driven by the
12 AP (Application Processor, meaning the main CPU) and one driven by the EC
18 Since U-Boot runs on the AP, the terminology used is 'our' claim GPIO,
23 i2c-arb-gpio-challenge for the implementation.
28 - AP_CLAIM: output from AP, signalling to the EC that the AP wants the bus
29 - EC_CLAIM: output from EC, signalling to the AP that the EC wants the bus
38 2. Waits a little bit for the other side to notice (slew time)
[all …]
|
| /openbmc/qemu/include/hw/xen/interface/ |
| H A D | vcpu.h | 1 /* SPDX-License-Identifier: MIT */
20 * @extra_args == Operation-specific extra arguments (NULL if none).
25 * newly-initialised VCPU will not run until it is brought up by VCPUOP_up.
41 * Bring down a VCPU (i.e., make it non-runnable).
45 * idea to ensure that the VCPU has entered a non-critical loop before
60 * Return information about the state and running time of a VCPU.
67 /* When was current state entered (system time, ns)? */
76 * Time spent in each RUNSTATE_* (ns). The sum of these times is
77 * guaranteed not to drift from system time.
79 uint64_t time[4]; member
[all …]
|
| /openbmc/linux/Documentation/process/ |
| H A D | stable-api-nonsense.rst | 8 Greg Kroah-Hartman <greg@kroah.com>
18 The kernel to userspace interface is the one that application programs use,
19 the syscall interface. That interface is **very** stable over time, and
22 That interface is the one that users and application programmers can count
27 -----------------
38 -----
41 to worry about the in-kernel interfaces changing. For the majority of
59 -----------------------
64 - Depending on the version of the C compiler you use, different kernel
71 - Depending on what kernel build options you select, a wide range of
[all …]
|
| /openbmc/openbmc-test-automation/ipmi/ |
| H A D | test_ipmi_sel_time.robot | 3 Documentation Module to test IPMI SEL Time functionality.
4 ... Pre-requisite Condition : Client Machine and BMC should be in
10 ... Test the Set/Get SEL Time functionality and compare the result against
13 ... Set the Time Sync Mode from NTP to Manual to Set SEL Time.
14 ... Time Sync Mode change performed via REDFISH URI.
15 ... Performs the change in Time Sync Mode with Test Setup and Teardown Execution
18 ... NETWORK_RESTART_TIME added for Set SEL Time and Add SEL Entry as the corresponding
21 ... Current SEL time identified via BMC Native command (date) and perform SEL Time ope…
23 ... Script Verifies SEL Time for various scenarios such as,
24 ... Get current time from BMC and add future year and compare against BMC native comma…
[all …]
|
| /openbmc/linux/drivers/cpuidle/governors/ |
| H A D | teo.c | 1 // SPDX-License-Identifier: GPL-2.0
6 * Copyright (C) 2018 - 2021 Intel Corporation
9 * Util-awareness mechanism:
15 * DOC: teo-description
22 * idle state with target residency within the (known) time till the closest
27 * Of course, non-timer wakeup sources are more important in some use cases
28 * which can be covered by taking a few most recent idle time intervals of the
50 * They are updated every time before selecting an idle state for the given CPU
51 * in accordance with what happened last time.
55 * same bin (that is, the CPU appears to wake up "on time" relative to the sleep
[all …]
|
| /openbmc/linux/Documentation/timers/ |
| H A D | no_hz.rst | 2 NO_HZ: Reducing Scheduling-Clock Ticks
7 reduce the number of scheduling-clock interrupts, thereby improving energy
9 some types of computationally intensive high-performance computing (HPC)
10 applications and for real-time applications.
12 There are three main ways of managing scheduling-clock interrupts
13 (also known as "scheduling-clock ticks" or simply "ticks"):
15 1. Never omit scheduling-clock ticks (CONFIG_HZ_PERIODIC=y or
16 CONFIG_NO_HZ=n for older kernels). You normally will -not-
19 2. Omit scheduling-clock ticks on idle CPUs (CONFIG_NO_HZ_IDLE=y or
23 3. Omit scheduling-clock ticks on CPUs that are either idle or that
[all …]
|
| /openbmc/linux/Documentation/driver-api/pm/ |
| H A D | cpuidle.rst | 1 .. SPDX-License-Identifier: GPL-2.0
5 CPU Idle Time Management
13 CPU Idle Time Management Subsystem
16 Every time one of the logical CPUs in the system (the entities that appear to
26 situation in principle, so it may be necessary to find the most suitable one
28 particular idle state. That is the role of the CPU idle time management
40 CPU Idle Time Governors
43 A CPU idle time (``CPUIdle``) governor is a bundle of policy code invoked when
44 one of the logical CPUs in the system turns out to be idle. Its role is to
61 only one in the list (that is, the list was empty before) or the value of its
[all …]
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | quota.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 of used inodes there are actually two limits. The first one is called softlimit
11 and the second one hardlimit. A user can never exceed a hardlimit for any
13 softlimit but only for limited period of time. This period is called "grace
14 period" or "grace time". When grace time is over, user is not able to allocate
17 Quota limits (and amount of grace time) are set independently for each
20 For more details about quota design, see the documentation in quota-tools package
25 When user exceeds a softlimit, runs out of grace time or reaches hardlimit,
40 Currently, the interface supports only one message type QUOTA_NL_C_WARNING.
46 - type of quota being exceeded (one of USRQUOTA, GRPQUOTA)
[all …]
|
| /openbmc/phosphor-state-manager/ |
| H A D | settings.cpp | 5 #include <phosphor-logging/elog-errors.hpp>
6 #include <phosphor-logging/lg2.hpp>
64 * Interface. A persistent user setting and a one-time in Objects()
65 * setting which is only valid for one boot of the system. in Objects()
66 * The one-time setting will have "one_time" in its in Objects()
81 * Interface. A persistent user setting and a one-time in Objects()
82 * setting which is only valid for one boot of the system. in Objects()
83 * The one-time setting will have "one_time" in its in Objects()
128 return result.begin()->first; in service()
|