In current android code,there are two way in surfaceflinger to respond
when PM need to turn off display:
1.User virtual console:
status_t DisplayHardwareBase::ConsoleManagerThread::releaseScreen()
const
{
int fd = this->consoleFd;
int err = ioctl(fd, VT_RELDISP, (void*)1);
LOGE_IF(err<0, "ioctl(%d, VT_RELDISP, 1) failed %d (%s)",
fd, errno, strerror(errno));
return (err<0) ? (-errno) : status_t(NO_ERROR);
}
2.User framebuffer
status_t DisplayHardwareBase::DisplayEventThread::releaseScreen()
const
{
mBarrier.open();
return NO_ERROR;
}
The way to use is depend on two fb device file and fbcon folder. If
the two files exist and the folder not, SurfaceFlinger will use the
second way, otherwise use the first way.
The question is:
If the second ways is used,there's no code to turn off display. Is
it an incomplete code or does android will turn off display in other
place for such case?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"android-framework" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-framework?hl=en
-~----------~----~----~----~------~----~------~--~---
