| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-bus-pci | 47 Upon successfully adding an ID, the driver will probe
298 element. Drivers have the ability at probe time to reduce the
|
| H A D | sysfs-bus-usb | 45 Upon successfully adding an ID, the driver will probe
|
| H A D | sysfs-class-cxl | 25 requested by userspace. The default on probe is the maximum
|
| H A D | sysfs-devices-system-cpu | 40 What: /sys/devices/system/cpu/probe
48 probe: writes to this file will dynamically add a CPU to the
|
| H A D | sysfs-devices-waiting_for_supplier | 12 before the device can probe.
15 to be added before it can probe. A value of 1 means the device
17 probe.
|
| /linux/Documentation/PCI/ |
| H A D | pci-error-recovery.rst | 317 set the needs_freset bit in the pci_dev structure in their probe function.
|
| H A D | pci-iov-howto.rst | 166 .probe = dev_probe,
|
| H A D | pci.rst | 112 Once added, the driver probe routine will be invoked for any unclaimed
|
| H A D | pciebus-howto.rst | 144 .probe = aerdrv_load,
|
| /linux/Documentation/admin-guide/blockdev/ |
| H A D | paride.rst | 120 All parports and all protocol drivers are probed automatically unless probe=0
133 mode mode number (protocol-specific) or -1 for probe
|
| /linux/Documentation/admin-guide/ |
| H A D | kernel-parameters.txt | 1041 probe. Only specific dependencies (subsystems or
1648 to enforce probe and suspend/resume ordering.
1663 probe successfully.
2574 kprobe_event=[probe-list]
2576 The probe-list is a semicolon delimited list of probe
3529 probe on this module. Otherwise, enable/disable
4274 Set to non-zero to probe primary and secondary ISA
4328 Set to non-zero to probe tertiary and further ISA
4349 Set to non-zero to probe Winbond controllers. Use
4395 off [X86] don't probe for the PCI bus
[all …]
|
| H A D | parport.rst | 59 Parport probe [optional]
70 The probe information is available from files in ``/proc/sys/dev/parport/``.
|
| H A D | pnp.rst | 233 2. Optionally define probe and remove functions. It may make sense not to
261 .probe = serial_pnp_probe,
|
| /linux/Documentation/admin-guide/media/ |
| H A D | philips.rst | 207 2 0x2 probe() and disconnect() traces On
|
| /linux/Documentation/admin-guide/mm/ |
| H A D | memory-hotplug.rst | 118 The probe interface is located at::
120 /sys/devices/system/memory/probe
125 % echo addr > /sys/devices/system/memory/probe
132 Using the probe interface is discouraged as it is easy to crash the kernel,
288 ``probe`` write-only: add (probe) selected memory blocks manually
|
| /linux/Documentation/arch/arm/ |
| H A D | interrupts.rst | 100 - flags indicating what we can do with this IRQ (valid, probe,
139 Set the valid/probe/noautoenable flags.
|
| /linux/Documentation/arch/arm64/ |
| H A D | arm-acpi.rst | 268 Drivers should determine their probe() type by checking for a null
450 else must be discovered by the driver probe function. Then, have the rest
453 the probe function instead of being scattered throughout the driver. For
481 /* Continue with any generic probe operations */
|
| /linux/Documentation/arch/powerpc/ |
| H A D | booting.rst | 28 kernel can then probe those and match drivers to device, without having to hard
|
| /linux/Documentation/arch/s390/ |
| H A D | cds.rst | 52 * The oper_handler is (kindof) replaced by the probe() and set_online() functions
149 This methods implies that Linux/390 doesn't require to probe for free (not
|
| H A D | driver-model.rst | 102 int (*probe) (struct ccw_device *);
131 probe:
139 int (*probe) (struct ccw_device *cdev);
|
| H A D | vfio-ap.rst | 233 | | 8 probe | |
258 driver's probe and remove callback interfaces. Devices older than CEX4 queues
295 | +---------+ | probe()/remove() +--------------+ APIs
|
| H A D | vfio-ccw.rst | 154 | +---------+ | probe()/remove() +--------------+ APIs
179 vfio_mdev is also the vfio device driver. It will probe the mdev and
|
| /linux/Documentation/arch/x86/ |
| H A D | cpuinfo.rst | 23 said CPU supports CPUID faulting - userspace can simply probe for the
|
| H A D | earlyprintk.rst | 127 c) On Nvidia Southbridge based systems: the kernel will try to probe
|
| /linux/Documentation/bpf/ |
| H A D | bpf_devel_QA.rst | 610 LLVM has an option to select ``-mcpu=probe`` where it will probe the host
620 probe - Select the probe processor.
627 extensions such that ``-mcpu=probe`` users can benefit from the
633 By the way, the BPF kernel selftests run with ``-mcpu=probe`` for better
|