Searched full:cause (Results 1 – 25 of 362) sorted by relevance
12345678910>>...15
| /Documentation/devicetree/bindings/watchdog/ |
| D | men-a021-wdt.txt | 9 4: Watchdog reset cause bit 0
10 5: Watchdog reset cause bit 1
11 6: Watchdog reset cause bit 2
|
| /Documentation/devicetree/bindings/i2c/ |
| D | mellanox,i2c-mlxbf.txt | 10 2) Cause master registers.
11 3) Cause slave registers.
12 4) Cause coalesce registers (if compatible isn't set
|
| /Documentation/ABI/testing/ |
| D | sysfs-devices-lpss_ltr | 19 is not "active", attempts to read from this attribute cause
31 is not "active", attempts to read from this attribute cause
43 is not "active", attempts to read from this attribute cause
|
| D | sysfs-bus-fsl-mc | 5 Writing a device location to this file will cause
18 Writing a device location to this file will cause the
|
| D | sysfs-class-zram | 14 RO attribute. Read operation will cause zram to add a new
|
| D | sysfs-platform-hidma-mgmt | 65 can also cause performance reduction to other peripherals
86 can also cause performance reduction to other peripherals
|
| /Documentation/core-api/ |
| D | unaligned-memory-access.rst | 15 unaligned accesses, why you need to write code that doesn't cause them,
73 platforms and will cause performance problems on others.
76 Code that does not cause unaligned access
95 not be unreasonable to expect that accessing field2 would cause an unaligned
111 will never cause an unaligned access, because all memory addresses are evenly
139 the memory access in a way that does not cause unaligned access. Of course,
140 the extra instructions obviously cause a loss in performance compared to the
149 that can cause an unaligned memory access. The following function taken
183 Here is another example of some code that could cause unaligned accesses::
192 This code will cause unaligned accesses every time the data parameter points
|
| /Documentation/ABI/stable/ |
| D | sysfs-driver-mlxreg-io | 93 Description: These files show the system reset cause, as following: power
97 this is reset cause, 0 - otherwise. Only one of the above
99 reset cause.
110 Description: These files show the system reset cause, as following: ComEx
113 Value 1 in file means this is reset cause, 0 - otherwise.
115 the last reset cause.
137 Description: These files show the system reset cause, as following:
141 reload. Value 1 in file means this is reset cause, 0 - otherwise.
143 only last reset cause.
|
| /Documentation/hwmon/ |
| D | tc654.rst | 32 Setting pwm1_mode to 1 will cause the pwm output to be driven based on
33 the pwm1 value. Setting pwm1_mode to 0 will cause the pwm output to be
|
| D | drivetemp.rst | 42 reading the drive temperature in this mode will not cause the drive to
61 this temperature may cause physical damage to the
66 this temperature may cause physical damage to the
|
| D | adc128d818.rst | 25 When the HOT Temperature Limit is crossed, this will cause an alarm that will
39 is read at least once. This means that the cause for the alarm may
|
| D | lm80.rst | 45 this will cause an alarm that will be reasserted until the temperature
67 is read at least once. This means that the cause for the alarm may
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | marvell,orion-intc.txt | 7 - reg: base address(es) of interrupt registers starting with CAUSE register
30 - reg: base address of bridge interrupt registers starting with CAUSE register
|
| /Documentation/admin-guide/ |
| D | xfs.rst | 96 cause problems for some applications that cannot handle
298 OR together the tags which represent errors which should cause panics:
325 Setting this to "1" will cause the "sync" flag set
330 Setting this to "1" will cause the "nodump" flag set
335 Setting this to "1" will cause the "noatime" flag set
340 Setting this to "1" will cause the "nosymlinks" flag set
345 Setting this to "1" will cause the "nodefrag" flag set
400 for a specific class will cause the error to be propagated rather than reset and
404 dependent - it may cause a shut down in the case of an unrecoverable error,
459 a single error, the first retry configuration that expires will cause the error
[all …]
|
| /Documentation/driver-api/md/ |
| D | raid5-cache.rst | 26 shutdown can cause data in some stripes to not be in consistent state, eg, data
41 doesn't cause data loss. Of course cache disk failure means the array is
63 disks later after specific conditions met. So cache disk failure will cause
67 the same data stored on cache disk, so a power loss doesn't cause data loss.
|
| /Documentation/devicetree/bindings/power/reset/ |
| D | keystone-reset.txt | 8 block. The Reset Mux block can be configured to cause reset or not.
29 - ti,wdt-list: WDT list that can cause SoC reset. It's not related
|
| /Documentation/networking/ |
| D | xfrm_sync.rst | 71 XFRM_AE_CR=16, /* Event cause is replay update */
72 XFRM_AE_CE=32, /* Event cause is timer expiry */
73 XFRM_AE_CU=64, /* Event cause is policy update */
76 message (kernel<->user) as well the cause (config, query or event).
|
| /Documentation/sound/cards/ |
| D | via82xx-mixer.rst | 6 Setting it to ``Input2`` on such boards will cause recording to hang, or fail
|
| /Documentation/driver-api/ |
| D | io_ordering.rst | 32 which could cause problems. Fixing it is easy enough though::
49 Here, the reads from safe_register will cause the I/O chipset to flush any
|
| /Documentation/arm/ |
| D | mem_alignment.rst | 28 space, and might cause programs to fail unexpectedly.
37 will cause the kernel to print a message indicating
|
| /Documentation/security/ |
| D | sak.rst | 86 These commands cause **all** daemons which are launched by the
89 delete these lines, but this may cause system management
|
| /Documentation/powerpc/ |
| D | transactional_memory.rst | 61 abort handler can check the cause of the failure, and retry.
92 give the appearance of success) or perform operations that cause transaction
174 Failure cause codes used by kernel
223 transaction when tm suspend occurs. So tsuspend will cause a
225 cause the transaction to be aborted and rolled back and the exception
|
| /Documentation/filesystems/ |
| D | locks.rst | 24 This should not cause problems for anybody, since everybody using a
39 over time, or under a very heavy mail load, would eventually cause the kernel
|
| /Documentation/x86/x86_64/ |
| D | machinecheck.rst | 8 by the CPU. Uncorrected errors typically cause a machine check
9 (often with panic), corrected ones cause a machine check log entry.
|
| /Documentation/x86/ |
| D | pti.rst | 144 kernel entry code. In general, old kernels might cause these tests
164 Bugs in PTI cause a few different signatures of crashes
170 in the trampoline code or mappings cause these.
178 careful and can be the cause of crashes that show up when
|
12345678910>>...15