Searched refs:removal (Results 1 – 25 of 119) sorted by relevance
12345
| /Linux-v5.15/drivers/of/unittest-data/ |
| D | overlay_6.dts | 6 /* overlays 6, 7 application and removal in sequence */
|
| D | overlay_7.dts | 6 /* overlays 6, 7 application and removal in sequence */
|
| D | overlay_8.dts | 6 /* overlays 8, 9, 10, 11 application and removal in bad sequence */
|
| D | overlay_9.dts | 6 /* overlays 8, 9, 10, 11 application and removal in bad sequence */
|
| D | overlay_11.dts | 6 /* overlays 8, 9, 10, 11 application and removal in bad sequence */
|
| D | overlay_10.dts | 6 /* overlays 8, 9, 10, 11 application and removal in bad sequence */
|
| /Linux-v5.15/Documentation/devicetree/bindings/sound/ |
| D | qcom,msm8916-wcd-analog.txt | 16 "mbhc_ins_rem_det1" - jack insert removal detect interrupt 1.
19 "mbhc_ins_rem_det" - jack insert removal detect interrupt.
|
| D | sirf-audio.txt | 14 insertion, removal.
|
| D | omap-abe-twl6040.txt | 16 insertion, removal.
|
| /Linux-v5.15/drivers/staging/sm750fb/ |
| D | TODO | 6 - check on hardware effects of removal of USE_HW_I2C and USE_DVICHIP (these two
|
| /Linux-v5.15/drivers/staging/ks7010/ |
| D | TODO | 27 - fix the 'card removal' event when card is inserted when booting
|
| /Linux-v5.15/Documentation/filesystems/ |
| D | efivarfs.rst | 24 as immutable files. This doesn't prevent removal - "chattr -i" will work -
|
| /Linux-v5.15/Documentation/networking/ |
| D | sctp.rst | 30 module removal of lksctp is not yet a safe activity.
|
| /Linux-v5.15/Documentation/sound/designs/ |
| D | jack-controls.rst | 21 intelligently based on jack insertion or removal events.
|
| /Linux-v5.15/Documentation/admin-guide/nfs/ |
| D | nfsd-admin-interfaces.rst | 39 removal of listening sockets, and startup and shutdown of the server.
|
| /Linux-v5.15/Documentation/driver-api/soundwire/ |
| D | locking.rst | 20 - Addition and removal of Slave(s), changing Slave status.
|
| /Linux-v5.15/Documentation/RCU/ |
| D | whatisRCU.rst | 67 The basic idea behind RCU is to split updates into "removal" and
68 "reclamation" phases. The removal phase removes references to data items
71 The reason that it is safe to run the removal phase concurrently with
76 removal phase. Because reclaiming data items can disrupt any readers
80 Splitting the update into removal and reclamation phases permits the
81 updater to perform the removal phase immediately, and to defer the
82 reclamation phase until all readers active during the removal phase have
85 during the removal phase need be considered, because any reader starting
86 after the removal phase will be unable to gain a reference to the removed
110 pointers are atomic on modern CPUs, allowing atomic insertion, removal,
[all …]
|
| /Linux-v5.15/drivers/staging/iio/Documentation/ |
| D | inkernel.txt | 33 on to the core via a call to iio_map_array_register. On removal,
|
| /Linux-v5.15/Documentation/kbuild/ |
| D | Kconfig.recursion-issue-01 | 37 # obvious that an easy to solution to this problem should just be the removal
|
| /Linux-v5.15/Documentation/translations/ |
| D | index.rst | 43 English documentation. Any content addition, removal or update, must be
|
| /Linux-v5.15/drivers/net/wireless/intel/iwlwifi/pcie/ |
| D | trans.c | 1986 struct iwl_trans_pcie_removal *removal = in iwl_trans_pcie_removal_wk() local
1988 struct pci_dev *pdev = removal->pdev; in iwl_trans_pcie_removal_wk()
1998 kfree(removal); in iwl_trans_pcie_removal_wk()
2062 struct iwl_trans_pcie_removal *removal; in __iwl_trans_pcie_grab_nic_access() local
2081 removal = kzalloc(sizeof(*removal), GFP_ATOMIC); in __iwl_trans_pcie_grab_nic_access()
2082 if (!removal) { in __iwl_trans_pcie_grab_nic_access()
2092 removal->pdev = to_pci_dev(trans->dev); in __iwl_trans_pcie_grab_nic_access()
2093 INIT_WORK(&removal->work, iwl_trans_pcie_removal_wk); in __iwl_trans_pcie_grab_nic_access()
2094 pci_dev_get(removal->pdev); in __iwl_trans_pcie_grab_nic_access()
2095 schedule_work(&removal->work); in __iwl_trans_pcie_grab_nic_access()
|
| /Linux-v5.15/Documentation/pcmcia/ |
| D | driver-changes.rst | 139 * device list iteration upon module removal (as of 2.6.10)
141 client list and call the ->detach() function upon module removal.
|
| /Linux-v5.15/Documentation/locking/ |
| D | robust-futex-ABI.rst | 69 the address of the 'lock entry', during list insertion and removal,
137 protocol on 'lock entry' insertion and removal:
148 On removal:
|
| /Linux-v5.15/Documentation/ABI/stable/ |
| D | sysfs-transport-srp | 14 Zero means immediate removal. Setting this attribute to "off"
|
| /Linux-v5.15/Documentation/core-api/ |
| D | cpu_hotplug.rst | 19 insertion and removal require support for CPU hotplug.
370 setup and removal.
401 invocations of the state callbacks on add and removal. To set up such a
477 removal, then this number has to be saved by the caller and used
513 In order to complete the removal, the teardown callback should not fail.
515 The state removal and the callback invocations are serialized against CPU
579 In order to complete the removal, the teardown callback should not fail.
|
12345
