Home
last modified time | relevance | path

Searched full:probing (Results 1 – 25 of 939) sorted by relevance

12345678910>>...38

/openbmc/linux/drivers/base/
H A Ddd.c43 * request probing to be deferred by returning -EPROBE_DEFER from its probe hook
67 * to prohibit probing of devices as it could be unsafe.
79 * deferred_probe_work_func() - Retry probing devices in the active list.
109 * Drop the mutex while probing each device; the probe path may in deferred_probe_work_func()
158 * driver_deferred_probe_trigger() - Kick off re-probing deferred devices
165 * more than one device is probing at the same time, it is possible for one
171 * trigger has occurred in the midst of probing a driver. If the trigger count
201 * It will disable probing of devices and defer their probes instead.
213 * It will restore normal behavior and trigger re-probing of deferred
338 * deferred_probe_initcall() - Enable probing of deferred devices
[all …]
/openbmc/u-boot/drivers/video/stm32/
H A DKconfig23 framebuffer during device-model binding/probing.
32 framebuffer during device-model binding/probing.
41 framebuffer during device-model binding/probing.
/openbmc/linux/Documentation/driver-api/
H A Deisa.rst25 implements bus probing (detecting EISA cards available on the bus),
53 to this device, as well as some parameters for probing purposes::
197 Force the probing code to probe EISA slots even when it cannot find an
199 (don't force), and set to 1 (force probing) when either
206 code (since probing is now in the core EISA code). Unfortunately, most
207 drivers share their probing routine between ISA, and EISA. Special
215 Unfortunately, most drivers are doing the probing by themselves, and
H A Ddevice_link.rst64 presence of the supplier after adding the link, and defer probing on
66 ``->probe`` callback while the supplier is still probing, but the consumer must
111 may cause probing of the consumer to be deferred indefinitely. This can become
144 probing) or never. Consequently it cannot be determined whether to defer
145 probing or not. It would be possible to notify drivers when optional
146 resources become available after probing, but it would come at a high cost
249 A more suitable approach might be to simply use deferred probing or
309 probing are waited for until they are done.
/openbmc/linux/drivers/gpu/drm/display/
H A Ddrm_dp_aux_bus.c226 * @done_probing: Callback functions to call after EP device finishes probing.
234 * our sub-device will have finished probing. It should be noted that if our
235 * sub-device returns -EPROBE_DEFER or is probing asynchronously for some
240 * when our sub device finishes probing. Our sub device is expected to be an
243 * probing. For this reason the caller can pass in a function pointer that
244 * will be called when our sub-device finishes probing.
331 * @done_probing: Callback functions to call after EP device finishes probing.
/openbmc/linux/drivers/base/test/
H A DKconfig3 tristate "Build kernel module to test asynchronous driver probing"
7 testing asynchronous driver probing by the device core.
/openbmc/linux/sound/soc/sof/
H A Dsof-client-probes-ipc3.c50 * ipc3_probes_init - initialize data probing
60 * Probing is initialized only once and each INIT request must be
85 * ipc3_probes_deinit - cleanup after data probing
170 * transfer data from or to target stream given the probing purpose.
H A Dsof-client-probes-ipc4.c92 * ipc4_probes_init - initialize data probing
103 * Probing is initialized only once and each INIT request must be
137 * ipc4_probes_deinit - cleanup after data probing
/openbmc/linux/tools/perf/util/
H A Dprobe-event.h65 /* Perf probe probing point */
76 /* Perf probe probing argument field chain */
84 /* Perf probe probing argument */
93 /* Perf probe probing event (point + arg) */
/openbmc/linux/net/tipc/
H A Dmonitor.c227 /* Loss of local node must be detected by active probing */ in mon_identify_lost_members()
231 /* Start probing if member was removed from applied domain */ in mon_identify_lost_members()
493 bool probing = state->probing; in tipc_mon_rcv() local
496 state->probing = false; in tipc_mon_rcv()
519 if (!more(new_gen, state->peer_gen) && !probing) in tipc_mon_rcv()
527 /* Peer is confirmed, stop any ongoing probing */ in tipc_mon_rcv()
607 state->probing = false; in tipc_mon_get_state()
613 if (!state->probing && in tipc_mon_get_state()
621 state->probing = state->acked_gen != mon->dom_gen; in tipc_mon_get_state()
622 state->probing |= peer->down_cnt; in tipc_mon_get_state()
H A Dmonitor.h47 * @probing: peer endpoint should be temporarily probed for potential loss
55 bool probing :1; member
/openbmc/u-boot/drivers/video/rockchip/
H A DKconfig29 framebuffer during device-model binding/probing.
38 framebuffer during device-model binding/probing.
/openbmc/linux/arch/x86/pci/
H A Dlegacy.c3 * legacy.c - traditional, old school PCI bus probing
32 pr_info("PCI: Probing PCI hardware\n"); in pci_legacy_init()
/openbmc/linux/kernel/irq/
H A Dautoprobe.c5 * This file contains the interrupt probing code and driver APIs.
26 * Commence probing for an interrupt. The interrupts are scanned
49 * Some chips need to know about probing in in probe_irq_on()
/openbmc/linux/drivers/mtd/maps/
H A Dlantiq-flash.c29 * map. The workaround involves swapping all addresses whilst probing the chip.
30 * Once probing is complete we stop swapping the addresses but swizzle the
145 dev_err(&pdev->dev, "probing failed\n"); in ltq_mtd_probe()
H A Dsolutionengine.c46 printk(KERN_NOTICE "Probing for flash chips at 0x00000000:\n"); in init_soleng_maps()
50 printk(KERN_NOTICE "Probing for flash chips at 0x01000000:\n"); in init_soleng_maps()
/openbmc/u-boot/drivers/mtd/
H A DKconfig30 for probing the capabilities of flash devices. If you wish to
41 for probing the capabilities of flash devices. If you wish to
/openbmc/linux/Documentation/fb/
H A Dintel810.rst54 - Supports EDID probing either by DDC/I2C or through the BIOS
102 be equal to hsync2. If EDID probing is successful, these will be
111 rate. If EDID probing is successful, these will be ignored and values
250 e. If you want support for DDC/I2C probing (Plug and Play Displays),
/openbmc/linux/drivers/mtd/chips/
H A DKconfig12 for probing the capabilities of flash devices. If you wish to
22 This option enables JEDEC-style probing of flash chips which are not
227 This option enables support for a dummy probing driver used to
/openbmc/linux/Documentation/i2c/
H A Dinstantiating-devices.rst188 probing.
199 probed, will be probed. For example this avoids probing for hardware
214 * Probing is only one way to instantiate I2C devices now, while it was the
221 that no probing happens. The purpose of the class bitfield is to limit
/openbmc/linux/sound/soc/intel/avs/boards/
H A DKconfig91 tristate "Probing (data) board"
95 This adds support for data probing board which can be used to
/openbmc/linux/net/batman-adv/
H A Dbat_v_elp.c181 * batadv_v_elp_wifi_neigh_probe() - send link probing packets to a neighbour
201 /* this probing routine is for Wifi neighbours only */ in batadv_v_elp_wifi_neigh_probe()
300 * probing/sampling to each neighbor in batadv_v_elp_periodic_work()
303 * probing packets at point 1) could still be in the HW queue) in batadv_v_elp_periodic_work()
308 /* if something goes wrong while probing, better to stop in batadv_v_elp_periodic_work()
/openbmc/linux/drivers/net/
H A DSpace.c35 * are then used in the device probing.
86 * later in the device probing.
115 * later in the device probing.
/openbmc/linux/Documentation/riscv/
H A Dhwprobe.rst3 RISC-V Hardware Probing Interface
6 The RISC-V hardware probing interface is based around a single syscall, which
/openbmc/linux/arch/x86/boot/
H A Dvideo.h10 * Header file for the real-mode video probing code
76 int unsafe; /* Probing is unsafe, only do after "scan" */

12345678910>>...38