| /linux-6.14.4/drivers/pci/hotplug/ |
| D | Kconfig | 3 # PCI Hotplug support
7 bool "Support for PCI Hotplug"
11 Say Y here if you have a motherboard with a PCI Hotplug controller.
15 Thunderbolt/USB4 PCIe tunneling depends on native PCIe hotplug.
22 tristate "Compaq PCI Hotplug driver"
25 Say Y here if you have a motherboard with a Compaq PCI Hotplug
37 Say Y here if you have a Compaq server that has a PCI Hotplug
38 controller. This will allow the PCI Hotplug driver to store the PCI
44 tristate "IBM PCI Hotplug driver"
47 Say Y here if you have a motherboard with a IBM PCI Hotplug
[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 | rpadlpar_core.c | 103 * find_php_slot - return hotplug slot structure for device node
106 * This routine will return the hotplug slot structure
196 /* Add hotplug slot */ in dlpar_add_pci_slot()
198 printk(KERN_ERR "%s: unable to add hotplug slot %s\n", in dlpar_add_pci_slot()
214 /* If pci slot is hotpluggable, use hotplug to remove it */ in dlpar_remove_phb()
217 printk(KERN_ERR "%s: unable to remove hotplug slot %s\n", in dlpar_remove_phb()
247 printk(KERN_ERR "%s: unable to add hotplug slot %s\n", in dlpar_add_phb()
277 * Make the hotplug module and the kernel aware of a newly added I/O Slot.
325 * Remove the kernel and hotplug representations of an I/O Slot.
350 * Remove the kernel and hotplug representations of a PCI I/O Slot.
[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()
85 * pciehp_unconfigure_device() - remove PCI devices below a hotplug bridge
86 * @ctrl: PCIe hotplug controller
91 * Unbind PCI devices below a hotplug bridge from their drivers and remove
|
| 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 * @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()
|
| 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.
168 /* Root bridges will not have hotplug context. */ in free_bridge()
259 acpi_handle_err(handle, "No hotplug context\n"); in acpiphp_add_context()
299 * by the native PCIe hotplug (PCIeHP) or standard PCI hotplug in acpiphp_add_context()
313 pr_debug("found ACPI PCI Hotplug slot %llu at PCI %04x:%02x:%02x\n", in acpiphp_add_context()
321 pr_warn("Slot %llu already registered by another hotplug driver\n", sun); in acpiphp_add_context()
[all …]
|
| D | octep_hp.c | 181 return "hotplug enable"; in octep_hp_cmd_name()
183 return "hotplug disable"; in octep_hp_cmd_name()
227 /* Process all the hotplug commands */ in octep_hp_work_handler()
383 * Register all hotplug slots. Hotplug controller is the first function in octep_hp_pci_probe()
384 * of the PCI device. The hotplug slots are the remaining functions of in octep_hp_pci_probe()
385 * the PCI device. The hotplug slot functions are logically removed from in octep_hp_pci_probe()
387 * hotplug event is received. in octep_hp_pci_probe()
396 "Failed to register hotplug slot %u\n", in octep_hp_pci_probe()
427 MODULE_DESCRIPTION("Marvell OCTEON PCI Hotplug driver");
|
| D | pciehp.h | 47 * struct controller - PCIe hotplug controller
49 * @dsn: cached copy of Device Serial Number of Function 0 in the hotplug slot
77 * @hotplug_slot: structure registered with the PCI hotplug core
81 * @depth: Number of additional hotplug ports in the path to the root bus,
88 * PCIe hotplug has a 1:1 relationship between controller and slot, hence
113 struct hotplug_slot hotplug_slot; /* hotplug core interface */
149 * hotplug port was inaccessible when the interrupt occurred, requiring
151 * hotplug port accessible by runtime resuming its parents to D0
|
| /linux-6.14.4/drivers/gpu/drm/i915/display/ |
| D | intel_hotplug.c | 37 * DOC: Hotplug
39 * Simply put, hotplug occurs when a display is connected to or disconnected
43 * Hotplug in i915 is handled in many different levels of abstraction.
47 * handlers gather the hotplug detect (HPD) information from relevant registers
48 * into a platform independent mask of hotplug pins that have fired.
51 * intel_hotplug.c does hotplug irq storm detection and mitigation, and passes
53 * regular hotplug).
57 * pulses, with failures and non-MST long pulses triggering regular hotplug
60 * The regular hotplug work function i915_hotplug_work_func() calls connector
61 * detect hooks, and, if connector status changes, triggers sending of hotplug
[all …]
|
| D | intel_hotplug_irq.c | 136 struct intel_hotplug *hpd = &dev_priv->display.hotplug; in intel_hpd_init_pins()
182 /* For display hotplug interrupt */
194 * i915_hotplug_interrupt_update - update hotplug interrupt enable
338 * hotplug detection results from several registers.
363 "hotplug event received, stat 0x%08x, dig 0x%08x, pins 0x%08x, long 0x%08x\n", in intel_get_hpd_pins()
374 if (dev_priv->display.hotplug.stats[encoder->hpd_pin].state == HPD_ENABLED) in intel_hpd_enabled_irqs()
396 u32 hotplug = 0; in intel_hpd_hotplug_mask() local
399 hotplug |= hotplug_mask(pin); in intel_hpd_hotplug_mask()
401 return hotplug; in intel_hpd_hotplug_mask()
408 u32 hotplug = 0; in intel_hpd_hotplug_enables() local
[all …]
|
| /linux-6.14.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-6.14.4/Documentation/core-api/ |
| D | cpu_hotplug.rst | 2 CPU hotplug in the Kernel
19 insertion and removal require support for CPU hotplug.
23 system execution path. Hence the need for CPU hotplug support in the
26 A more novel use of CPU-hotplug support is its use today in suspend resume
73 of them may be online. When physical hotplug is processed by the relevant
77 at which time hotplug is disabled.
87 Using CPU hotplug
104 drwxr-xr-x 2 root root 0 Dec 21 16:33 hotplug
125 and excluded from CPU hotplug.
127 The CPU hotplug coordination
[all …]
|
| /linux-6.14.4/tools/testing/selftests/sched_ext/ |
| D | hotplug.c | 14 #include "hotplug.bpf.skel.h"
46 struct hotplug *skel; in test_hotplug()
102 struct hotplug *skel; in test_hotplug_attach()
110 skel = SCX_OPS_OPEN(hotplug_nocb_ops, hotplug); in test_hotplug_attach()
113 SCX_OPS_LOAD(skel, hotplug_nocb_ops, hotplug, uei); in test_hotplug_attach()
116 * Take the CPU offline to increment the global hotplug seq, which in test_hotplug_attach()
117 * should cause attach to fail due to us setting the hotplug seq above in test_hotplug_attach()
164 .name = "hotplug",
165 .description = "Verify hotplug behavior",
|
| /linux-6.14.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
53 * @slot_list: internal list used to track hotplug PCI slots
61 /* Variables below this are for use only by the hotplug pci core. */
|
| D | cpuhotplug.h | 26 * CPU hotplug states. The state machine invokes the installed state
38 * hotplug startup/teardown code with interrupts disabled.
41 * hotplug thread with interrupts and preemption enabled.
197 /* Online section invoked on the hotplugged CPU from the hotplug thread */
263 * cpuhp_setup_state - Setup hotplug state callbacks with calling the @startup
282 * cpuhp_setup_state_cpuslocked - Setup hotplug state callbacks with calling
303 * cpuhp_setup_state_nocalls - Setup hotplug state callbacks without calling the
323 * cpuhp_setup_state_nocalls_cpuslocked - Setup hotplug state callbacks without
428 * cpuhp_remove_state - Remove hotplug state callbacks and invoke the teardown
440 * cpuhp_remove_state_nocalls - Remove hotplug state callbacks without invoking
[all …]
|
| /linux-6.14.4/Documentation/arch/arm64/ |
| D | cpu-hotplug.rst | 5 CPU Hotplug and ACPI
8 CPU hotplug in the arm64 world is commonly used to describe the kernel taking
15 CPU Hotplug on physical systems - CPUs not present at boot
42 CPU Hotplug on virtual systems - CPUs not enabled at boot
49 CPU Hotplug on virtual systems is supported. It is distinct from physical
50 CPU Hotplug as all resources are described as ``present``, but CPUs may be
58 Virtual hotplug is implemented as a firmware policy affecting which CPUs can be
|
| /linux-6.14.4/include/linux/platform_data/ |
| D | mlxreg.h | 28 * enum mlxreg_hotplug_kind - kind of hotplug entry
57 * enum mlxreg_hotplug_device_action - hotplug device action required for
73 * struct mlxreg_core_hotplug_notifier - hotplug notifier block:
98 * Structure represents I2C hotplug device static data (board topology) and
127 * @hpdev - hotplug device data;
160 * @kind: kind of hotplug attribute;
207 * struct mlxreg_core_hotplug_platform_data - hotplug platform data:
209 * @items: same type components with the hotplug capability;
212 * @counter: number of the components with the hotplug capability;
|
| /linux-6.14.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-6.14.4/drivers/pci/ |
| D | slot.c | 194 * @hotplug: set if caller is hotplug driver, NULL otherwise
229 struct hotplug_slot *hotplug) in pci_create_slot() argument
242 * Hotplug drivers are allowed to rename an existing slot, in pci_create_slot()
247 if (hotplug) { in pci_create_slot()
248 if (slot->hotplug) { in pci_create_slot()
331 * pci_hp_create_module_link - create symbolic link to hotplug driver module
335 * the hotplug driver module.
339 struct hotplug_slot *slot = pci_slot->hotplug; in pci_hp_create_module_link()
357 * pci_hp_remove_module_link - remove symbolic link to the hotplug driver
362 * the hotplug driver module.
|
| /linux-6.14.4/Documentation/admin-guide/media/ |
| 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-6.14.4/kernel/ |
| D | cpu.c | 12 #include <linux/sched/hotplug.h>
48 * struct cpuhp_cpu_state - Per cpu hotplug state storage
51 * @fail: Current CPU hotplug callback state
52 * @thread: Pointer to the hotplug thread
118 * struct cpuhp_step - Hotplug state machine step
165 * Called from cpu hotplug and from the state register machinery.
519 * We can't have hotplug operations before userspace starts running, in lockdep_assert_cpus_held()
520 * and some init codepaths will knowingly not take the hotplug lock. in lockdep_assert_cpus_held()
556 * Wait for currently running CPU hotplug operations to complete (if any) and
557 * disable future CPU hotplug (from sysfs). The 'cpu_add_remove_lock' protects
[all …]
|
| /linux-6.14.4/Documentation/translations/zh_CN/kbuild/ |
| D | kconfig.rst | 158 /hotplug
159 这会列出所有包含 "hotplug" 的配置符号，例如，HOTPLUG_CPU，
166 /^hotplug
244 Ctrl-F hotplug
248 菜单：File, Search, hotplug
250 列出所有符号名称中包含 "hotplug" 的配置符号项。在此搜索对话框中，
|
| /linux-6.14.4/drivers/gpu/drm/ |
| D | drm_probe_helper.c | 56 * 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
609 * pick up any changes and fire the hotplug event. But if in drm_helper_probe_single_connector_modes()
611 * check here, and if anything changed start the hotplug code. in drm_helper_probe_single_connector_modes()
620 * The hotplug event code might call into the fb in drm_helper_probe_single_connector_modes()
713 * drm_kms_helper_hotplug_event - fire off KMS hotplug events
717 * client hotplug function, which is most commonly used to inform the fbdev
720 * Drivers should call this from their hotplug handling code when a change is
739 * drm_kms_helper_connector_hotplug_event - fire off a KMS connector hotplug event
791 * want any hotplug detection at all for polling. */ in output_poll_execute()
[all …]
|
| /linux-6.14.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/cpu-on-off-test.sh
95 * tools/testing/selftests/memory-hotplug/mem-on-off-test.sh
|