| /linux/drivers/gpu/drm/i915/display/ |
| H A D | intel_hotplug.c | 34 * DOC: Hotplug
36 * Simply put, hotplug occurs when a display is connected to or disconnected
40 * Hotplug in i915 is handled in many different levels of abstraction.
44 * handlers gather the hotplug detect (HPD) information from relevant registers
45 * into a platform independent mask of hotplug pins that have fired.
48 * intel_hotplug.c does hotplug irq storm detection and mitigation, and passes
50 * regular hotplug).
54 * pulses, with failures and non-MST long pulses triggering regular hotplug
57 * The regular hotplug work function i915_hotplug_work_func() calls connector
58 * detect hooks, and, if connector status changes, triggers sending of hotplug
[all …]
|
| /linux/drivers/pci/hotplug/ |
| H A 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 …]
|
| H A 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 …]
|
| H A 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 …]
|
| H A 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
|
| H A 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()
|
| H A 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 …]
|
| H A 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()
|
| H A 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/Documentation/power/ |
| H A 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/include/linux/ |
| H A 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. */
|
| H A 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.
196 /* Online section invoked on the hotplugged CPU from the hotplug thread */
261 * cpuhp_setup_state - Setup hotplug state callbacks with calling the @startup
280 * cpuhp_setup_state_cpuslocked - Setup hotplug state callbacks with calling
301 * cpuhp_setup_state_nocalls - Setup hotplug state callbacks without calling the
321 * cpuhp_setup_state_nocalls_cpuslocked - Setup hotplug state callbacks without
426 * cpuhp_remove_state - Remove hotplug state callbacks and invoke the teardown
438 * cpuhp_remove_state_nocalls - Remove hotplug state callbacks without invoking
[all …]
|
| /linux/include/linux/platform_data/ |
| H A 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/Documentation/driver-api/usb/ |
| H A 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/drivers/pci/ |
| H A D | slot.c | 193 * @hotplug: set if caller is hotplug driver, NULL otherwise
228 struct hotplug_slot *hotplug) in pci_create_slot() argument
241 * Hotplug drivers are allowed to rename an existing slot, in pci_create_slot()
246 if (hotplug) { in pci_create_slot()
247 if ((err = slot->hotplug ? -EBUSY : 0) in pci_create_slot()
327 * pci_hp_create_module_link - create symbolic link to hotplug driver module
331 * the hotplug driver module.
335 struct hotplug_slot *slot = pci_slot->hotplug; in pci_hp_create_module_link()
353 * pci_hp_remove_module_link - remove symbolic link to the hotplug driver
358 * the hotplug driver module.
|
| /linux/kernel/ |
| H A 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 …]
|
| H A D | smpboot.c | 25 * For the hotplug case we keep the task structs around and reuse
97 * smpboot_thread_fn - percpu hotplug thread loop function
283 * to hotplug
284 * @plug_thread: Hotplug thread descriptor
312 * smpboot_unregister_percpu_thread - Unregister a per_cpu thread related to hotplug
313 * @plug_thread: Hotplug thread descriptor
|
| /linux/Documentation/admin-guide/media/ |
| H A 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/Documentation/fault-injection/ |
| H A 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
|
| /linux/drivers/gpu/drm/ |
| H A D | drm_client.c | 118 * Registering a client generates a hotplug event that allows the client
120 * initialized its state to able to handle the hotplug event successfully.
130 if (client->funcs && client->funcs->hotplug) { in drm_client_register()
132 * Perform an initial hotplug event to pick up the in drm_client_register()
135 * in the list of clients, or a concurrent hotplug in drm_client_register()
138 * Hold the clientlist_mutex as for a regular hotplug in drm_client_register()
141 ret = client->funcs->hotplug(client); in drm_client_register()
143 drm_dbg_kms(dev, "client hotplug ret=%d\n", ret); in drm_client_register()
209 * drm_client_dev_hotplug - Send hotplug event to clients
212 * This function calls the &drm_client_funcs.hotplug callback on the attached clients.
[all …]
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-firmware-acpi | 67 What: /sys/firmware/acpi/hotplug/
71 There are separate hotplug profiles for different classes of
73 processors, PCI root bridges etc. A hotplug profile for a given
75 that class of devices will be handled by the ACPI core hotplug
77 of /sys/firmware/acpi/hotplug/.
80 hotplug profile:
84 hotplug events associated with the given class of
87 effectively disables hotplug for the corresponding
|
| /linux/drivers/staging/media/av7110/ |
| H A D | Kconfig | 30 download/extract it, and then copy it to /usr/lib/hotplug/firmware
31 or /lib/firmware (depending on configuration of firmware hotplug).
69 download/extract it, and then copy it to /usr/lib/hotplug/firmware
70 or /lib/firmware (depending on configuration of firmware hotplug).
|
| /linux/drivers/net/wireless/intel/iwlegacy/ |
| H A D | Kconfig | 28 look in the hotplug script /etc/hotplug/firmware.agent to
55 look in the hotplug script /etc/hotplug/firmware.agent to
|
| /linux/arch/arm/mach-mvebu/ |
| H A D | platsmp-a9.c | 46 * in the offline state after using CPU hotplug. in mvebu_cortex_a9_boot_secondary()
59 * When a CPU is brought back online, either through CPU hotplug, or
75 * CPU hotplug is implemented by putting offline CPUs into the in armada_38x_cpu_die()
83 * we support CPU hotplug. However, the function does not need to do
|
| /linux/tools/testing/selftests/ftrace/test.d/ftrace/ |
| H A D | func_hotplug.tc | 3 # description: ftrace - function trace across cpu hotplug
15 echo "We cannot test cpu hotplug in UP environment"
28 echo "We cannot test cpu hotplug with a single cpu online"
|