| /Linux-v5.4/drivers/gpu/drm/i915/display/ |
| 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 …]
|
| /Linux-v5.4/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()
|
| 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()
|
| D | acpiphp_glue.c | 3 * ACPI PCI HotPlug glue functions to ACPI CA subsystem
54 * acpiphp_init_context - Create hotplug context and grab a reference to it.
75 * acpiphp_get_context - Get hotplug context and grab a reference to it.
93 * acpiphp_put_context - Drop a reference to ACPI hotplug context.
94 * @context: ACPI hotplug context to drop a reference to.
160 /* Root bridges will not have hotplug context. */ in free_bridge()
250 acpi_handle_err(handle, "No hotplug context\n"); in acpiphp_add_context()
290 * by the native PCIe hotplug (PCIeHP) or standard PCI hotplug in acpiphp_add_context()
304 pr_debug("found ACPI PCI Hotplug slot %llu at PCI %04x:%02x:%02x\n", in acpiphp_add_context()
312 pr_warn("Slot %llu already registered by another hotplug driver\n", sun); in acpiphp_add_context()
[all …]
|
| /Linux-v5.4/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 …]
|
| /Linux-v5.4/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 …]
|
| /Linux-v5.4/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 …]
|
| /Linux-v5.4/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. */
|
| D | cpuhotplug.h | 198 * cpuhp_setup_state - Setup hotplug state callbacks with calling the callbacks
225 * cpuhp_setup_state_nocalls - Setup hotplug state callbacks without calling the
324 * cpuhp_remove_state - Remove hotplug state callbacks and invoke the teardown
336 * cpuhp_remove_state_nocalls - Remove hotplug state callbacks without invoking
351 * cpuhp_remove_multi_state - Remove hotplug multi state callback
367 * cpuhp_state_remove_instance - Remove hotplug instance from state and invoke
382 * cpuhp_state_remove_instance_nocalls - Remove hotplug instance from state
|
| /Linux-v5.4/kernel/ |
| D | cpu.c | 11 #include <linux/sched/hotplug.h>
42 * cpuhp_cpu_state - Per cpu hotplug state storage
45 * @thread: Pointer to the hotplug thread
106 * cpuhp_step - Hotplug state machine step
145 * Called from cpu hotplug and from the state register machinery.
321 * We can't have hotplug operations before userspace starts running, in lockdep_assert_cpus_held()
322 * and some init codepaths will knowingly not take the hotplug lock. in lockdep_assert_cpus_held()
343 * Wait for currently running CPU hotplug operations to complete (if any) and
344 * disable future CPU hotplug (from sysfs). The 'cpu_add_remove_lock' protects
346 * hotplug path before performing hotplug operations. So acquiring that lock
[all …]
|
| /Linux-v5.4/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
|
| /Linux-v5.4/Documentation/driver-api/usb/ |
| D | hotplug.rst | 38 Kernel Hotplug Helper (``/sbin/hotplug``)
41 There is a kernel parameter: ``/proc/sys/kernel/hotplug``, which normally
42 holds the pathname ``/sbin/hotplug``. That parameter names a program
45 The /sbin/hotplug program can be invoked by any subsystem as part of its
52 Hotplug software and other resources is available at:
54 http://linux-hotplug.sourceforge.net
62 The USB subsystem currently invokes ``/sbin/hotplug`` when USB devices
|
| /Linux-v5.4/Documentation/media/dvb-drivers/ |
| D | ttusb-dec.rst | 18 - Hotplug firmware loader
38 Hotplug Firmware Loading
44 Copy the three files downloaded above into the /usr/lib/hotplug/firmware or
45 /lib/firmware directory (depending on configuration of firmware hotplug).
|
| /Linux-v5.4/drivers/xen/ |
| D | Kconfig | 14 bool "Memory hotplug support for Xen balloon driver"
17 Memory hotplug support for Xen balloon driver allows expanding memory
58 expanded to when using memory hotplug.
242 i.e. memory hotplug and cpu hotplug, and to block native drivers loaded,
245 To enable Xen features like cpu and memory hotplug, select Y here.
248 tristate "Xen ACPI memory hotplug"
251 This is Xen ACPI memory hotplug.
258 tristate "Xen ACPI cpu hotplug"
|
| /Linux-v5.4/drivers/pci/ |
| D | slot.c | 228 * @hotplug: set if caller is hotplug driver, NULL otherwise
263 struct hotplug_slot *hotplug) in pci_create_slot() argument
276 * Hotplug drivers are allowed to rename an existing slot, in pci_create_slot()
281 if (hotplug) { in pci_create_slot()
282 if ((err = slot->hotplug ? -EBUSY : 0) in pci_create_slot()
360 * pci_hp_create_link - create symbolic link to the hotplug driver module.
364 * the hotplug driver module.
368 struct hotplug_slot *slot = pci_slot->hotplug; in pci_hp_create_module_link()
386 * pci_hp_remove_link - remove symbolic link to the hotplug driver module.
390 * the hotplug driver module.
|
| /Linux-v5.4/Documentation/fault-injection/ |
| D | notifier-error-inject.rst | 10 * Memory hotplug notifier
33 Memory hotplug notifier error injection module
44 Example: Inject memory hotplug offline error (-12 == -ENOMEM)::
94 * tools/testing/selftests/cpu-hotplug/on-off-test.sh
95 * tools/testing/selftests/memory-hotplug/on-off-test.sh
|
| /Linux-v5.4/drivers/gpu/drm/ |
| D | drm_probe_helper.c | 55 * generic hotplug interrupt handling where the driver doesn't or cannot keep
59 * Drivers can also overwrite different parts e.g. use their own hotplug
444 * pick up any changes and fire the hotplug event. But if in drm_helper_probe_single_connector_modes()
446 * check here, and if anything changed start the hotplug code. in drm_helper_probe_single_connector_modes()
456 * The hotplug event code might call into the fb in drm_helper_probe_single_connector_modes()
550 * drm_kms_helper_hotplug_event - fire off KMS hotplug events
557 * Drivers should call this from their hotplug handling code when a change is
607 * want any hotplug detection at all for polling. */ in output_poll_execute()
631 * call after receiving a hotplug event due to this in output_poll_execute()
713 * @dev. Drivers which do not have reliable hotplug support in hardware can use
[all …]
|
| /Linux-v5.4/Documentation/dev-tools/ |
| D | kselftest.rst | 18 in safe mode with a limited scope. In limited mode, cpu-hotplug test is
19 run on a single cpu as opposed to all hotplug capable cpus, and memory
20 hotplug test is run on 2% of hotplug capable memory instead of 10%.
26 Running the selftests (hotplug tests are run in limited mode)
111 Running the full range hotplug selftests
114 To build the hotplug tests::
116 $ make -C tools/testing/selftests hotplug
118 To run the hotplug tests::
|
| /Linux-v5.4/arch/powerpc/platforms/pseries/ |
| D | pmem.c | 13 #include <linux/sched/hotplug.h>
112 /* slim chance, but we might get a hotplug event while booting */ in dlpar_hp_pmem()
116 pr_err("Hotplug event for a pmem device, but none exists\n"); in dlpar_hp_pmem()
121 pr_err("Unsupported hotplug event type %d\n", in dlpar_hp_pmem()
135 pr_err("Unsupported hotplug action (%d)\n", hp_elog->action); in dlpar_hp_pmem()
|
| /Linux-v5.4/tools/testing/selftests/ |
| D | Makefile | 8 TARGETS += cpu-hotplug
28 TARGETS += memory-hotplug
63 TARGETS_HOTPLUG = cpu-hotplug
64 TARGETS_HOTPLUG += memory-hotplug
155 hotplug: target
161 run_hotplug: hotplug
237 .PHONY: khdr all run_tests hotplug run_hotplug clean_hotplug run_pstore_crash install clean
|
| /Linux-v5.4/drivers/net/wireless/intel/iwlegacy/ |
| D | Kconfig | 29 look in the hotplug script /etc/hotplug/firmware.agent to
55 look in the hotplug script /etc/hotplug/firmware.agent to
|
