| /openbmc/qemu/migration/ |
| H A D | options.c | 44 /* Define default autoconverge cpu throttle migration parameters */
75 * Parameters for self_announce_delay giving a stream of RARP/ARP
107 /* Migration parameters */
109 parameters.throttle_trigger_threshold,
112 parameters.cpu_throttle_initial,
115 parameters.cpu_throttle_increment,
118 parameters.cpu_throttle_tailslow, false),
120 parameters.max_bandwidth, MAX_THROTTLE),
122 parameters.avail_switchover_bandwidth, 0),
124 parameters.downtime_limit,
[all …]
|
| /openbmc/docs/designs/oem/ibm/ |
| H A D | system-power-mode.md | 14 save parameters. This design is only applicable to POWER processors.
24 parameters.
33 the OCC state changes to ACTIVE or the customer updates these new parameters at
46 A proposal for adding Idle Power Saving parameters was submitted to the Redfish
49 Customer Settable Idle Power Save Parameters:
75 parameters. These commands are defined in the OCC Interface Spec:
79 parameters for the system. If the customer has not yet set any of these
80 parameters, these default values will be used. If/when the customer does set any
84 The customer requested PowerMode and Idle Power Saver parameters will be stored
91 - Using hardcoded power mode and Idle Power Save parameters (no flexibility to
[all …]
|
| /openbmc/qemu/docs/interop/ |
| H A D | barrier.rst | 33 Parameters:
47 Parameters:
63 Parameters:
78 Parameters:
88 Parameters:
98 Parameters:
119 Parameters:
133 Parameters:
149 Parameters:
161 Parameters:
[all …]
|
| /openbmc/phosphor-fan-presence/control/example/ |
| H A D | events.yaml | 13 # parameters:
14 # [Ordered list of required parameters for the match string function]
19 # parameters:
20 # [Ordered list of required parameters for the signal function]
26 # parameters:
32 # parameters:
33 # [Ordered list of required parameters for the handler function]
39 # parameters:
40 # [Ordered list of required parameters for the precondition function]
45 # parameters:
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/com/ibm/VPD/ |
| H A D | Manager.interface.yaml | 7 parameters:
36 parameters.
37 parameters:
48 Parameters in required format to write the keyword's value.
61 parameters:
71 Parameters in required format to write the keyword's value.
83 Method to read a single keyword's value based on the input parameters.
84 parameters:
93 Parameters in required format to read the keyword's value.
108 parameters:
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | ActionInfo.v1_4_2.json | 9 …parameters and other information for a Redfish action. Supported parameters can differ among vend…
10 …parameters and other information for a Redfish action on a target within a Redfish implementation.…
62 "Parameters": { object
63 … "description": "The list of parameters included in the specified Redfish action.",
65 "$ref": "#/definitions/Parameters"
67 …"longDescription": "This property shall list the parameters included in the specified Redfish acti…
100 "Parameters": { object
127 …ray member. This property shall only be present for numeric parameters or string parameters that …
134 …lowable values for each array member. This property shall only be present for string parameters.",
169 …ervice supports for this parameter. This property shall not be present for non-array parameters.",
[all …]
|
| H A D | JobDocument.v1_0_0.json | 52 …escription": "The `JobDocument` schema describes the template for a job with a set of parameters.",
149 …"description": "The metadata for each of the parameters supported by this job document for the `Su…
153 …escription": "This property shall contain the metadata for each of the parameters supported by thi…
233 …"description": "An object containing a set of parameters for submitting a new job based on a job d…
234 …"longDescription": "This type shall contain a set of parameters for submitting a new job based on …
284 …cification. This property shall only be present for numeric parameters or string parameters that …
290 … allowable values for this parameter. This property shall only be present for string parameters.",
326 … this service supports. This property shall not be present for non-integer or number parameters.",
332 … this service supports. This property shall not be present for non-integer or number parameters.",
363 …iption": "Creates a new job based on the contents of this job document and additional parameters.",
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
| H A D | ActionInfo.v1_4_2.json | 9 …parameters and other information for a Redfish action. Supported parameters can differ among vend…
10 …parameters and other information for a Redfish action on a target within a Redfish implementation.…
62 "Parameters": { object
63 … "description": "The list of parameters included in the specified Redfish action.",
65 "$ref": "#/definitions/Parameters"
67 …"longDescription": "This property shall list the parameters included in the specified Redfish acti…
100 "Parameters": { object
127 …ray member. This property shall only be present for numeric parameters or string parameters that …
134 …lowable values for each array member. This property shall only be present for string parameters.",
169 …ervice supports for this parameter. This property shall not be present for non-array parameters.",
[all …]
|
| /openbmc/openbmc/meta-ibm/meta-romulus/recipes-phosphor/fans/phosphor-fan-control-events-config/ |
| H A D | events.yaml | 99 parameters:
103 parameters:
106 parameters:
114 parameters:
123 parameters:
132 parameters:
140 parameters:
145 parameters:
151 parameters:
156 parameters:
[all …]
|
| /openbmc/qemu/include/hw/xen/interface/ |
| H A D | event_channel.h | 77 /* IN parameters */
79 /* OUT parameters */
105 /* IN parameters. */
108 /* OUT parameters. */
126 /* IN parameters. */
129 /* OUT parameters. */
141 /* IN parameters. */
145 /* OUT parameters. */
158 /* OUT parameters. */
169 /* IN parameters. */
[all …]
|
| /openbmc/bmcweb/test/redfish-core/lib/ |
| H A D | system_test.cpp | 46 nlohmann::json::array_t parameters; in TEST() local
61 parameters.emplace_back(std::move(parameter)); in TEST()
63 EXPECT_EQ(response->res.jsonValue["Parameters"], parameters); in TEST()
79 nlohmann::json::array_t parameters; in TEST() local
93 parameters.emplace_back(std::move(parameter)); in TEST()
95 EXPECT_EQ(response->res.jsonValue["Parameters"], parameters); in TEST()
112 nlohmann::json::array_t parameters; in TEST() local
127 parameters.emplace_back(std::move(parameter)); in TEST()
129 EXPECT_EQ(response->res.jsonValue["Parameters"], parameters); in TEST()
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/csdl/ |
| H A D | ActionInfo_v1.xml | 34 …parameters and other information for a Redfish action. Supported parameters can differ among vend…
35 …parameters and other information for a Redfish action on a target within a Redfish implementation.…
53 <ComplexType Name="Parameters" Abstract="true">
65 … <Property Name="Parameters" Type="Collection(ActionInfo.v1_0_0.Parameters)" Nullable="false">
66 …<Annotation Term="OData.Description" String="The list of parameters included in the specified Redf…
67 …<Annotation Term="OData.LongDescription" String="This property shall list the parameters included …
71 <ComplexType Name="Parameters" BaseType="ActionInfo.Parameters">
91 …perty shall be required for parameters with a data type of `Object` or `ObjectArray`, and shall no…
163 …tring="This version was created to clarify the behavior of AllowableValues for array parameters."/>
179 <ComplexType Name="Parameters" BaseType="ActionInfo.v1_0_0.Parameters">
[all …]
|
| H A D | JobDocument_v1.xml | 42 …ion" String="The `JobDocument` schema describes the template for a job with a set of parameters."/>
67 … String="Creates a new job based on the contents of this job document and additional parameters."/>
68 …reate a new `Job` resource based on the contents of this job document and additional parameters."/>
74 <Parameter Name="Parameters" Type="JobDocument.v1_0_0.Parameter" Nullable="false">
75 …<Annotation Term="OData.Description" String="The list of parameters for the new job that are speci…
76 …ain the list of parameters for the new job that are specific to this job document. Services shall…
87 …parameters should be hidden from view after the job has been created. If `true`, responses do not…
88 …parameters should be hidden from view after the job has been created. If `true`, responses shall …
143 …<Annotation Term="OData.Description" String="The metadata for each of the parameters supported by …
144 …tion" String="This property shall contain the metadata for each of the parameters supported by thi…
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/installed/ |
| H A D | ActionInfo_v1.xml | 34 …parameters and other information for a Redfish action. Supported parameters can differ among vend…
35 …parameters and other information for a Redfish action on a target within a Redfish implementation.…
53 <ComplexType Name="Parameters" Abstract="true">
65 … <Property Name="Parameters" Type="Collection(ActionInfo.v1_0_0.Parameters)" Nullable="false">
66 …<Annotation Term="OData.Description" String="The list of parameters included in the specified Redf…
67 …<Annotation Term="OData.LongDescription" String="This property shall list the parameters included …
71 <ComplexType Name="Parameters" BaseType="ActionInfo.Parameters">
91 …perty shall be required for parameters with a data type of `Object` or `ObjectArray`, and shall no…
163 …tring="This version was created to clarify the behavior of AllowableValues for array parameters."/>
179 <ComplexType Name="Parameters" BaseType="ActionInfo.v1_0_0.Parameters">
[all …]
|
| /openbmc/u-boot/arch/x86/include/asm/arch-quark/ |
| H A D | mrc.h | 91 BM_FAST = 2, /* restore timing parameters */
101 * Memory Reference Code parameters
104 * - input parameters like boot mode and DRAM parameters
105 * - context parameters for MRC internal state
106 * - output parameters like initialization result and memory size
109 /* Input parameters */
111 /* DRAM parameters */
137 /* Internally used context parameters */
148 /* Output parameters */
182 * @mrc_params: parameters for MRC
|
| /openbmc/x86-power-control/src/ |
| H A D | power_control.hpp | 24 * This manager supposed to store runtime parameters that supposed to be
27 * @note: currently only string parameters supported
52 * @brief Initialize configuration parameters.
72 * @brief Check if all required algorithms parameters are set
74 * Call this after set any of Power Restore algorithm parameters. Once all
75 * parameters are set this will run invoke() function.
81 * Take Power Restore actions according to Policy and other parameters.
97 * List of all supported parameters
|
| /openbmc/openbmc/meta-ibm/recipes-phosphor/fans/phosphor-fan-control-events-config/witherspoon/ |
| H A D | events.yaml | 149 parameters:
153 parameters:
156 parameters:
159 parameters:
167 parameters:
176 parameters:
185 parameters:
192 parameters:
200 parameters:
205 parameters:
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/org/open_power/Logging/ |
| H A D | PEL.interface.yaml | 7 parameters:
24 parameters:
40 parameters:
51 parameters:
69 parameters:
123 parameters:
140 parameters:
156 parameters:
|
| /openbmc/sdbusplus/tools/sdbusplus/templates/ |
| H A D | method.client.hpp.mako | 3 % if len(method.parameters) != 0:
5 % for p in method.parameters:
18 % if len(method.parameters) != 0:
26 % if len(method.parameters) != 0:
|
| H A D | method.md.mako | 5 % if len(method.parameters) or len(method.returns):
6 ${"####"} Parameters and Returns
9 % for p in method.parameters:
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Smbios/ |
| H A D | MDR_V2.interface.yaml | 7 parameters:
23 parameters:
39 parameters:
82 parameters:
114 parameters:
139 parameters:
|
| /openbmc/u-boot/drivers/net/fsl-mc/ |
| H A D | dprc.c | 30 /* retrieve response parameters */ in dprc_get_container_id()
54 /* retrieve response parameters */ in dprc_open()
96 /* retrieve response parameters */ in dprc_create_container()
155 /* retrieve response parameters */ in dprc_get_attributes()
179 /* retrieve response parameters */ in dprc_get_obj_count()
205 /* retrieve response parameters */ in dprc_get_obj()
233 /* retrieve response parameters */ in dprc_get_res_count()
259 /* retrieve response parameters */ in dprc_get_res_ids()
287 /* retrieve response parameters */ in dprc_get_obj_region()
350 /* retrieve response parameters */ in dprc_get_connection()
[all …]
|
| /openbmc/openbmc-test-automation/lib/ |
| H A D | resource.robot | 77 # IPMI SOL console output types/parameters to verify.
81 # PDU related parameters
88 # User define input SSH and HTTPS related parameters
97 # OS related parameters.
103 # Networking related parameters
131 # Upload Image parameters
142 # Parameters for doing N-1 and N+1 code updates.
183 # Client related parameters
|
| /openbmc/u-boot/arch/arm/mach-uniphier/ |
| H A D | Kconfig | 104 bool "Enable dump command of DDR PHY parameters"
109 The command "ddrphy" shows the resulting parameters of DDR PHY
113 bool "Enable dump command of DDR Multi PHY parameters"
117 The command "ddrmphy" shows the resulting parameters of DDR Multi PHY
|
| /openbmc/u-boot/drivers/serial/ |
| H A D | Kconfig | 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
215 You will need to provide parameters to make this work. The
223 will need to provide parameters to make this work. The driver will
231 will need to provide parameters to make this work. The driver will
238 will need to provide parameters to make this work. The driver will
254 will need to provide parameters to make this work. The driver will
262 will need to provide parameters to make this work. The driver will
269 You will need to provide parameters to make this work. The driver will
[all …]
|