Searched full:cleared (Results 1 – 25 of 186) sorted by relevance
12345678
| /Documentation/hwmon/ |
| D | ltc2992.rst | 39 inX_min_alarm An undervoltage occurred. Cleared on read.
40 inX_max_alarm An overvoltage occurred. Cleared on read.
47 currX_min_alarm An undercurrent occurred. Cleared on read.
48 currX_max_alarm An overcurrent occurred. Cleared on read.
55 powerX_min_alarm An underpower occurred. Cleared on read.
56 powerX_max_alarm An overpower occurred. Cleared on read.
|
| D | w83793.rst | 77 sure bit 0 is cleared in the 6 values. And then set the pwm1 value to
101 If the case open alarm triggers, it will stay in this state unless cleared
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-platform-devices-occ-hwmon | 7 the file is empty. The data is cleared when it's been
9 from the first error is saved, until it's cleared upon read. The OCC hwmon driver, running on
|
| D | sysfs-mce | 81 All corrected events are not cleared and kept in bank MSRs.
88 All reported corrected errors will be cleared silently.
|
| D | sysfs-bus-amba | 11 be cleared with an empty string (echo > driver_override).
|
| D | sysfs-bus-vmbus | 11 may be cleared with an empty string (echo > driver_override).
|
| D | sysfs-bus-iio-chemical-sunrise-co2 | 29 - 'error_no_measurement': Cleared at first measurement
|
| D | sysfs-bus-acpi | 76 Bit [3] Set if the device is functioning properly (cleared
79 Bits [31:5] Reserved (must be cleared)
|
| D | sysfs-devices-platform-ACPI-TAD | 39 is explicitly cleared via the ac_status attribute.
83 cleared through this attribute.
|
| D | sysfs-firmware-gsmi | 44 cleared.
|
| /Documentation/arch/parisc/ |
| D | debugging.rst | 39 happens when the Q bit is cleared is the CPU does not update the
44 instruction that cleared the Q bit, if you're not it points anywhere
|
| /Documentation/admin-guide/mm/ |
| D | soft-dirty.rst | 22 Internally, to do this tracking, the writable bit is cleared from PTEs
23 when the soft-dirty bit is cleared. So, after this, when the task tries to
|
| D | idle_page_tracking.rst | 69 their idle flag cleared in the interim.
101 section), and cleared automatically whenever a page is referenced as defined
104 When a page is marked idle, the Accessed bit must be cleared in all PTEs it is
109 cleared as a result of setting or updating a page's Idle flag, the Young flag
|
| D | nommu-mmap.rst | 53 memory and any extraneous space beyond the EOF will be cleared
122 be cleared by the kernel before being returned in accordance with the
127 to cleared physical pages when a write happens on that specific page
134 pages, and the entire map is cleared at allocation time. This can cause
|
| /Documentation/userspace-api/media/v4l/ |
| D | vidioc-g-dv-timings.rst | 112 the bit is set (1) it is positive polarity and if is cleared (0),
267 will also be cleared. This is a read-only flag, applications must
272 set. This flag is cleared otherwise. It is also only valid for
274 formats the flag will be cleared by the driver.
279 generate such frequencies, then the flag will be cleared.
314 cleared by transmitters.
|
| /Documentation/devicetree/bindings/powerpc/fsl/ |
| D | pmc.txt | 40 and cleared on suspend, and restored on resume. This sleep controller
44 which will be ORed into PMCDR upon suspend, and cleared from PMCDR
|
| /Documentation/devicetree/bindings/watchdog/ |
| D | microchip,pic32-wdt.txt | 4 WDT is not cleared periodically in software.
|
| D | dlg,da9062-watchdog.yaml | 37 watchdog timeout triggers SHUTDOWN, if cleared the watchdog triggers
|
| D | xlnx,xps-timebase-wdt.yaml | 18 cleared (by writing a one to the state bit) before the next
|
| D | starfive,jh7100-wdt.yaml | 19 isn't cleared, the watchdog will reset the system unless the watchdog
|
| /Documentation/scheduler/ |
| D | sched-arch.rst | 30 be cleared until the running task has called schedule(). Idle
58 an interrupt sleep, it needs to be cleared then a memory
|
| /Documentation/devicetree/bindings/mfd/ |
| D | max77620.txt | 54 When FPS event cleared (set to LOW), regulators, GPIOs and 32KHz
99 event cleared (set to LOW) whether it
109 event get cleared.
|
| /Documentation/filesystems/ |
| D | automount-support.rst | 66 The expiration flag is cleared by calls to mntput. This means that expiration
97 Again, the expiration flag is cleared every time anything other than umount()
|
| /Documentation/arch/powerpc/ |
| D | dawr-power9.rst | 83 cleared, all DAWR access should be cleared immediately and your
|
| /Documentation/devicetree/bindings/net/ |
| D | maxlinear,gpy2xx.yaml | 21 interrupt status register is cleared. Thus it is blocking the
|
12345678