| /openbmc/linux/drivers/gpu/drm/i915/display/ |
| H A D | intel_hotplug.c | 147 struct intel_hotplug *hpd = &dev_priv->display.hotplug; in intel_hpd_irq_storm_detect()
155 (!long_hpd && !dev_priv->display.hotplug.hpd_short_storm_enabled)) in intel_hpd_irq_storm_detect()
197 dev_priv->display.hotplug.stats[pin].state != HPD_MARK_DISABLED) in intel_hpd_irq_storm_switch_to_polling()
205 dev_priv->display.hotplug.stats[pin].state = HPD_DISABLED; in intel_hpd_irq_storm_switch_to_polling()
216 &dev_priv->display.hotplug.reenable_work, in intel_hpd_irq_storm_switch_to_polling()
225 display.hotplug.reenable_work.work); in intel_hpd_irq_storm_reenable_work()
239 dev_priv->display.hotplug.stats[pin].state != HPD_DISABLED) in intel_hpd_irq_storm_reenable_work()
251 if (dev_priv->display.hotplug.stats[pin].state == HPD_DISABLED) in intel_hpd_irq_storm_reenable_work()
252 dev_priv->display.hotplug.stats[pin].state = HPD_ENABLED; in intel_hpd_irq_storm_reenable_work()
303 container_of(work, struct drm_i915_private, display.hotplug.dig_port_work); in i915_digport_work_func()
[all …]
|
| H A D | intel_hotplug_irq.c | 136 struct intel_hotplug *hpd = &dev_priv->display.hotplug; in intel_hpd_init_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
410 hotplug |= hotplug_enables(encoder); in intel_hpd_hotplug_enables()
412 return hotplug; in intel_hpd_hotplug_enables()
467 dev_priv->display.hotplug.hpd, in i9xx_hpd_irq_handler()
504 dev_priv->display.hotplug.pch_hpd, in ibx_hpd_irq_handler()
[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/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/drivers/pci/hotplug/ |
| H A D | pci_hotplug_core.c | 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()
261 struct hotplug_slot *slot = pci_slot->hotplug; in has_latch_file()
[all …]
|
| /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/linux/Documentation/translations/zh_CN/core-api/ |
| H A D | cpu_hotplug.rst | 111 drwxr-xr-x 2 root root 0 Dec 21 16:33 hotplug
363 对于一个驱动程序或子系统有多个实例，并且每个实例都需要调用相同的CPU hotplug状态回
364 调的情况，CPU hotplug核心提供多实例支持。与驱动程序特定的实例列表相比，其优势在于
365 与实例相关的函数完全针对CPU hotplug操作进行序列化，并在添加和删除时提供状态回调的
454 状态移除和回调调用是针对CPU热拔插操作进行序列化的。如果移除函数必须从CPU hotplug
504 CPU hotplug回调和CPU hotplug读取锁定区域内使用。
560 所有注册的状态都被列举在 ``/sys/devices/system/cpu/hotplug/states`` ::
562 $ tail /sys/devices/system/cpu/hotplug/states
576 $ cat /sys/devices/system/cpu/cpu4/hotplug/state
578 $ echo 140 > /sys/devices/system/cpu/cpu4/hotplug/target
[all …]
|
| H A D | memory-hotplug.rst | 3 :Original: Documentation/core-api/memory-hotplug.rst
13 .. _cn_core-api_memory-hotplug:
|
| /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
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_hw_reduced_hotplug.rst | 7 events, including the hotplug ones. GED is modelled as a device
64 0: Memory hotplug event
66 2: NVDIMM hotplug event
67 3: CPU hotplug event
|
| 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/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/linux/tools/testing/selftests/ |
| H A D | Makefile | 14 TARGETS += cpu-hotplug
47 TARGETS += memory-hotplug
106 TARGETS_HOTPLUG = cpu-hotplug
107 TARGETS_HOTPLUG += memory-hotplug
192 hotplug: target
198 run_hotplug: hotplug
277 .PHONY: all run_tests hotplug run_hotplug clean_hotplug run_pstore_crash install clean gen_tar
|
| /openbmc/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
|
| /openbmc/linux/Documentation/arch/x86/x86_64/ |
| H A D | cpu-hotplug-spec.rst | 4 Firmware support for CPU hotplug under Linux/x86-64
7 Linux/x86-64 supports CPU hotplug now. For various reasons Linux wants to
16 For CPU hotplug Linux/x86-64 expects now that any possible future hotpluggable
|
| /openbmc/linux/drivers/firmware/psci/ |
| H A D | Kconfig | 9 Run the PSCI checker during startup. This checks that hotplug and
13 on and off through hotplug, so for now torture tests and PSCI checker
|
| /openbmc/qemu/docs/system/ |
| H A D | cpu-hotplug.rst | 2 Virtual CPU hotplug
5 A complete example of vCPU hotplug (and hot-unplug) using QMP
8 vCPU hotplug
12 allow vCPU hotplug)::
|
| /openbmc/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
|
| /openbmc/qemu/hw/acpi/ |
| H A D | meson.build | 10 acpi_ss.add(when: 'CONFIG_ACPI_CPU_HOTPLUG', if_false: files('acpi-cpu-hotplug-stub.c'))
12 acpi_ss.add(when: 'CONFIG_ACPI_MEMORY_HOTPLUG', if_false: files('acpi-mem-hotplug-stub.c'))
24 acpi_ss.add(when: 'CONFIG_ACPI_PCIHP', if_false: files('acpi-pci-hotplug-stub.c'))
|
| /openbmc/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).
91 download/extract it, and then copy it to /usr/lib/hotplug/firmware
92 or /lib/firmware (depending on configuration of firmware hotplug).
|
| /openbmc/linux/Documentation/admin-guide/media/ |
| H A D | ttusb-dec.rst | 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/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
|
| /openbmc/linux/drivers/media/usb/ttusb-dec/ |
| H A D | Kconfig | 19 download/extract them, and then copy them to /usr/lib/hotplug/firmware
20 or /lib/firmware (depending on configuration of firmware hotplug).
|