hwc: reduce blank ioctl EBUSY from error to info

EBUSY means the screen is already in the requested state.  This happens
during normal initialization and isn't harmful in practice.

Bug: 7249087
Change-Id: Ic8b6078aadd48d776191523e9696455d68b6ac62
Signed-off-by: Greg Hackmann <ghackmann@google.com>

diff --git a/libhwc/hwc.cpp b/libhwc/hwc.cpp
index 15db935541854e5f8ffaa482b9336e43d96f3b92..bde56fea7fd86222e7431e70a9975b299523dd85 100644 (file)
--- a/libhwc/hwc.cpp
+++ b/libhwc/hwc.cpp
@@ -1547,7 +1547,12 @@ static int exynos5_blank(struct hwc_composer_device_1 *dev, int dpy, int blank)
     int fb_blank = blank ? FB_BLANK_POWERDOWN : FB_BLANK_UNBLANK;
     int err = ioctl(pdev->fd, FBIOBLANK, fb_blank);
     if (err < 0) {
-        ALOGE("%sblank ioctl failed", blank ? "" : "un");
+        if (errno == EBUSY)
+            ALOGI("%sblank ioctl failed (display already %sblanked)",
+                    blank ? "" : "un", blank ? "" : "un");
+        else
+            ALOGE("%sblank ioctl failed: %s", blank ? "" : "un",
+                    strerror(errno));
         return -errno;
     }