On Thu, Sep 02, 2021 at 08:54:11PM +0800, fengchengwen wrote: > When some hardware is faulty, the error code cannot be set, and it just stops > working. > In addition, interrupts are generally not enabled. Therefore, for such > hardware, the > framework needs to have a mechanism to transmit the status so that > applications can > sense the status. > > So how about extend vchan_idle to vchan_status, include: idle, running, > error-stop ? >
We can look at changing that. By "idle" I originally meant "non-active", meaning that it's either halted or idle, but I think we can separate out those two into separate items like you suggest. /Bruce
