Searched refs:force_probe (Results 1 – 10 of 10) sorted by relevance
/openbmc/linux/drivers/eisa/ |
H A D | virtual_root.c | 22 static int force_probe = EISA_FORCE_PROBE_DEFAULT; variable 56 eisa_bus_root.force_probe = force_probe; in virtual_eisa_root_init() 70 module_param (force_probe, int, 0444);
|
H A D | eisa-bus.c | 328 if (!root->force_probe) in eisa_probe() 330 goto force_probe; in eisa_probe() 336 if (!root->force_probe) in eisa_probe() 338 goto force_probe; in eisa_probe() 350 force_probe: in eisa_probe()
|
/openbmc/linux/arch/mips/sni/ |
H A D | eisa.c | 29 .force_probe = 1,
|
/openbmc/linux/Documentation/gpu/rfc/ |
H A D | xe.rst | 48 However, the force_probe mechanism existent in both drivers will allow only one 55 i915.force_probe=!5690 xe.force_probe=5690 59 force_probe parameter while the driver is under development. This protection is 65 forever experimental and dependent on the usage of force_probe for these 70 Xe driver will be protected with both STAGING Kconfig and force_probe. Changes in 73 ‘no regression’ rule. Then force_probe will be lifted only for future platforms
|
/openbmc/linux/include/linux/ |
H A D | eisa.h | 98 int force_probe; /* Probe even when no slot 0 */ member
|
/openbmc/linux/drivers/gpu/drm/i915/ |
H A D | i915_params.h | 77 param(char *, force_probe, CONFIG_DRM_I915_FORCE_PROBE, 0400) \
|
H A D | i915_params.c | 127 i915_param_named_unsafe(force_probe, charp, 0400,
|
H A D | i915_pci.c | 984 return device_id_in_list(device_id, i915_modparams.force_probe, false); in id_forced() 989 return device_id_in_list(device_id, i915_modparams.force_probe, true); in id_blocked()
|
H A D | Kconfig | 63 This is the default value for the i915.force_probe module
|
/openbmc/linux/Documentation/driver-api/ |
H A D | eisa.rst | 60 int force_probe; /* Probe even when no slot 0 */ 72 force_probe Probe even when slot 0 is empty (no EISA mainboard) 196 virtual_root.force_probe
|