Lines Matching full:a

17    restarting from a known position. In the case of such errors outside of a
21    and after a number of such errors are detected the bus might be reset. Note
24    be distinguished, although a recurring bus clash when audio is enabled is a
25    indication of a bus allocation issue. The interrupt mechanism can also help
26    identify Slaves which detected a Bus Clash or a Parity Error, but they may
27    not be responsible for the errors so resetting them individually is not a
30 2. Command status: Each command is associated with a status, which only
33    current frame. A NAK indicates that the command was in error and will not
34    be applied. In case of a bad programming (command sent to non-existent
35    Slave or to a non-implemented register) or electrical issue, no response
36    signals the command was ignored. Some Master implementations allow for a
38    backtracking and restarting the entire programming sequence might be a
39    solution. Alternatively some implementations might directly issue a bus
42 3. Timeouts: In a number of cases such as ChannelPrepare or
43    ClockStopPrepare, the bus driver is supposed to poll a register field until
44    it transitions to a NotFinished value of zero. The MIPI SoundWire spec 1.1
47    driver will return a -ETIMEOUT. Such timeouts are symptoms of a faulty
53 1. BankSwitch: An error during the last command issuing a BankSwitch is
55    possible in a single segment setup, but this can lead to synchronization
56    problems when enabling multiple bus segments (a command with side effects
57    such as frame reconfiguration would be handled at different times). A global
60 Note that SoundWire does not provide a mechanism to detect illegal values
61 written in valid registers. In a number of cases the standard even mentions
63 implementation does not provide a recovery mechanism for such errors, Slave