On Mon, 04 Mar 2024, "Chauhan, Shekhar" wrote:
> On 3/4/2024 14:16, Jani Nikula wrote:
>> I did not ask for this. I would rather all platforms used 2 ms. I even
>> said the original change looked fine. But I'd like it to be explained in
>> the commit message.
> I felt that when you said "why bump
On 3/4/2024 14:16, Jani Nikula wrote:
On Mon, 04 Mar 2024, Shekhar Chauhan wrote:
Currently, the driver is only waiting for 1ms for
idle patterns. But starting from LNL and beyond,
the MST wants the driver to wait for 1640us before
What does it mean that "the MST wants"?
I wanted to convey t
On Mon, 04 Mar 2024, Shekhar Chauhan wrote:
> Currently, the driver is only waiting for 1ms for
> idle patterns. But starting from LNL and beyond,
> the MST wants the driver to wait for 1640us before
What does it mean that "the MST wants"?
> timing out (which we round up to 2ms).
>
> v1: Introdu
Currently, the driver is only waiting for 1ms for
idle patterns. But starting from LNL and beyond,
the MST wants the driver to wait for 1640us before
timing out (which we round up to 2ms).
v1: Introduced the 2ms wait timeout.
v2: Segregated the wait timeout for platforms before & after LNL.
v3: Fi
