# Re: \[PATCH\] Video : Amba: Use in\_interrupt() in clcdfb\_sleep().

- From: Alan Cox \<hidden\>
- Date: 2012-03-11 18:23:08 
- List: linux-fbdev
- Page: https://ratatoskr.run/linux-fbdev/2012/03/3833870
- Thread: https://ratatoskr.run/linux-fbdev/2012/03/3833822/t.md

```text
> As I've said, if we aren't going to use this, then the only solution is
> to completely omit the msleep() there and just say "sod you to running
> anything else for 20ms while this driver busy-spins."  That's
> ultimately the safe thing to do, and at the moment I see no other
> alternative there.

Anyone having this argument is also right now peeing into the wind. Quite
a few console drivers do this including some the big name x86 ones. We
don't seem to be getting any resulting problem reports.

Architecturally we really need a way to help console drivers separate the
civilised acceleration friendly, lock friendly output paths from printk.
That's the real fix, but a whole different matter to solve cleanly.

Alan
```