| /openbmc/linux/Documentation/devicetree/ |
| H A D | changesets.rst | 9 will be applied, or none of them will be. If an error occurs partway
12 applied.
14 When a changeset is applied, all of the changes get applied to the tree
31 entire changeset will get applied, or if there is an error the tree will
36 If a successfully applied changeset needs to be removed, it can be done
|
| /openbmc/u-boot/drivers/ddr/marvell/axp/ |
| H A D | xor.h | 24 * This enumerator describes the set of commands that can be applied on
27 * Start can be applied only when status is IDLE
28 * Stop can be applied only when status is IDLE, ACTIVE or PAUSED
29 * Pause can be applied only when status is ACTIVE
30 * Restart can be applied only when status is PAUSED
|
| /openbmc/openbmc/meta-arm/meta-arm/classes/ |
| H A D | apply_local_src_patches.bbclass | 2 # the fetched source code which need to be applied.
6 # LOCAL_SRC_PATCHES_DEST_DIR is the directory where the patches will be applied
39 if ! quilt applied $patch_basename >/dev/null ; then
45 bbdebug 1 "$patch_basename already applied."
|
| /openbmc/u-boot/drivers/ddr/marvell/a38x/ |
| H A D | xor.h | 53 * This enumerator describes the set of commands that can be applied on
57 * Start can be applied only when status is IDLE
58 * Stop can be applied only when status is IDLE, ACTIVE or PAUSED
59 * Pause can be applied only when status is ACTIVE
60 * Restart can be applied only when status is PAUSED
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | Settings.v1_4_0.json | 20 …: "This value shall indicate the values within the settings resource are applied during the mainte…
21 …: "This value shall indicate the values within the settings resource are applied immediately. Thi…
22 …: "This value shall indicate the values within the settings resource are applied during the mainte…
23 …set": "This value shall indicate the values within settings resource are applied when the system o…
195 …tion": "The entity tag (ETag) of the resource to which the settings were applied, after the applic…
196 …contain the entity tag (ETag) of the resource to which the settings were applied, after the applic…
225 "description": "The time when the settings can be applied.",
229 …perty with a single array member in order to inform the client when the settings will be applied.",
235 "description": "The time when the settings were applied.",
237 …cription": "This property shall indicate the time when the settings were applied to the resource.",
|
| H A D | redfish-schema.v1_10_0.json | |
| H A D | redfish-schema-v1.json | 33 "description": "The term shall be applied to a property in order to specify that the property is deprecated. The value of the string should explain the deprecation, including new property or properties to be used. The property can be supported in new and existing implementations, but usage in new implementations is discouraged. Deprecated properties are likely to be removed in a future major version of the schema."
37 "description": "The term shall be applied to a property in order to specify when the property was deprecated. The value of the string should contain the resource version where the property was deprecated."
41 "description": "The term shall be applied to a property in order to specify when the property was added. The value of the string should contain the resource version where the property was added."
53 "description": "The term shall be applied to a value in order to specify that the value is deprecated. The value of the string should explain the deprecation, including new value to be used. The value can be supported in new and existing implementations, but usage in new implementations is discouraged. Deprecated values are likely to be removed in a future major version of the schema."
57 "description": "The term shall be applied to a value in order to specify when the value was deprecated. The value of the string should contain the resource version where the value was deprecated."
61 "description": "The term shall be applied to a value in order to specify when the value was added. The value of the string should contain the resource version where the value was added."
139 "description": "The term is applied to Redfish schema or registry in order to specify licensing information."
|
| H A D | UpdateService.v1_14_1.json | |
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
| H A D | Settings.v1_4_0.json | 20 …: "This value shall indicate the values within the settings resource are applied during the mainte…
21 …: "This value shall indicate the values within the settings resource are applied immediately. Thi…
22 …: "This value shall indicate the values within the settings resource are applied during the mainte…
23 …set": "This value shall indicate the values within settings resource are applied when the system o…
195 …tion": "The entity tag (ETag) of the resource to which the settings were applied, after the applic…
196 …contain the entity tag (ETag) of the resource to which the settings were applied, after the applic…
225 "description": "The time when the settings can be applied.",
229 …perty with a single array member in order to inform the client when the settings will be applied.",
235 "description": "The time when the settings were applied.",
237 …cription": "This property shall indicate the time when the settings were applied to the resource.",
|
| H A D | redfish-schema.v1_10_0.json | |
| H A D | redfish-schema-v1.json | 33 "description": "The term shall be applied to a property in order to specify that the property is deprecated. The value of the string should explain the deprecation, including new property or properties to be used. The property can be supported in new and existing implementations, but usage in new implementations is discouraged. Deprecated properties are likely to be removed in a future major version of the schema."
37 "description": "The term shall be applied to a property in order to specify when the property was deprecated. The value of the string should contain the resource version where the property was deprecated."
41 "description": "The term shall be applied to a property in order to specify when the property was added. The value of the string should contain the resource version where the property was added."
53 "description": "The term shall be applied to a value in order to specify that the value is deprecated. The value of the string should explain the deprecation, including new value to be used. The value can be supported in new and existing implementations, but usage in new implementations is discouraged. Deprecated values are likely to be removed in a future major version of the schema."
57 "description": "The term shall be applied to a value in order to specify when the value was deprecated. The value of the string should contain the resource version where the value was deprecated."
61 "description": "The term shall be applied to a value in order to specify when the value was added. The value of the string should contain the resource version where the value was added."
139 "description": "The term is applied to Redfish schema or registry in order to specify licensing information."
|
| H A D | UpdateService.v1_14_1.json | |
| /openbmc/linux/net/tipc/ |
| H A D | monitor.c | 69 * @applied: number of reported domain members applied on this monitor list
80 u8 applied; member
217 int applied_aft = peer->applied; in mon_identify_lost_members()
231 /* Start probing if member was removed from applied domain */ in mon_identify_lost_members()
237 /* Member loss is confirmed if it is still in applied domain */ in mon_identify_lost_members()
257 peer->applied = 0; in mon_apply_domain()
263 peer->applied++; in mon_apply_domain()
282 self->applied = member_cnt; in mon_update_local_domain()
334 if (i++ < head->applied) { in mon_assign_roles()
382 peer->applied = 0; in tipc_mon_remove_peer()
[all …]
|
| /openbmc/linux/Documentation/admin-guide/hw-vuln/ |
| H A D | srso.rst | 51 The processor is vulnerable and no mitigations have been applied.
56 functionality to address the vulnerability has been applied.
60 The "Safe RET" mitigation (see below) has been applied to protect the
61 kernel, but the IBPB-extending microcode has not been applied. User
66 Extended IBPB functionality microcode patch has been applied. It does
138 an indrect branch prediction barrier after having applied the required
|
| /openbmc/phosphor-power/phosphor-regulators/docs/config_file/ |
| H A D | configuration.md | 5 Configuration changes that should be applied to a device or regulator rail.
12 The configuration changes are applied during the boot before regulators are
15 The configuration changes are applied by executing one or more actions. The
27 …r | Output voltage expressed as a decimal number. Applied using the [pmbus_…
|
| /openbmc/linux/Documentation/process/ |
| H A D | applying-patches.rst | 16 one of the many trees/branches should be applied to. Hopefully this document
57 To revert a previously applied patch, use the -R argument to patch.
58 So, if you applied a patch like this::
134 it'll tell you about it by saying the patch applied with **fuzz**.
141 read this file to see exactly what change couldn't be applied, so you can
144 If you don't have any third-party patches applied to your kernel source, but
158 applied with ``-p0`` instead of ``-p1`` (reading the patch file should reveal if
174 patch could not be applied correctly and the patch program was unable to
179 If you get ``Reversed (or previously applied) patch detected! Assume -R? [n]``
183 If you actually did apply this patch previously and you just re-applied it
[all …]
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-bus-iio-dac-ad5766 | 11 Inverts the dither applied to the selected DAC channel. Dither is not
24 Scales the dither before it is applied to the selected channel.
30 Selects dither source applied to the selected channel. Write "0" to
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/csdl/ |
| H A D | Settings_v1.xml | 52 …<Annotation Term="OData.Description" String="The requested operation is applied immediately. This…
53 …alue shall indicate the requested create, delete, or action operation is applied immediately. Thi…
56 … <Annotation Term="OData.Description" String="The requested operation is applied on a reset."/>
57 …alue shall indicate the requested create, delete, or action operation is applied when the system o…
60 …<Annotation Term="OData.Description" String="The requested operation is applied within the adminis…
61 …alue shall indicate the requested create, delete, or action operation is applied during the mainte…
64 …<Annotation Term="OData.Description" String="The requested operation is applied after a reset but …
65 …alue shall indicate the requested create, delete, or action operation is applied during the mainte…
68 …<Annotation Term="OData.Description" String="The requested operation is applied when the `StartUpd…
69 …alue shall indicate the requested create, delete, or action operation is applied when the `StartUp…
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/installed/ |
| H A D | Settings_v1.xml | 52 …<Annotation Term="OData.Description" String="The requested operation is applied immediately. This…
53 …alue shall indicate the requested create, delete, or action operation is applied immediately. Thi…
56 … <Annotation Term="OData.Description" String="The requested operation is applied on a reset."/>
57 …alue shall indicate the requested create, delete, or action operation is applied when the system o…
60 …<Annotation Term="OData.Description" String="The requested operation is applied within the adminis…
61 …alue shall indicate the requested create, delete, or action operation is applied during the mainte…
64 …<Annotation Term="OData.Description" String="The requested operation is applied after a reset but …
65 …alue shall indicate the requested create, delete, or action operation is applied during the mainte…
68 …<Annotation Term="OData.Description" String="The requested operation is applied when the `StartUpd…
69 …alue shall indicate the requested create, delete, or action operation is applied when the `StartUp…
[all …]
|
| /openbmc/linux/Documentation/userspace-api/media/mediactl/ |
| H A D | request-api.rst | 13 Another is support of stateless codecs, which require controls to be applied
30 applied when needed to get the expected result. Configuration values at the time
56 fact that the ioctl is part of said request, and is not to be applied
59 instead of being immediately applied, and buffers queued to a request do not
76 may synchronize so the requested pipeline's topology is applied before the
89 Controls can still be set without a request and are applied immediately,
134 be applied by the driver for the OUTPUT buffer, allowing user-space
|
| /openbmc/linux/mm/damon/ |
| H A D | paddr.c | 230 unsigned long addr, applied; in damon_pa_pageout() local
253 applied = reclaim_pages(&folio_list); in damon_pa_pageout()
255 return applied * PAGE_SIZE; in damon_pa_pageout()
261 unsigned long addr, applied = 0; in damon_pa_mark_accessed_or_deactivate() local
276 applied += folio_nr_pages(folio); in damon_pa_mark_accessed_or_deactivate()
280 return applied * PAGE_SIZE; in damon_pa_mark_accessed_or_deactivate()
|
| /openbmc/linux/tools/power/cpupower/man/ |
| H A D | cpupower-set.1 | 14 are applied on all cores. How to modify single core configurations is
16 option affects the whole system or can be applied to individual cores is
48 This option can be applied to individual cores only via the \-\-cpu option,
|
| /openbmc/linux/arch/parisc/kernel/ |
| H A D | alternative.c | 27 int index = 0, applied = 0; in apply_alternatives() local
96 applied++; in apply_alternatives()
99 pr_info("%s%salternatives: applied %d out of %d patches\n", in apply_alternatives()
101 applied, index); in apply_alternatives()
|
| /openbmc/linux/include/linux/ |
| H A D | netfilter_netdev.h | 67 * @dev: netdev whose egress hooks shall be applied to @skb
75 * When tc redirects a packet to another interface, netfilter is not applied
78 * The nf_skip_egress flag controls whether netfilter is applied on egress.
82 * false after sch_handle_egress(). This ensures that netfilter is applied
|
| /openbmc/linux/Documentation/devicetree/bindings/pinctrl/ |
| H A D | fsl,imx93-pinctrl.yaml | 53 "mux_val" indicates the mux value to be applied.
55 "input_val" indicates the select input value to be applied.
57 "pad_setting" indicates the pad configuration value to be applied.
|