Lines Matching refs:fault

1 This is a summary of the most important conventions for use of fault
7 Not all fault reports imply errors; "page faults" should be a familiar
11 recovery, triggered by a fault report, there is no error.
13 In a similar way, sometimes a "fault" code just reports one defined
19 the right fault code, so that it can (in turn) behave correctly.
22 I2C and SMBus fault codes
25 some positive number indicating a non-fault return.  The specific
32 cases (unless the hardware doesn't provide unique fault reports).
51 	fault is only reported on read transactions; the SMBus slave
59 	SMBus adapter) needs some fault recovery (such as resetting),
65 	specific fault code when you can.
69 	performing an I/O operation.  Use a more specific fault