/Linux-v5.15/drivers/base/ |
D | dd.c | 43 * request probing to be deferred by returning -EPROBE_DEFER from its probe hook 66 * to prohibit probing of devices as it could be unsafe. 78 * deferred_probe_work_func() - Retry probing devices in the active list. 108 * Drop the mutex while probing each device; the probe path may in deferred_probe_work_func() 157 * driver_deferred_probe_trigger() - Kick off re-probing deferred devices 164 * more than one device is probing at the same time, it is possible for one 170 * trigger has occurred in the midst of probing a driver. If the trigger count 200 * It will disable probing of devices and defer their probes instead. 212 * It will restore normal behavior and trigger re-probing of deferred 319 * deferred_probe_initcall() - Enable probing of deferred devices [all …]
|
/Linux-v5.15/Documentation/driver-api/ |
D | eisa.rst | 25 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
|
D | device_link.rst | 64 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.
|
/Linux-v5.15/drivers/base/test/ |
D | Kconfig | 3 tristate "Build kernel module to test asynchronous driver probing" 7 testing asynchronous driver probing by the device core.
|
/Linux-v5.15/Documentation/ide/ |
D | ide.rst | 82 Drives are normally found by auto-probing and/or examining the CMOS/BIOS data. 96 The results of successful auto-probing may override the physical geometry/irq 100 If the auto-probing during boot time confuses a drive (ie. the drive works 191 you need to explicitly enable probing by using "probe" kernel parameter, 192 i.e. to enable probing for ALI M14xx chipsets (ali14xx host driver) use: 200 kernel paremeter to enable probing for VLB version of the chipset (PCI ones 227 * "noprobe=[interface_number.device_number]" to skip probing
|
/Linux-v5.15/net/tipc/ |
D | monitor.c | 227 /* 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() 517 if (!more(new_gen, state->peer_gen) && !probing) in tipc_mon_rcv() 525 /* Peer is confirmed, stop any ongoing probing */ in tipc_mon_rcv() 605 state->probing = false; in tipc_mon_get_state() 611 if (!state->probing && in tipc_mon_get_state() 619 state->probing = state->acked_gen != mon->dom_gen; in tipc_mon_get_state() 620 state->probing |= peer->down_cnt; in tipc_mon_get_state()
|
D | monitor.h | 47 * @probing: peer endpoint should be temporarily probed for potential loss 55 bool probing :1; member
|
/Linux-v5.15/tools/perf/util/ |
D | probe-event.h | 65 /* Perf probe probing point */ 76 /* Perf probe probing argument field chain */ 84 /* Perf probe probing argument */ 93 /* Perf probe probing event (point + arg) */
|
/Linux-v5.15/sound/soc/sof/ |
D | probe.c | 15 * sof_ipc_probe_init - initialize data probing 25 * Probing is initialized only once and each INIT request must be 53 * sof_ipc_probe_deinit - cleanup after data probing 125 * extractor (dma) and it is always assigned on probing init. 232 * transfer data from or to target stream given the probing purpose.
|
/Linux-v5.15/kernel/irq/ |
D | autoprobe.c | 5 * 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()
|
/Linux-v5.15/arch/x86/pci/ |
D | legacy.c | 3 * legacy.c - traditional, old school PCI bus probing 32 pr_info("PCI: Probing PCI hardware\n"); in pci_legacy_init()
|
/Linux-v5.15/Documentation/fb/ |
D | intel810.rst | 54 - 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),
|
/Linux-v5.15/drivers/mtd/maps/ |
D | solutionengine.c | 46 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()
|
D | lantiq-flash.c | 29 * map. The workaround involves swapping all addresses whilst probing the chip. 30 * Once probing is complete we stop swapping the addresses but swizzle the 150 dev_err(&pdev->dev, "probing failed\n"); in ltq_mtd_probe()
|
/Linux-v5.15/drivers/mtd/chips/ |
D | Kconfig | 12 for probing the capabilities of flash devices. If you wish to 22 This option enables JEDEC-style probing of flash chips which are not 225 This option enables support for a dummy probing driver used to
|
/Linux-v5.15/Documentation/i2c/ |
D | instantiating-devices.rst | 180 probing. 191 probed, will be probed. For example this avoids probing for hardware 206 * Probing is only one way to instantiate I2C devices now, while it was the 213 that no probing happens. The purpose of the class bitfield is to limit
|
/Linux-v5.15/drivers/hid/ |
D | hid-uclogic-params.c | 751 "transition firmware detected, not probing pen v2 parameters\n"); in uclogic_params_huion_init() 757 "failed probing pen v2 parameters: %d\n", rc); in uclogic_params_huion_init() 784 "failed probing pen v1 parameters: %d\n", rc); in uclogic_params_huion_init() 793 hid_err(hdev, "v1 buttonpad probing failed: %d\n", rc); in uclogic_params_huion_init() 907 "pen probing failed: %d\n", in uclogic_params_init() 1015 hid_err(hdev, "pen probing failed: %d\n", rc); in uclogic_params_init() 1034 hid_err(hdev, "pen probing failed: %d\n", rc); in uclogic_params_init() 1062 hid_err(hdev, "pen probing failed: %d\n", rc); in uclogic_params_init() 1096 hid_err(hdev, "pen probing failed: %d\n", rc); in uclogic_params_init()
|
/Linux-v5.15/net/batman-adv/ |
D | bat_v_elp.c | 183 * batadv_v_elp_wifi_neigh_probe() - send link probing packets to a neighbour 203 /* this probing routine is for Wifi neighbours only */ in batadv_v_elp_wifi_neigh_probe() 302 * probing/sampling to each neighbor in batadv_v_elp_periodic_work() 305 * probing packets at point 1) could still be in the HW queue) in batadv_v_elp_periodic_work() 310 /* if something goes wrong while probing, better to stop in batadv_v_elp_periodic_work()
|
/Linux-v5.15/drivers/net/ |
D | Space.c | 35 * are then used in the device probing. 86 * later in the device probing. 115 * later in the device probing.
|
/Linux-v5.15/tools/bpf/bpftool/Documentation/ |
D | bpftool-feature.rst | 50 specified, probing the kernel is the default behaviour. 67 same role as when probing the kernel.
|
/Linux-v5.15/arch/x86/boot/ |
D | video.h | 10 * Header file for the real-mode video probing code 76 int unsafe; /* Probing is unsafe, only do after "scan" */
|
/Linux-v5.15/Documentation/driver-api/driver-model/ |
D | overview.rst | 26 of common callbacks, such as device discovery during bus probing, bus 115 The bus layer may also create files for the devices it finds while probing the
|
/Linux-v5.15/Documentation/ABI/testing/ |
D | sysfs-class-devlink | 76 - 'consumer probing' 91 'consumer probing' means the consumer device is currently
|
/Linux-v5.15/drivers/block/ |
D | ataflop.c | 32 * - When probing the floppies we should add the FDCCMDADD_H flag since 400 * while Probing is set. fd_rwsec_done() clears it after a 403 static int Probing = 0; variable 1155 if (Probing) { in fd_rwsec_done1() 1163 Probing = 0; in fd_rwsec_done1() 1169 Probing=0; in fd_rwsec_done1() 1172 /* record not found, but not probing. Maybe stretch wrong ? Restart probing */ in fd_rwsec_done1() 1177 Probing = 1; in fd_rwsec_done1() 1180 if (Probing) { in fd_rwsec_done1() 1206 Probing = 0; in fd_rwsec_done1() [all …]
|
/Linux-v5.15/Documentation/sound/hd-audio/ |
D | notes.rst | 93 Codec-Probing Problem 95 A less often but a more severe problem is the codec probing. When 123 Since 2.6.29 kernel, the driver has a more robust probing method, so 165 hda_codec: ALC880: BIOS auto-probing. 184 support the automatic probing (yet as of 2.6.28). And, BIOS is often, 325 kernel messages at probing. 485 try probing multi-I/O config (e.g. shared line-in/surround, 759 probing, the proc file is available, so you can get the raw codec 857 at probing and operating the HD-audio driver.
|