| /openbmc/linux/drivers/gpu/drm/i915/display/ |
| H A 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 …]
|
| H A D | intel_hotplug_irq.c | 136 struct intel_hotplug *hpd = &dev_priv->display.hotplug; in intel_hpd_init_pins()
182 /* For display hotplug interrupt */
193 * i915_hotplug_interrupt_update - update hotplug interrupt enable
337 * hotplug detection results from several registers.
362 "hotplug event received, stat 0x%08x, dig 0x%08x, pins 0x%08x, long 0x%08x\n", in intel_get_hpd_pins()
373 if (dev_priv->display.hotplug.stats[encoder->hpd_pin].state == HPD_ENABLED) in intel_hpd_enabled_irqs()
395 u32 hotplug = 0; in intel_hpd_hotplug_mask() local
398 hotplug |= hotplug_mask(pin); in intel_hpd_hotplug_mask()
400 return hotplug; in intel_hpd_hotplug_mask()
407 u32 hotplug = 0; in intel_hpd_hotplug_enables() local
[all …]
|
| /openbmc/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 | 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()
81 * pciehp_unconfigure_device() - remove PCI devices below a hotplug bridge
82 * @ctrl: PCIe hotplug controller
87 * Unbind PCI devices below a hotplug bridge from their drivers and remove
|
| 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 | 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 | 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 | 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 …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-connectivity/libmtp/libmtp/ |
| H A D | 0001-Use-native-mtp-hotplug.patch | 4 Subject: [PATCH] Use native mtp-hotplug
23 libmtp.usermap: util/mtp-hotplug
24 - util/mtp-hotplug > libmtp.usermap
25 + mtp-hotplug > libmtp.usermap
27 @UDEV_RULES@: util/mtp-hotplug
28 - util/mtp-hotplug -u -p"@UDEV@" @UDEV_GROUP@ @UDEV_MODE@ > @UDEV_RULES@
29 + mtp-hotplug -u -p"@UDEV@" @UDEV_GROUP@ @UDEV_MODE@ > @UDEV_RULES@
31 libmtp.fdi: util/mtp-hotplug
32 - util/mtp-hotplug -H > libmtp.fdi
33 + mtp-hotplug -H > libmtp.fdi
[all …]
|
| H A D | 0002-util-mtp-hotplug.c-Enable-stack-memory-protection.patch | 4 Subject: [PATCH] util/mtp-hotplug.c: Enable stack memory protection
15 $ objdump -T ./util/.libs/mtp-hotplug | grep __stack_chk_fail
20 util/mtp-hotplug.c | 2 +-
23 diff --git a/util/mtp-hotplug.c b/util/mtp-hotplug.c
25 --- a/util/mtp-hotplug.c
26 +++ b/util/mtp-hotplug.c
|
| /openbmc/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 …]
|
| /openbmc/linux/Documentation/core-api/ |
| H A 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
79 of them may be online. When physical hotplug is processed by the relevant
83 at which time hotplug is disabled.
93 Using CPU hotplug
110 drwxr-xr-x 2 root root 0 Dec 21 16:33 hotplug
131 and excluded from CPU hotplug.
133 The CPU hotplug coordination
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-bsp/pcmciautils/pcmciautils/ |
| H A D | makefile_fix.patch | 35 install-hotplug:
37 - $(INSTALL_PROGRAM) -D hotplug/pcmcia.agent $(DESTDIR)$(hotplugdir)/pcmcia.agent
38 - $(INSTALL_PROGRAM) -D hotplug/pcmcia.rc $(DESTDIR)$(hotplugdir)/pcmcia.rc
39 + $(INSTALL_PROGRAM) hotplug/pcmcia.agent $(DESTDIR)$(hotplugdir)/pcmcia.agent
40 + $(INSTALL_PROGRAM) hotplug/pcmcia.rc $(DESTDIR)$(hotplugdir)/pcmcia.rc
42 uninstall-hotplug:
45 install-socket-hotplug:
46 - $(INSTALL_PROGRAM) -D hotplug/pcmcia_socket.agent $(DESTDIR)$(hotplugdir)/pcmcia_socket.agent
47 - $(INSTALL_PROGRAM) -D hotplug/pcmcia_socket.rc $(DESTDIR)$(hotplugdir)/pcmcia_socket.rc
48 + $(INSTALL_PROGRAM) hotplug/pcmcia_socket.agent $(DESTDIR)$(hotplugdir)/pcmcia_socket.agent
[all …]
|
| /openbmc/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.
203 /* Online section invoked on the hotplugged CPU from the hotplug thread */
273 * cpuhp_setup_state - Setup hotplug state callbacks with calling the @startup
292 * cpuhp_setup_state_cpuslocked - Setup hotplug state callbacks with calling
313 * cpuhp_setup_state_nocalls - Setup hotplug state callbacks without calling the
333 * cpuhp_setup_state_nocalls_cpuslocked - Setup hotplug state callbacks without
438 * cpuhp_remove_state - Remove hotplug state callbacks and invoke the teardown
450 * cpuhp_remove_state_nocalls - Remove hotplug state callbacks without invoking
[all …]
|
| /openbmc/qemu/docs/ |
| H A D | memory-hotplug.txt | 1 QEMU memory hotplug
4 This document explains how to use the memory hotplug feature in QEMU,
7 Guest support is required for memory hotplug to work.
9 Basic RAM hotplug
12 In order to be able to hotplug memory, QEMU has to be told how many
35 Two monitor commands are used to hotplug memory:
50 Besides basic RAM hotplug, QEMU also supports using files as a memory
67 2MB pages. Also, the guest has additional memory slots to hotplug more
|
| /openbmc/qemu/docs/specs/ |
| H A D | acpi_pci_hotplug.rst | 1 QEMU<->ACPI BIOS PCI hotplug interface
4 QEMU supports PCI hotplug via ACPI, for PCI bus 0. This document
10 Generic ACPI GPE block. Bit 1 (GPE.1) used to notify PCI hotplug/eject
35 Read: Hotplug features register. Used by platform to identify features
41 write: bit per slot eject, read: hotplug feature set
42 - Read-only hotplug capable register @0xae0c, 4-byte access, bit per slot
|
| H A D | acpi_cpu_hotplug.rst | 1 QEMU<->ACPI BIOS CPU hotplug interface
4 QEMU supports CPU hotplug via ACPI. This document
11 Legacy ACPI CPU hotplug interface registers
20 to modern CPU hotplug interface, write 0 into it to do switch.
27 Modern ACPI CPU hotplug interface registers
189 (x86) Detecting and enabling modern CPU hotplug interface
192 QEMU starts with legacy CPU hotplug interface enabled. Detecting and
193 switching to modern interface is based on the 2 legacy CPU hotplug features:
198 Use following steps to detect and enable modern CPU hotplug interface:
205 Otherwise legacy or no CPU hotplug interface available
|
| /openbmc/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;
|
| /openbmc/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
|
| /openbmc/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).
|
| /openbmc/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
119 * struct cpuhp_step - Hotplug state machine step
166 * Called from cpu hotplug and from the state register machinery.
518 * We can't have hotplug operations before userspace starts running, in lockdep_assert_cpus_held()
519 * and some init codepaths will knowingly not take the hotplug lock. in lockdep_assert_cpus_held()
547 * Wait for currently running CPU hotplug operations to complete (if any) and
548 * disable future CPU hotplug (from sysfs). The 'cpu_add_remove_lock' protects
[all …]
|
| /openbmc/linux/drivers/pci/ |
| H A 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 ((err = slot->hotplug ? -EBUSY : 0) in pci_create_slot()
329 * pci_hp_create_module_link - create symbolic link to hotplug driver module
333 * the hotplug driver module.
337 struct hotplug_slot *slot = pci_slot->hotplug; in pci_hp_create_module_link()
355 * pci_hp_remove_module_link - remove symbolic link to the hotplug driver
360 * the hotplug driver module.
|
| /openbmc/linux/drivers/gpu/drm/ |
| H A D | drm_client.c | 126 * Registering a client generates a hotplug event that allows the client
128 * initialized its state to able to handle the hotplug event successfully.
138 if (client->funcs && client->funcs->hotplug) { in drm_client_register()
140 * Perform an initial hotplug event to pick up the in drm_client_register()
143 * in the list of clients, or a concurrent hotplug in drm_client_register()
146 * Hold the clientlist_mutex as for a regular hotplug in drm_client_register()
149 ret = client->funcs->hotplug(client); in drm_client_register()
151 drm_dbg_kms(dev, "client hotplug ret=%d\n", ret); in drm_client_register()
206 * drm_client_dev_hotplug - Send hotplug event to clients
209 * This function calls the &drm_client_funcs.hotplug callback on the attached clients.
[all …]
|