Reviewed-by: Maulik Shah
Thanks,
Maulik
On 5/28/2020 8:18 PM, Douglas Anderson wrote:
The write_tcs_reg_sync() may be called after timekeeping is suspended
so it's not OK to use ktime. The readl_poll_timeout_atomic() macro
implicitly uses ktime. This was causing a warning at suspend time.
Bjorn and Andy,
On Thu, May 28, 2020 at 7:48 AM Douglas Anderson wrote:
>
> The write_tcs_reg_sync() may be called after timekeeping is suspended
> so it's not OK to use ktime. The readl_poll_timeout_atomic() macro
> implicitly uses ktime. This was causing a warning at suspend time.
>
> Change
Hi,
On Thu, May 28, 2020 at 3:44 PM Stephen Boyd wrote:
>
> Quoting Douglas Anderson (2020-05-28 07:48:34)
> > The write_tcs_reg_sync() may be called after timekeeping is suspended
> > so it's not OK to use ktime. The readl_poll_timeout_atomic() macro
> > implicitly uses ktime. This was
Quoting Douglas Anderson (2020-05-28 07:48:34)
> The write_tcs_reg_sync() may be called after timekeeping is suspended
> so it's not OK to use ktime. The readl_poll_timeout_atomic() macro
> implicitly uses ktime. This was causing a warning at suspend time.
>
> Change to just loop 100 times
The write_tcs_reg_sync() may be called after timekeeping is suspended
so it's not OK to use ktime. The readl_poll_timeout_atomic() macro
implicitly uses ktime. This was causing a warning at suspend time.
Change to just loop 100 times with a delay of 1 us between loops.
This may give a
5 matches
Mail list logo