diff options
| author | Tomi Valkeinen <tomi.valkeinen@nokia.com> | 2010-04-30 11:24:33 +0300 |
|---|---|---|
| committer | Tomi Valkeinen <tomi.valkeinen@nokia.com> | 2010-08-05 16:52:01 +0300 |
| commit | 9ecd96842bc6312fdb2f84b6379a6f92686e2fd0 (patch) | |
| tree | b96e69d5f3317cbafe60eac2cef59a42cb2b2914 /fs/btrfs/version.sh | |
| parent | d73701044b70924f450fc6b161d952b38b7d0182 (diff) | |
| download | kernel_samsung_tuna-9ecd96842bc6312fdb2f84b6379a6f92686e2fd0.zip kernel_samsung_tuna-9ecd96842bc6312fdb2f84b6379a6f92686e2fd0.tar.gz kernel_samsung_tuna-9ecd96842bc6312fdb2f84b6379a6f92686e2fd0.tar.bz2 | |
OMAP: DSS2: DSI: change dsi_vc_config_l4/vp()
Change dsi_vc_config_l4/vp() to loop for the VC_BUSY flag to change, and
return an error if it fails.
Busy looping is bad, but there's no interrupt that can be used for all the
cases where VC can be busy. So the caller should first try to make sure
that the VC is not busy, if possible, and then call dsi_vc_config_l4/vp().
Most notable case when the caller cannot be sure if the VC is busy is
after frame has been sent. Usually DSI buffers have been emptied until we
need to reconfig the VC, but in some rare cases the VC can still be busy,
and this patch will handle that case.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@nokia.com>
Diffstat (limited to 'fs/btrfs/version.sh')
0 files changed, 0 insertions, 0 deletions