| /kernel/linux/linux-4.19/drivers/gpu/drm/i915/ |
| D | intel_hotplug.c | 33 * DOC: Hotplug
35 * Simply put, hotplug occurs when a display is connected to or disconnected
39 * Hotplug in i915 is handled in many different levels of abstraction.
43 * handlers gather the hotplug detect (HPD) information from relevant registers
44 * into a platform independent mask of hotplug pins that have fired.
47 * intel_hotplug.c does hotplug irq storm detection and mitigation, and passes
49 * regular hotplug).
53 * pulses, with failures and non-MST long pulses triggering regular hotplug
56 * The regular hotplug work function i915_hotplug_work_func() calls connector
57 * detect hooks, and, if connector status changes, triggers sending of hotplug
[all …]
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/i915/display/ |
| D | intel_hotplug.c | 31 * DOC: Hotplug
33 * Simply put, hotplug occurs when a display is connected to or disconnected
37 * Hotplug in i915 is handled in many different levels of abstraction.
41 * handlers gather the hotplug detect (HPD) information from relevant registers
42 * into a platform independent mask of hotplug pins that have fired.
45 * intel_hotplug.c does hotplug irq storm detection and mitigation, and passes
47 * regular hotplug).
51 * pulses, with failures and non-MST long pulses triggering regular hotplug
54 * The regular hotplug work function i915_hotplug_work_func() calls connector
55 * detect hooks, and, if connector status changes, triggers sending of hotplug
[all …]
|
| /kernel/linux/linux-4.19/drivers/pci/hotplug/ |
| D | Kconfig | 3 # PCI Hotplug support
7 bool "Support for PCI Hotplug"
10 Say Y here if you have a motherboard with a PCI Hotplug controller.
19 tristate "Compaq PCI Hotplug driver"
22 Say Y here if you have a motherboard with a Compaq PCI Hotplug
34 Say Y here if you have a Compaq server that has a PCI Hotplug
35 controller. This will allow the PCI Hotplug driver to store the PCI
41 tristate "IBM PCI Hotplug driver"
44 Say Y here if you have a motherboard with a IBM PCI Hotplug
53 bool "ACPI PCI Hotplug driver"
[all …]
|
| D | pci_hotplug_core.c | 3 * PCI HotPlug Controller Core
74 retval = get_power_status(pci_slot->hotplug, &value); in GET_STATUS()
84 struct hotplug_slot *slot = pci_slot->hotplug; in power_write_file()
131 retval = get_attention_status(pci_slot->hotplug, &value); in attention_read_file()
141 struct hotplug_slot_ops *ops = pci_slot->hotplug->ops; in attention_write_file()
155 retval = ops->set_attention_status(pci_slot->hotplug, attention); in attention_write_file()
175 retval = get_latch_status(pci_slot->hotplug, &value); in latch_read_file()
192 retval = get_adapter_status(pci_slot->hotplug, &value); in presence_read_file()
207 struct hotplug_slot *slot = pci_slot->hotplug; in test_write_file()
237 struct hotplug_slot *slot = pci_slot->hotplug; in has_power_file()
[all …]
|
| D | pciehp_core.c | 61 struct hotplug_slot *hotplug = NULL; in init_slot() local
67 hotplug = kzalloc(sizeof(*hotplug), GFP_KERNEL); in init_slot()
68 if (!hotplug) in init_slot()
75 /* Setup hotplug slot ops */ in init_slot()
95 /* register this slot with the hotplug pci core */ in init_slot()
96 hotplug->info = info; in init_slot()
97 hotplug->private = slot; in init_slot()
98 hotplug->ops = ops; in init_slot()
99 slot->hotplug_slot = hotplug; in init_slot()
102 retval = pci_hp_initialize(hotplug, in init_slot()
[all …]
|
| D | rpadlpar_core.c | 102 * find_php_slot - return hotplug slot structure for device node
105 * This routine will return the hotplug slot structure
195 /* Add hotplug slot */ in dlpar_add_pci_slot()
197 printk(KERN_ERR "%s: unable to add hotplug slot %s\n", in dlpar_add_pci_slot()
213 /* If pci slot is hotpluggable, use hotplug to remove it */ in dlpar_remove_phb()
216 printk(KERN_ERR "%s: unable to remove hotplug slot %s\n", in dlpar_remove_phb()
246 printk(KERN_ERR "%s: unable to add hotplug slot %s\n", in dlpar_add_phb()
276 * Make the hotplug module and the kernel aware of a newly added I/O Slot.
324 * Remove the kernel and hotplug representations of an I/O Slot.
349 * Remove the kernel and hotplug representations of a PCI I/O Slot.
[all …]
|
| D | cpcihp_generic.c | 11 * This generic CompactPCI hotplug driver should allow using the PCI hotplug
76 err("Invalid hotplug bus bridge device bus number"); in validate_parameters()
82 err("Invalid hotplug bus bridge device"); in validate_parameters()
88 err("Invalid hotplug bus bridge device slot number"); in validate_parameters()
154 err("Could not register cPCI hotplug controller"); in cpcihp_generic_init()
161 err("Could not register cPCI hotplug bus"); in cpcihp_generic_init()
168 err("Could not started cPCI hotplug system"); in cpcihp_generic_init()
|
| D | acpi_pcihp.c | 34 /* acpi_run_oshp - get control of hotplug from the firmware
36 * @handle - the handle of the hotplug controller.
64 * @dev: the pci_dev of the bridge that has a hotplug controller
66 * Attempt to take hotplug control from firmware.
108 * This hotplug controller was not listed in the ACPI name in acpi_get_hp_hw_control_from_firmware()
121 pci_info(pdev, "Requesting control of SHPC hotplug via OSHP (%s)\n", in acpi_get_hp_hw_control_from_firmware()
134 pci_info(pdev, "Cannot get control of SHPC hotplug\n"); in acpi_get_hp_hw_control_from_firmware()
138 pci_info(pdev, "Gained control of SHPC hotplug (%s)\n", in acpi_get_hp_hw_control_from_firmware()
|
| /kernel/linux/linux-5.10/drivers/pci/hotplug/ |
| D | Kconfig | 3 # PCI Hotplug support
7 bool "Support for PCI Hotplug"
10 Say Y here if you have a motherboard with a PCI Hotplug controller.
19 tristate "Compaq PCI Hotplug driver"
22 Say Y here if you have a motherboard with a Compaq PCI Hotplug
34 Say Y here if you have a Compaq server that has a PCI Hotplug
35 controller. This will allow the PCI Hotplug driver to store the PCI
41 tristate "IBM PCI Hotplug driver"
44 Say Y here if you have a motherboard with a IBM PCI Hotplug
53 bool "ACPI PCI Hotplug driver"
[all …]
|
| D | pci_hotplug_core.c | 3 * PCI HotPlug Controller Core
72 retval = get_power_status(pci_slot->hotplug, &value); in GET_STATUS()
82 struct hotplug_slot *slot = pci_slot->hotplug; in power_write_file()
129 retval = get_attention_status(pci_slot->hotplug, &value); in attention_read_file()
139 struct hotplug_slot *slot = pci_slot->hotplug; in attention_write_file()
174 retval = get_latch_status(pci_slot->hotplug, &value); in latch_read_file()
191 retval = get_adapter_status(pci_slot->hotplug, &value); in presence_read_file()
206 struct hotplug_slot *slot = pci_slot->hotplug; in test_write_file()
236 struct hotplug_slot *slot = pci_slot->hotplug; in has_power_file()
249 struct hotplug_slot *slot = pci_slot->hotplug; in has_attention_file()
[all …]
|
| D | pciehp_pci.c | 25 * pciehp_configure_device() - enumerate PCI devices below a hotplug bridge
26 * @ctrl: PCIe hotplug controller
28 * Enumerate PCI devices below a hotplug bridge and add them to the system.
45 * boot firmware or a previous hotplug event. in pciehp_configure_device()
74 * pciehp_unconfigure_device() - remove PCI devices below a hotplug bridge
75 * @ctrl: PCIe hotplug controller
80 * Unbind PCI devices below a hotplug bridge from their drivers and remove
|
| D | rpadlpar_core.c | 102 * find_php_slot - return hotplug slot structure for device node
105 * This routine will return the hotplug slot structure
195 /* Add hotplug slot */ in dlpar_add_pci_slot()
197 printk(KERN_ERR "%s: unable to add hotplug slot %s\n", in dlpar_add_pci_slot()
213 /* If pci slot is hotpluggable, use hotplug to remove it */ in dlpar_remove_phb()
216 printk(KERN_ERR "%s: unable to remove hotplug slot %s\n", in dlpar_remove_phb()
246 printk(KERN_ERR "%s: unable to add hotplug slot %s\n", in dlpar_add_phb()
276 * Make the hotplug module and the kernel aware of a newly added I/O Slot.
324 * Remove the kernel and hotplug representations of an I/O Slot.
349 * Remove the kernel and hotplug representations of a PCI I/O Slot.
[all …]
|
| D | cpcihp_generic.c | 11 * This generic CompactPCI hotplug driver should allow using the PCI hotplug
76 err("Invalid hotplug bus bridge device bus number"); in validate_parameters()
82 err("Invalid hotplug bus bridge device"); in validate_parameters()
88 err("Invalid hotplug bus bridge device slot number"); in validate_parameters()
154 err("Could not register cPCI hotplug controller"); in cpcihp_generic_init()
161 err("Could not register cPCI hotplug bus"); in cpcihp_generic_init()
168 err("Could not started cPCI hotplug system"); in cpcihp_generic_init()
|
| /kernel/linux/linux-4.19/Documentation/ |
| D | memory-hotplug.txt | 2 Memory Hotplug
6 :Updated: Add description of notifier of memory hotplug: Oct 11 2007
8 This document is about memory hotplug including how-to-use and current status.
9 Because Memory Hotplug is still under development, contents of this text will
15 1.1 purpose of memory hotplug
16 1.2. Phases of memory hotplug
19 3. sysfs files for memory hotplug
30 8. Memory hotplug event notifier
36 (1) x86_64's has special implementation for memory hotplug.
44 purpose of memory hotplug
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/mm/ |
| D | memory-hotplug.rst | 4 Memory Hotplug
10 This document is about memory hotplug including how-to-use and current status.
11 Because Memory Hotplug is still under development, contents of this text will
18 (1) x86_64's has special implementation for memory hotplug.
26 Purpose of memory hotplug
29 Memory Hotplug allows users to increase/decrease the amount of memory.
40 Linux memory hotplug is designed for both purpose.
42 Phases of memory hotplug
45 There are 2 phases in Memory Hotplug:
47 1) Physical Memory Hotplug phase
[all …]
|
| /kernel/linux/linux-4.19/Documentation/power/ |
| D | suspend-and-cpuhotplug.txt | 1 Interaction of Suspend code (S3) with the CPU hotplug infrastructure
6 I. How does the regular CPU hotplug code differ from how the Suspend-to-RAM
12 interactions involving the freezer and CPU hotplug and also tries to explain
16 What happens when regular CPU hotplug and Suspend-to-RAM race with each other
74 Disable regular cpu hotplug
92 | Decrease cpu_hotplug_disabled, thereby enabling regular cpu hotplug
108 Regular CPU hotplug call path
140 regular CPU hotplug]
145 regular CPU hotplug and the suspend code path converge at the _cpu_down() and
147 in that during regular CPU hotplug, 0 is passed for the 'tasks_frozen'
[all …]
|
| /kernel/linux/linux-5.10/Documentation/power/ |
| D | suspend-and-cpuhotplug.rst | 2 Interaction of Suspend code (S3) with the CPU hotplug infrastructure
8 I. Differences between CPU hotplug and Suspend-to-RAM
11 How does the regular CPU hotplug code differ from how the Suspend-to-RAM
17 interactions involving the freezer and CPU hotplug and also tries to explain
21 What happens when regular CPU hotplug and Suspend-to-RAM race with each other
79 Disable regular cpu hotplug
99 | Decrease cpu_hotplug_disabled, thereby enabling regular cpu hotplug
117 Regular CPU hotplug call path
149 regular CPU hotplug]
154 regular CPU hotplug and the suspend code path converge at the _cpu_down() and
[all …]
|
| /kernel/linux/linux-4.19/Documentation/core-api/ |
| D | cpu_hotplug.rst | 2 CPU hotplug in the Kernel
18 insertion and removal require support for CPU hotplug.
22 system execution path. Hence the need for CPU hotplug support in the
25 A more novel use of CPU-hotplug support is its use today in suspend resume
85 of them may be online. When physical hotplug is processed by the relevant
89 at which time hotplug is disabled.
99 Using CPU hotplug
115 drwxr-xr-x 2 root root 0 Dec 21 16:33 hotplug
136 and excluded from CPU hotplug. On X86 the kernel option
147 The CPU hotplug coordination
[all …]
|
| /kernel/linux/linux-5.10/Documentation/core-api/ |
| D | cpu_hotplug.rst | 2 CPU hotplug in the Kernel
18 insertion and removal require support for CPU hotplug.
22 system execution path. Hence the need for CPU hotplug support in the
25 A more novel use of CPU-hotplug support is its use today in suspend resume
78 of them may be online. When physical hotplug is processed by the relevant
82 at which time hotplug is disabled.
92 Using CPU hotplug
108 drwxr-xr-x 2 root root 0 Dec 21 16:33 hotplug
129 and excluded from CPU hotplug. On X86 the kernel option
140 The CPU hotplug coordination
[all …]
|
| /kernel/linux/linux-4.19/include/linux/ |
| D | pci_hotplug.h | 3 * PCI HotPlug Core Functions
18 * struct hotplug_slot_ops -the callbacks that the hotplug pci core can use
41 * hotplug events or where a slot can be reset independent of the bus.
43 * The table of function pointers that is passed to the hotplug pci core by a
44 * hotplug pci driver. These functions are called by the hotplug pci core when
63 * struct hotplug_slot_info - used to notify the hotplug pci core of the state of the slot
69 * Used to notify the hotplug pci core of the status of a specific slot.
79 * struct hotplug_slot - used to register a physical slot with the hotplug pci core
83 * @private: used by the hotplug pci controller driver to store whatever it
91 /* Variables below this are for use only by the hotplug pci core. */
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | pci_hotplug.h | 3 * PCI HotPlug Core Functions
18 * struct hotplug_slot_ops -the callbacks that the hotplug pci core can use
31 * hotplug events or where a slot can be reset independent of the bus.
33 * The table of function pointers that is passed to the hotplug pci core by a
34 * hotplug pci driver. These functions are called by the hotplug pci core when
51 * struct hotplug_slot - used to register a physical slot with the hotplug pci core
59 /* Variables below this are for use only by the hotplug pci core. */
|
| /kernel/linux/linux-4.19/Documentation/dev-tools/ |
| D | kselftest.rst | 13 in safe mode with a limited scope. In limited mode, cpu-hotplug test is
14 run on a single cpu as opposed to all hotplug capable cpus, and memory
15 hotplug test is run on 2% of hotplug capable memory instead of 10%.
17 Running the selftests (hotplug tests are run in limited mode)
75 Running the full range hotplug selftests
78 To build the hotplug tests::
80 $ make -C tools/testing/selftests hotplug
82 To run the hotplug tests::
|
| /kernel/linux/linux-5.10/kernel/ |
| D | cpu.c | 12 #include <linux/sched/hotplug.h>
44 * cpuhp_cpu_state - Per cpu hotplug state storage
47 * @thread: Pointer to the hotplug thread
108 * cpuhp_step - Hotplug state machine step
147 * Called from cpu hotplug and from the state register machinery.
323 * We can't have hotplug operations before userspace starts running, in lockdep_assert_cpus_held()
324 * and some init codepaths will knowingly not take the hotplug lock. in lockdep_assert_cpus_held()
345 * Wait for currently running CPU hotplug operations to complete (if any) and
346 * disable future CPU hotplug (from sysfs). The 'cpu_add_remove_lock' protects
348 * hotplug path before performing hotplug operations. So acquiring that lock
[all …]
|
| /kernel/linux/linux-4.19/Documentation/ABI/testing/ |
| D | sysfs-firmware-acpi | 21 What: /sys/firmware/acpi/hotplug/
25 There are separate hotplug profiles for different classes of
27 processors, PCI root bridges etc. A hotplug profile for a given
29 that class of devices will be handled by the ACPI core hotplug
31 of /sys/firmware/acpi/hotplug/.
34 hotplug profile:
37 hotplug events associated with the given class of
40 effectively disables hotplug for the correspoinding
|
| /kernel/linux/linux-4.19/kernel/ |
| D | cpu.c | 12 #include <linux/sched/hotplug.h>
42 * cpuhp_cpu_state - Per cpu hotplug state storage
45 * @thread: Pointer to the hotplug thread
103 * cpuhp_step - Hotplug state machine step
142 * Called from cpu hotplug and from the state register machinery.
318 * We can't have hotplug operations before userspace starts running, in lockdep_assert_cpus_held()
319 * and some init codepaths will knowingly not take the hotplug lock. in lockdep_assert_cpus_held()
330 * Wait for currently running CPU hotplug operations to complete (if any) and
331 * disable future CPU hotplug (from sysfs). The 'cpu_add_remove_lock' protects
333 * hotplug path before performing hotplug operations. So acquiring that lock
[all …]
|