On Fri, 22 Jan 2021 11:42:12 +0100
Cornelia Huck <> wrote:
> > > We could work around that by making a positive statement. Not telling,
> > > when the driver MUST NOT consider the reset completed, but tell when the
> > > driver SHOULD consider the reset completed.
>
> That could be
>
> "The driver SHOULD consider a driver-initiated reset complete when it
> reads the device status as 0."
Sounds good to me!
>
> > >
> > > The MUST NOT does not buy much to the driver. It knows, what is
> > > certainly wrong, but it still does not know what is right. What the
> > > driver needs is a criterion when the reset is certainly completed (so
> > > it can free up resources for example).
>
> Any further comments before I put together a v3 (without the RFC)?
> I also need to open a github issue for this.
No further comments. I think we are heading in the right direction.
Regards,
Halil
