Searched refs:detected (Results 1 – 25 of 290) sorted by relevance
12345678910>>...12
| /Linux-v5.4/scripts/kconfig/tests/err_recursive_dep/ |
| D | expected_stderr | 1 Kconfig:11:error: recursive dependency detected!
6 Kconfig:5:error: recursive dependency detected!
11 Kconfig:17:error: recursive dependency detected!
17 Kconfig:32:error: recursive dependency detected!
23 Kconfig:37:error: recursive dependency detected!
29 Kconfig:60:error: recursive dependency detected!
34 Kconfig:51:error: recursive dependency detected!
|
| /Linux-v5.4/tools/perf/ |
| D | Makefile.config | 15 $(shell printf "" > $(OUTPUT).config-detected)
16 detected = $(shell echo "$(1)=y" >> $(OUTPUT).config-detected)
17 detected_var = $(shell echo "$(1)=$($(1))" >> $(OUTPUT).config-detected)
38 $(call detected,CONFIG_X86)
44 $(call detected,CONFIG_X86_64)
78 $(call detected,CONFIG_PERF_REGS)
418 $(call detected,CONFIG_SETNS)
430 $(call detected,CONFIG_LIBOPENCSD)
443 $(call detected,CONFIG_LIBELF)
471 $(call detected,CONFIG_DWARF)
[all …]
|
| D | .gitignore | 31 .config-detected
|
| /Linux-v5.4/drivers/parport/ |
| D | daisy.c | 94 int detected = 0; in parport_daisy_init() local
142 detected += assign_addrs(port); in parport_daisy_init()
151 detected++; in parport_daisy_init()
156 if (!detected && !last_try) { in parport_daisy_init()
171 return detected; in parport_daisy_init()
405 int detected; in assign_addrs() local
469 detected = numdevs - thisdev; in assign_addrs()
471 detected); in assign_addrs()
481 return detected; in assign_addrs()
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-driver-hid-wiimote | 24 supported and if detected, it's no longer reported as static
34 done. This file shows the detected device type. "pending" means
36 device couldn't be detected or loaded. "generic" means, that the
37 device couldn't be detected but supports basic Wii Remote
50 Description: This attribute is only provided if the device was detected as a
65 Description: This attribute is only provided if the device was detected as a
74 Calibration data is detected by the kernel during device setup.
|
| D | sysfs-platform-dfl-fme | 52 Description: Read-Write. Read this file for errors detected on pcie0 link.
61 Description: Read-Write. Read this file for errors detected on pcie1 link.
70 Description: Read-only. It returns non-fatal errors detected.
76 Description: Read-only. It returns catastrophic and fatal errors detected.
91 Description: Read-Write. Read this file to get errors detected on FME.
100 Description: Read-only. Read this file to get the first error detected by
107 Description: Read-only. Read this file to get the second error detected by
|
| D | sysfs-class-fpga-manager | 50 * reconfig operation error - invalid operations detected by
54 * reconfig CRC error - CRC error detected by
58 * reconfig IP protocol error - protocol errors detected by
60 * reconfig fifo overflow error - FIFO overflow detected by
|
| D | sysfs-class-power-twl4030 | 7 "auto" - draw power as appropriate for detected
26 "auto" - draw power as appropriate for detected
|
| D | sysfs-bus-iio-temperature-max31856 | 9 has been detected.
10 '0' = No open circuit or broken thermocouple wires are detected
|
| D | sysfs-block-device | 13 detected.
15 every 10ms when activity is detected.
|
| /Linux-v5.4/Documentation/media/uapi/v4l/ |
| D | vidioc-query-dv-timings.rst | 54 timings are detected. Instead, drivers should send the
60 :ref:`VIDIOC_QUERY_DV_TIMINGS`, and if the detected timings are valid they
64 If the timings could not be detected because there was no signal, then
65 ENOLINK is returned. If a signal was detected, but it was unstable and
87 No timings could be detected because no signal was found.
|
| D | vidioc-querystd.rst | 50 between 50 and 60 Hz systems. If no signal was detected, then the driver
58 automatically if a new video standard is detected. Instead, drivers
64 will have to call :ref:`VIDIOC_QUERYSTD`, and if the detected video
|
| D | dev-rds.rst | 57 Whether an RDS signal is present can be detected by looking at the
59 ``V4L2_TUNER_SUB_RDS`` will be set if RDS data was detected.
187 - A bit error was detected but corrected.
|
| /Linux-v5.4/Documentation/devicetree/bindings/power/supply/ |
| D | max8903-charger.txt | 5 - dok-gpios: Valid DC power has been detected (active low, input), optional if uok-gpios is provided
6 - uok-gpios: Valid USB power has been detected (active low, input), optional if dok-gpios is provid…
|
| D | tps65090.txt | 7 -ti,enable-low-current-chrg: Enables charging when a low current is detected
|
| D | lego_ev3_battery.txt | 6 detected by a key switch in the battery compartment.
|
| /Linux-v5.4/Documentation/devicetree/bindings/mfd/ |
| D | ab8500.txt | 42 : VBUS_DET_F : : VBUS falling detected
43 : VBUS_DET_R : : VBUS rising detected
48 : VBUS_OVV : : Overvoltage on Vbus ball detected (USB charge is stopped)
49 : CH_WD_EXP : : Charger watchdog detected
|
| /Linux-v5.4/Documentation/core-api/ |
| D | debug-objects.rst | 32 detected problems so the kernel can continue to work and the debug
56 Each detected error is reported in the statistics and a limited number
185 usage of the object is detected by the other debug checks.
214 debug_object_init is detected. The function takes the address of the
232 debug_object_activate is detected.
260 debug_object_destroy is detected.
273 debug_object_free is detected. Further it can be called from the debug
274 checks in kfree/vfree, when an active object is detected from the
289 debug_object_assert_init is detected.
|
| /Linux-v5.4/Documentation/devicetree/bindings/bus/ |
| D | brcm,bus-axi.txt | 9 The cores on the AXI bus are automatically detected by bcma with the
19 detected (e.g. IRQ numbers). Also some of the cores may be responsible
|
| /Linux-v5.4/scripts/kconfig/tests/err_recursive_inc/ |
| D | expected_stderr | 1 Recursive inclusion detected.
|
| /Linux-v5.4/Documentation/driver-api/soundwire/ |
| D | error_handling.rst | 11 The errors can be detected with multiple mechanisms:
21 and after a number of such errors are detected the bus might be reset. Note
26 identify Slaves which detected a Bus Clash or a Parity Error, but they may
|
| /Linux-v5.4/Documentation/devicetree/bindings/input/touchscreen/ |
| D | cyttsp.txt | 25 before movement is detected and reported by the device.
34 touches are detected before entering low-power mode.
|
| /Linux-v5.4/Documentation/scsi/ |
| D | g_NCR5380.txt | 22 This driver provides some information on what it has detected in
23 /proc/scsi/g_NCR5380/x where x is the scsi card number as detected at boot
|
| /Linux-v5.4/Documentation/i2c/ |
| D | gpio-fault-injection.rst | 101 should be corrupted and that should be detected properly. That means that the
104 should be detected beforehand. Also note, that SCL going down is monitored
124 This file is write only and you need to write the delay between the detected
129 Start of a transfer is detected by waiting for SCL going down by the master
|
| /Linux-v5.4/Documentation/w1/masters/ |
| D | ds2482.rst | 33 However, the device cannot be detected without writing to the i2c bus, so no
|
12345678910>>...12
