Searched full:update (Results 1 – 25 of 344) sorted by relevance
12345678910>>...14
| /Documentation/driver-api/ |
| D | dell_rbu.rst | 2 Usage of the new open sourced rbu (Remote BIOS Update) driver
8 Document demonstrating the use of the Dell Remote BIOS Update driver.
16 update itself with the image downloaded in to the memory.
21 This driver works with Dell OpenManage or Dell Update Packages for updating
26 OpenManage and Dell Update packages (DUP).
28 Libsmbios can also be used to update BIOS on Dell systems go to
31 Dell_RBU driver supports BIOS update using the monolithic image and packetized
41 inform the BIOS to enable the update in the next system reboot.
54 The driver supports two types of update mechanism; monolithic and packetized.
55 These update mechanism depends upon the BIOS currently running on the system.
[all …]
|
| /Documentation/driver-api/nvdimm/ |
| D | security.rst | 28 update <old_keyid> <new_keyid> - enable or update passphrase.
33 master_update <keyid> <new_keyid> - enable or update master passphrase.
69 5. Update
71 When doing an update, it is expected that the existing key is removed from
74 keyid when doing the update operation. It is also expected that the new key
76 document. The update command written to the sysfs attribute will be with
78 update <old keyid> <new keyid>
118 10. Master Update
120 The command format for doing a master update is:
121 update <old keyid> <new keyid>
[all …]
|
| /Documentation/sound/soc/ |
| D | jack.rst | 20 snd_soc_jack_pins representing DAPM endpoints to update and blocks of
26 connected and so will want to make sure to update both speaker and
41 These represent a DAPM pin to update depending on some of the status
53 input to the system and update a jack by calling snd_soc_jack_report(),
54 specifying a subset of bits to update. The jack detection code should
56 update and the set of things to report when the jack is connected.
71 the list of pins to update then set up one or more jack detection
72 mechanisms to update that jack based on their current status.
|
| /Documentation/filesystems/ |
| D | ocfs2.txt | 49 noatime Do not update access time.
50 relatime(*) Update atime if the previous atime is older than
52 strictatime Always update atime, but the minimum update interval
54 atime_quantum=60(*) OCFS2 will not update atime unless this number
55 of seconds has passed since the last update.
56 Set to zero to always update atime. This option need
|
| /Documentation/x86/ |
| D | usb-legacy-support.rst | 42 in the kernel config or USB Legacy support in the BIOS. A BIOS update
43 could help, but so far no such update exists.
46 is usually fixed by a BIOS update. Check the board
47 manufacturers web site. If an update is not available, disable USB
|
| D | tsx_async_abort.rst | 26 microcode update which can be used to disable TSX. In addition, it
71 … 1 0 HW default No Need ucode update Need ucode update
86 … 1 0 HW default No Need ucode update Need ucode update
101 … 1 0 HW default No Need ucode update Need ucode update
|
| /Documentation/vm/ |
| D | hmm.rst | 116 not as easy as CPU page table updates. To update the device page table, you must
118 specific commands in it to perform the update (unmap, cache invalidations, and
173 * @update: update information (see struct mmu_notifier_range)
174 * Return: -EAGAIN if update.blockable false and callback need to
178 * page table is updated. The device driver must update its page table
179 * in response to this callback. The update argument tells what action
187 const struct hmm_update *update);
190 The device driver must perform the update action to the range (mark range
191 read only, or fully unmap, etc.). The device must complete the update before
250 take_lock(driver->update);
[all …]
|
| /Documentation/trace/ |
| D | events-power.rst | 74 The PM QoS events are used for QoS add/update/remove request and for
75 target/flags update.
93 The third parameter is the current QoS value to update.
95 And, there are also events used for device PM QoS add/update/remove request.
102 The first parameter gives the device name which tries to add/update/remove
|
| /Documentation/crypto/ |
| D | devel-algos.rst | 197 .init() -> .update() -> .final() ! .update() might not be called
203 .init() -> .update() -> .finup() ! .update() may not be called
220 v v ! .update() may not be called
221 .setkey() -> .init() -> .update() -> .export() at all in this scenario.
229 .import -> .update() -> .final() ! .update() may not be called
240 - call .init() and then (as many times) .update()
245 to .init() or .update(), since there might be no chance to free them.
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | da9150-fg.txt | 7 - dlg,update-interval: Interval time (milliseconds) between battery level checks.
20 dlg,update-interval = <10000>;
|
| /Documentation/security/keys/ |
| D | trusted-encrypted.rst | 52 keyctl update key "update [options]"
100 keyctl update keyid "update key-type:master-key-name"
156 $ keyctl update 268728824 "update pcrinfo=`cat pcr.blob`"
|
| /Documentation/RCU/ |
| D | checklist.txt | 34 1. Does the update code have proper mutual exclusion?
64 rcu_read_lock_sched(), or by the appropriate update-side lock.
74 3. Does the update code tolerate concurrent accesses?
81 a. Use the RCU variants of the list and hlist update
107 readers see valid data at all phases of the update.
147 perfectly legal (if redundant) for update-side code to
235 usually results in simpler code. So, unless update performance is
248 code using call_rcu() should explicitly limit update rate in
263 One way to stall the updates is to acquire the update-side
273 b. Limiting update rate. For example, if updates occur only
[all …]
|
| D | rcu.rst | 6 The basic idea behind RCU (read-copy update) is to split destructive
71 "RCU" stands for "read-copy update". The file Documentation/RCU/listRCU.rst
73 "read-copy update" to find it.
|
| D | whatisRCU.txt | 1 What is RCU? -- "Read, Copy, Update"
68 Splitting the update into removal and reclamation phases permits the
77 So the typical RCU update sequence goes something like the following:
95 This is because lock-based updaters typically update data items in place,
109 thread performs both the update step (step (a) above) and the reclamation
201 it is illegal to block or where update-side performance is
207 of automatically limiting update rate should grace periods
210 update rate in order to gain this same sort of resilience. See
211 checklist.txt for some approaches to limiting the update rate.
265 if an update happened while in the critical section, and incur
[all …]
|
| /Documentation/arm/omap/ |
| D | omap.rst | 11 v4.3+ Update is needed for custom .config files to make sure
15 v4.18+ Update is needed for custom .config files to make sure
|
| /Documentation/virt/kvm/ |
| D | msr.txt | 29 guaranteed to update this data at the moment of MSR write.
35 An odd version indicates an in-progress update.
70 The hypervisor may update this structure at any time it sees fit until
77 An odd version indicates an in-progress update.
80 of the update of this structure. Guests can subtract this value
82 structure update.
221 The hypervisor may update this structure at any time it sees fit until
230 in-progress update.
|
| /Documentation/ABI/stable/ |
| D | sysfs-class-ubi | 160 if it is corrupted (e.g., due to an interrupted volume update).
207 Contains ASCII "0\n" if the update marker is not set for this
208 volume, and "1\n" if it is set. The update marker is set when
209 volume update starts, and cleaned when it ends. So the presence
210 of the update marker indicates that the volume is being updated
211 at the moment of the update was interrupted. The later may be
|
| /Documentation/driver-api/nfc/ |
| D | nfc-pn544.rst | 18 In the normal (HCI) mode and in the firmware update mode read and
29 checksum. Firmware update messages have the length in the second (MSB)
|
| /Documentation/translations/ |
| D | index.rst | 27 It is very unlikely that an update to :ref:`linux_doc` will be propagated
38 English documentation. Any content addition, removal or update, must be
|
| /Documentation/driver-api/thermal/ |
| D | exynos_thermal_emulation.rst | 23 When you input any temperature you want to update to sysfs node, it
32 enabling. It means when you want to update the any value of delay or
|
| /Documentation/translations/zh_CN/video4linux/ |
| D | omap3isp.txt | 3 If you have any comment or update to the content, please contact the
155 这些结构体中的 update 域标识是否针对指定的功能更新配置，而 flag 域
158 update 和 flag 位接受以下掩码值。CCDC 和 preview（预览）模块的
162 对于 VIDIOC_OMAP3ISP_CCDC_CFG，下面列出了 update 和 flag 域
|
| /Documentation/power/ |
| D | pm_qos_interface.rst | 50 Will update the list element pointed to by the handle with the new target value
55 Will remove the element. After removal it will update the aggregate target and
122 Will update the list element pointed to by the handle with the new target
127 Will remove the element. After removal it will update the aggregate target
225 DEV_PM_QOS_LATENCY_TOLERANCE device PM QoS type to add, remove and update
|
| /Documentation/translations/ja_JP/ |
| D | stable_kernel_rules.txt | 10 comment or update of this file, please try to update Original(English)
|
| /Documentation/sphinx/ |
| D | load_config.py | 53 namespace.update(config)
57 namespace.update(config)
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-leds-gt683r | 7 of one LED will update the mode of its two sibling devices as
|
12345678910>>...14