Searched refs:removal (Results 1 – 25 of 125) sorted by relevance
12345
| /linux-5.19.10/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_10.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 */
|
| /linux-5.19.10/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-5.19.10/drivers/staging/sm750fb/ |
| D | TODO | 6 - check on hardware effects of removal of USE_HW_I2C and USE_DVICHIP (these two
|
| /linux-5.19.10/drivers/staging/ks7010/ |
| D | TODO | 27 - fix the 'card removal' event when card is inserted when booting
|
| /linux-5.19.10/Documentation/filesystems/ |
| D | efivarfs.rst | 24 as immutable files. This doesn't prevent removal - "chattr -i" will work -
|
| /linux-5.19.10/Documentation/networking/ |
| D | sctp.rst | 30 module removal of lksctp is not yet a safe activity.
|
| /linux-5.19.10/Documentation/sound/designs/ |
| D | jack-controls.rst | 21 intelligently based on jack insertion or removal events.
|
| /linux-5.19.10/Documentation/admin-guide/nfs/ |
| D | nfsd-admin-interfaces.rst | 39 removal of listening sockets, and startup and shutdown of the server.
|
| /linux-5.19.10/Documentation/hwmon/ |
| D | hwmon-kernel-api.rst | 73 hwmon device does not have to be removed explicitly by the removal function.
84 hwmon device does not have to be removed explicitly by the removal function.
96 removal would be too late.
112 removal.
|
| /linux-5.19.10/Documentation/driver-api/soundwire/ |
| D | locking.rst | 20 - Addition and removal of Slave(s), changing Slave status.
|
| /linux-5.19.10/drivers/staging/iio/Documentation/ |
| D | inkernel.txt | 33 on to the core via a call to iio_map_array_register. On removal,
|
| /linux-5.19.10/Documentation/translations/ |
| D | index.rst | 43 English documentation. Any content addition, removal or update, must be
|
| /linux-5.19.10/Documentation/kbuild/ |
| D | Kconfig.recursion-issue-01 | 37 # obvious that an easy to solution to this problem should just be the removal
|
| /linux-5.19.10/drivers/net/wireless/intel/iwlwifi/pcie/ |
| D | trans.c | 2059 struct iwl_trans_pcie_removal *removal = in iwl_trans_pcie_removal_wk() local
2061 struct pci_dev *pdev = removal->pdev; in iwl_trans_pcie_removal_wk()
2071 kfree(removal); in iwl_trans_pcie_removal_wk()
2135 struct iwl_trans_pcie_removal *removal; in __iwl_trans_pcie_grab_nic_access() local
2154 removal = kzalloc(sizeof(*removal), GFP_ATOMIC); in __iwl_trans_pcie_grab_nic_access()
2155 if (!removal) { in __iwl_trans_pcie_grab_nic_access()
2165 removal->pdev = to_pci_dev(trans->dev); in __iwl_trans_pcie_grab_nic_access()
2166 INIT_WORK(&removal->work, iwl_trans_pcie_removal_wk); in __iwl_trans_pcie_grab_nic_access()
2167 pci_dev_get(removal->pdev); in __iwl_trans_pcie_grab_nic_access()
2168 schedule_work(&removal->work); in __iwl_trans_pcie_grab_nic_access()
|
| /linux-5.19.10/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-5.19.10/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-5.19.10/Documentation/ABI/stable/ |
| D | sysfs-transport-srp | 14 Zero means immediate removal. Setting this attribute to "off"
|
| /linux-5.19.10/Documentation/RCU/ |
| D | whatisRCU.rst | 69 The basic idea behind RCU is to split updates into "removal" and
70 "reclamation" phases. The removal phase removes references to data items
73 The reason that it is safe to run the removal phase concurrently with
78 removal phase. Because reclaiming data items can disrupt any readers
82 Splitting the update into removal and reclamation phases permits the
83 updater to perform the removal phase immediately, and to defer the
84 reclamation phase until all readers active during the removal phase have
87 during the removal phase need be considered, because any reader starting
88 after the removal phase will be unable to gain a reference to the removed
112 pointers are atomic on modern CPUs, allowing atomic insertion, removal,
[all …]
|
12345