Home
last modified time | relevance | path

Searched full:hotplug (Results 1 – 25 of 848) sorted by relevance

12345678910>>...34

/Linux-v5.10/drivers/gpu/drm/i915/display/
Dintel_hotplug.c31 * 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 …]
/Linux-v5.10/drivers/pci/hotplug/
DKconfig3 # 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 …]
Dpci_hotplug_core.c3 * 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 …]
Dpciehp_pci.c25 * 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
Drpadlpar_core.c102 * 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 …]
Dcpcihp_generic.c11 * 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()
Dacpi_pcihp.c34 /* acpi_run_oshp - get control of hotplug from the firmware
36 * @handle - the handle of the hotplug controller.
64 * @pdev: 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()
Dacpiphp_glue.c3 * 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.
168 /* Root bridges will not have hotplug context. */ in free_bridge()
258 acpi_handle_err(handle, "No hotplug context\n"); in acpiphp_add_context()
298 * by the native PCIe hotplug (PCIeHP) or standard PCI hotplug in acpiphp_add_context()
312 pr_debug("found ACPI PCI Hotplug slot %llu at PCI %04x:%02x:%02x\n", in acpiphp_add_context()
320 pr_warn("Slot %llu already registered by another hotplug driver\n", sun); in acpiphp_add_context()
[all …]
/Linux-v5.10/Documentation/admin-guide/mm/
Dmemory-hotplug.rst4 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.10/Documentation/power/
Dsuspend-and-cpuhotplug.rst2 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.10/Documentation/core-api/
Dcpu_hotplug.rst2 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 …]
/Linux-v5.10/include/linux/
Dpci_hotplug.h3 * 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. */
/Linux-v5.10/kernel/
Dcpu.c12 #include <linux/sched/hotplug.h>
43 * cpuhp_cpu_state - Per cpu hotplug state storage
46 * @thread: Pointer to the hotplug thread
107 * cpuhp_step - Hotplug state machine step
146 * Called from cpu hotplug and from the state register machinery.
322 * We can't have hotplug operations before userspace starts running, in lockdep_assert_cpus_held()
323 * and some init codepaths will knowingly not take the hotplug lock. in lockdep_assert_cpus_held()
344 * Wait for currently running CPU hotplug operations to complete (if any) and
345 * disable future CPU hotplug (from sysfs). The 'cpu_add_remove_lock' protects
347 * hotplug path before performing hotplug operations. So acquiring that lock
[all …]
/Linux-v5.10/drivers/gpu/drm/i915/
Di915_irq.c157 struct i915_hotplug *hpd = &dev_priv->hotplug; in intel_hpd_init_pins()
289 /* For display hotplug interrupt */
307 * i915_hotplug_interrupt_update - update hotplug interrupt enable
1165 * hotplug detection results from several registers.
1190 "hotplug event received, stat 0x%08x, dig 0x%08x, pins 0x%08x, long 0x%08x\n", in intel_get_hpd_pins()
1476 * bits can itself generate a new hotplug interrupt :( in i9xx_hpd_irq_ack()
1510 dev_priv->hotplug.hpd, in i9xx_hpd_irq_handler()
1691 * unless we touch the hotplug register, even if hotplug_trigger is in ibx_hpd_irq_handler()
1710 dev_priv->hotplug.pch_hpd, in ibx_hpd_irq_handler()
1872 dev_priv->hotplug.pch_hpd, in icp_irq_handler()
[all …]
/Linux-v5.10/Documentation/driver-api/usb/
Dhotplug.rst38 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.10/Documentation/admin-guide/media/
Dttusb-dec.rst18 - 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.10/drivers/pci/
Dslot.c192 * @hotplug: set if caller is hotplug driver, NULL otherwise
227 struct hotplug_slot *hotplug) in pci_create_slot() argument
240 * Hotplug drivers are allowed to rename an existing slot, in pci_create_slot()
245 if (hotplug) { in pci_create_slot()
246 if ((err = slot->hotplug ? -EBUSY : 0) in pci_create_slot()
326 * pci_hp_create_link - create symbolic link to the hotplug driver module.
330 * the hotplug driver module.
334 struct hotplug_slot *slot = pci_slot->hotplug; in pci_hp_create_module_link()
352 * pci_hp_remove_link - remove symbolic link to the hotplug driver module.
356 * the hotplug driver module.
/Linux-v5.10/Documentation/ABI/testing/
Dsysfs-firmware-acpi24 What: /sys/firmware/acpi/hotplug/
28 There are separate hotplug profiles for different classes of
30 processors, PCI root bridges etc. A hotplug profile for a given
32 that class of devices will be handled by the ACPI core hotplug
34 of /sys/firmware/acpi/hotplug/.
37 hotplug profile:
41 hotplug events associated with the given class of
44 effectively disables hotplug for the correspoinding
/Linux-v5.10/drivers/xen/
DKconfig14 bool "Memory hotplug support for Xen balloon driver"
18 Memory hotplug support for Xen balloon driver allows expanding memory
60 expanded to when using memory hotplug.
246 i.e. memory hotplug and cpu hotplug, and to block native drivers loaded,
249 To enable Xen features like cpu and memory hotplug, select Y here.
252 tristate "Xen ACPI memory hotplug"
255 This is Xen ACPI memory hotplug.
262 tristate "Xen ACPI cpu hotplug"
/Linux-v5.10/Documentation/fault-injection/
Dnotifier-error-inject.rst10 * 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.10/drivers/gpu/drm/
Ddrm_probe_helper.c56 * generic hotplug interrupt handling where the driver doesn't or cannot keep
60 * Drivers can also overwrite different parts e.g. use their own hotplug
472 * pick up any changes and fire the hotplug event. But if in drm_helper_probe_single_connector_modes()
474 * check here, and if anything changed start the hotplug code. in drm_helper_probe_single_connector_modes()
484 * The hotplug event code might call into the fb in drm_helper_probe_single_connector_modes()
592 * drm_kms_helper_hotplug_event - fire off KMS hotplug events
599 * Drivers should call this from their hotplug handling code when a change is
649 * want any hotplug detection at all for polling. */ in output_poll_execute()
673 * call after receiving a hotplug event due to this in output_poll_execute()
755 * @dev. Drivers which do not have reliable hotplug support in hardware can use
[all …]
/Linux-v5.10/include/linux/platform_data/
Dmlxreg.h35 * Structure represents I2C hotplug device static data (board topology) and
56 * @hpdev - hotplug device data;
125 * struct mlxreg_core_hotplug_platform_data - hotplug platform data:
127 * @items: same type components with the hotplug capability;
130 * @counter: number of the components with the hotplug capability;
/Linux-v5.10/Documentation/dev-tools/
Dkselftest.rst18 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.10/arch/powerpc/platforms/pseries/
Dpmem.c13 #include <linux/sched/hotplug.h>
111 /* slim chance, but we might get a hotplug event while booting */ in dlpar_hp_pmem()
115 pr_err("Hotplug event for a pmem device, but none exists\n"); in dlpar_hp_pmem()
120 pr_err("Unsupported hotplug event type %d\n", in dlpar_hp_pmem()
134 pr_err("Unsupported hotplug action (%d)\n", hp_elog->action); in dlpar_hp_pmem()
/Linux-v5.10/tools/testing/selftests/
DMakefile11 TARGETS += cpu-hotplug
34 TARGETS += memory-hotplug
75 TARGETS_HOTPLUG = cpu-hotplug
76 TARGETS_HOTPLUG += memory-hotplug
176 hotplug: target
182 run_hotplug: hotplug
257 .PHONY: khdr all run_tests hotplug run_hotplug clean_hotplug run_pstore_crash install clean gen_tar

12345678910>>...34