todo高通Android UEFI中的LCD分析（1）：启动流程分析
# 高通Android UEFI中的LCD分析（1）：启动流程
背景
之前学习的lk阶段点亮LCD的流程算是比较经典，但是高通已经推出了很多种基于UEFI方案的启动架构。
所以需要对这块比较新的技术进行学习。
同事遇到了一个UEFI阶段LCD显示异常，而kernel正常的问题；但我解决不了。
分析
在高通UEFI架构中，通过Protocol来调用对应的功能。因此实际上的函数调用并不是显式的，而是包裹在Protocol中进行。
高通UEFI显示有关的文件有：
BOOT.XF.4.1/boot_images/QcomPkg/Drivers/DisplayDxe/DisplayDxe.c
BOOT.XF.4.1/boot_images/QcomPkg/Application/QcomChargerApp/QcomChargerAppDisplay.c
BOOT.XF.4.1/boot_images/QcomPkg/Application/QcomChargerApp/QcomChargerAppDisplay.h
BOOT.XF.4.1/boot_images/QcomPkg/Drivers/DisplayDxe/DisplayDxe.c
BOOT.XF.4.1/boot_images/QcomPkg/Drivers/DisplayDxe/DisplayDxe.h
BOOT.XF.4.1/boot_images/QcomPkg/Drivers/DisplayDxe/DisplayDxe.inf
BOOT.XF.4.1/boot_images/QcomPkg/Drivers/DisplayDxe/DisplayPwrCtrlProtocol.c
BOOT.XF.4.1/boot_images/QcomPkg/Drivers/DisplayDxe/DisplayPwrProtocol.c
BOOT.XF.4.1/boot_images/QcomPkg/Include/Library/BootDisplay.h
BOOT.XF.4.1/boot_images/QcomPkg/Include/Library/DisplayLib.h
BOOT.XF.4.1/boot_images/QcomPkg/Include/Library/DisplayUtils.h
BOOT.XF.4.1/boot_images/QcomPkg/Include/Library/ExternalDisplayDriver.h
BOOT.XF.4.1/boot_images/QcomPkg/Include/Protocol/EFIDisplayPwr.h
BOOT.XF.4.1/boot_images/QcomPkg/Include/Protocol/EFIDisplayPwrCtrl.h
BOOT.XF.4.1/boot_images/QcomPkg/Include/Protocol/EFIDisplayUtils.h
BOOT.XF.4.1/boot_images/QcomPkg/Library/BootDisplayLib/BootDisplay.c
BOOT.XF.4.1/boot_images/QcomPkg/Library/BootDisplayLib/BootDisplayLib.inf
BOOT.XF.4.1/boot_images/QcomPkg/Library/DisplayLib/DisplayLib.c
BOOT.XF.4.1/boot_images/QcomPkg/Library/DisplayLib/DisplayLib.inf
BOOT.XF.4.1/boot_images/QcomPkg/Library/ExternalDisplayLib/ExtDisplay_driver.c
BOOT.XF.4.1/boot_images/QcomPkg/Library/ExternalDisplayLib/ExternalDisplayLib.dec
BOOT.XF.4.1/boot_images/QcomPkg/Library/ExternalDisplayLib/ExternalDisplayLib.inf
BOOT.XF.4.1/boot_images/QcomPkg/Library/ExternalDisplayLib/ExternalDisplayLibStub.inf
BOOT.XF.4.1/boot_images/QcomPkg/Include/Library/HALMDPLib.h
BOOT.XF.4.1/boot_images/QcomPkg/Include/Library/MDPLib.h
BOOT.XF.4.1/boot_images/QcomPkg/Include/Library/MDPPeripherals.h
BOOT.XF.4.1/boot_images/QcomPkg/Include/Library/MDPPlatformLib.h
BOOT.XF.4.1/boot_images/QcomPkg/Include/Library/MDPSystem.h
BOOT.XF.4.1/boot_images/QcomPkg/Include/Library/MDPTypes.h
BOOT.XF.4.1/boot_images/QcomPkg/Library/MDPLib/DisplayUtils.c
BOOT.XF.4.1/boot_images/QcomPkg/Library/MDPLib/MDPClocks.c
BOOT.XF.4.1/boot_images/QcomPkg/Library/MDPLib/MDPClocksBoot.c
BOOT.XF.4.1/boot_images/QcomPkg/Library/MDPLib/MDPConfig.c
BOOT.XF.4.1/boot_images/QcomPkg/Library/MDPLib/MDPEDID.c
BOOT.XF.4.1/boot_images/QcomPkg/Library/MDPLib/MDPLib.c
BOOT.XF.4.1/boot_images/QcomPkg/Library/MDPLib/MDPLib.inf
BOOT.XF.4.1/boot_images/QcomPkg/Library/MDPLib/MDPLibBoot.inf
BOOT.XF.4.1/boot_images/QcomPkg/Library/MDPLib/MDPLib_i.h
BOOT.XF.4.1/boot_images/QcomPkg/Library/MDPLib/MDPPanel.c
BOOT.XF.4.1/boot_images/QcomPkg/Library/MDPLib/MDPPeripherals.c
BOOT.XF.4.1/boot_images/QcomPkg/Library/MDPLib/MDPSystem.c
BOOT.XF.4.1/boot_images/QcomPkg/Library/MDPLib/MDPSystemBoot.c
BOOT.XF.4.1/boot_images/QcomPkg/Library/MDPLib/MDPVersion.c
BOOT.XF.4.1/boot_images/QcomPkg/Library/NullLibs/MDPPlatformLibNull/MDPPlatformLibNull.c
BOOT.XF.4.1/boot_images/QcomPkg/Library/NullLibs/MDPPlatformLibNull/MDPPlatformLibNull.inf
BOOT.XF.4.1/boot_images/QcomPkg/SocPkg/AgattiPkg/Library/MDPPlatformLib/MDPPlatformLib.c
BOOT.XF.4.1/boot_images/QcomPkg/SocPkg/AgattiPkg/Library/MDPPlatformLib/MDPPlatformLib.inf
BOOT.XF.4.1/boot_images/QcomPkg/SocPkg/AgattiPkg/Library/MDPPlatformLib/MDPPlatformLibPanelCommon.c
BOOT.XF.4.1/boot_images/QcomPkg/SocPkg/AgattiPkg/Library/MDPPlatformLib/MDPPlatformLibPanelCommon.h
BOOT.XF.4.1/boot_images/QcomPkg/SocPkg/AgattiPkg/Library/MDPPlatformLib/MDPPlatformLibPanelConfig.h
BOOT.XF.4.1/boot_images/QcomPkg/SocPkg/AgattiPkg/Library/MDPPlatformLibBoot/MDPPlatformLib.c
BOOT.XF.4.1/boot_images/QcomPkg/SocPkg/AgattiPkg/Library/MDPPlatformLibBoot/MDPPlatformLibBoot.inf
BOOT.XF.4.1/boot_images/QcomPkg/SocPkg/KamortaPkg/Library/MDPPlatformLib/MDPPlatformLib.c
BOOT.XF.4.1/boot_images/QcomPkg/SocPkg/KamortaPkg/Library/MDPPlatformLib/MDPPlatformLib.inf
BOOT.XF.4.1/boot_images/QcomPkg/SocPkg/KamortaPkg/Library/MDPPlatformLib/MDPPlatformLibPanelCommon.c
BOOT.XF.4.1/boot_images/QcomPkg/SocPkg/KamortaPkg/Library/MDPPlatformLib/MDPPlatformLibPanelCommon.h
BOOT.XF.4.1/boot_images/QcomPkg/SocPkg/KamortaPkg/Library/MDPPlatformLib/MDPPlatformLibPanelConfig.h
BOOT.XF.4.1/boot_images/QcomPkg/SocPkg/KamortaPkg/Library/MDPPlatformLibBoot/MDPPlatformLib.c
BOOT.XF.4.1/boot_images/QcomPkg/SocPkg/KamortaPkg/Library/MDPPlatformLibBoot/MDPPlatformLibBoot.inf
对外的Protocol
有关文件：
BOOT.XF.4.1/boot_images/QcomPkg/Include/Protocol/EFIDisplayPwr.h
BOOT.XF.4.1/boot_images/QcomPkg/Include/Protocol/EFIDisplayPwrCtrl.h
BOOT.XF.4.1/boot_images/QcomPkg/Include/Protocol/EFIDisplayUtils.h
Protocol接口
学习UEFI，比较关键的是：
0、了解UEFI是如何实现的
1、了解XXX_PROTOCOL定义中有什么接口可以使用：方便我们找到实现的原型
2、找到对应的XXX_PROTOCOL_GUID是多少：方便我们找到哪里调用了对应的接口
EFIDisplayPwr.h
路径：BOOT.XF.4.1/boot_images/QcomPkg/Include/Protocol/EFIDisplayPwr.h
声明了对应的EFI_DISPLAY_POWER_PROTOCOL_GUID，但没有调用。
/* Protocol GUID definition */
/** @ingroup efi_displayPwr_protocol */
#define EFI_DISPLAY_POWER_PROTOCOL_GUID \
{0xf352021d, 0x9593, 0x4432, {0xbf, 0x4, 0x67, 0xb9, 0xf3, 0xb7, 0x60, 0x8}}
/*===========================================================================
PROTOCOL INTERFACE
===========================================================================*/
/** @ingroup efi_displayUtils_protocol
@par Summary
Qualcomm Display Utils Protocol interface.
@par Parameters
@inputprotoparams{}
*/
struct _EFI_QCOM_DISPLAY_UTILS_PROTOCOL
{
UINT64 Revision;
EFI_DISPLAY_UTILS_SET_PROPERTY DisplayUtilsSetProperty;
EFI_DISPLAY_UTILS_GET_PROPERTY DisplayUtilsGetProperty;
EFI_DISPLAY_UTILS_RENDER_LOGO DisplayUtilsRenderLogo;
EFI_DISPLAY_UTILS_SET_MODE DisplayUtilsSetMode;
EFI_DISPLAY_UTILS_SET_VARIABLE DisplayUtilsSetVariable;
EFI_DISPLAY_UTILS_GET_VARIABLE DisplayUtilsGetVariable;
};
EFIDisplayPwrCtrl.h
路径：BOOT.XF.4.1/boot_images/QcomPkg/Include/Protocol/EFIDisplayPwrCtrl.h
这里的接口并没有被AP侧调用，甚至都没有声明。
/* Protocol GUID definition */
/** @ingroup efi_displayPwrCtrl_protocol */
#define EFI_DISPLAYPWRCTRL_PROTOCOL_GUID \
{0x7bfa4293, 0x7aa4, 0x4375, {0xb6, 0x3c, 0xb6, 0xaa, 0xb7, 0x86, 0xc4, 0x3c}}
// {68C3B70D-0F96-4006-99F6-0FD211F5F2B2}
#define EFI_UI_ACTIVE_EVENT_GUID \
{ 0x68c3b70d, 0xf96, 0x4006, { 0x99, 0xf6, 0xf, 0xd2, 0x11, 0xf5, 0xf2, 0xb2 } };
// {30D39942-9556-4887-A943-BC63805D9D43}
#define EFI_UI_IDLE_EVENT_GUID \
{0x30d39942, 0x9556, 0x4887, { 0xa9, 0x43, 0xbc, 0x63, 0x80, 0x5d, 0x9d, 0x43 }};
/*===========================================================================
PROTOCOL INTERFACE
===========================================================================*/
/** @ingroup efi_displayPwrCtrl_protocol
@par Summary
Qualcomm Display Power Control Protocol interface.
@par Parameters
@inputprotoparams{}
*/
struct _EFI_QCOM_DISPLAY_PWR_CTRL_PROTOCOL
{
UINT64 Revision;
EFI_DISPLAY_PANEL_POWER_CONTROL DisplayPanelPowerControl;
EFI_DISPLAY_PANEL_POWER_STATUS DisplayPanelPowerStatus;
EFI_DISPLAY_BACKLIGHT_BRIGHTNESS_LEVEL_CONTROL DisplayBacklightBrightnessLevelControl;
EFI_DISPLAY_BACKLIGHT_BRIGHTNESS_LEVEL_STATUS DisplayBacklightBrightnessLevelStatus;
};
EFIDisplayUtils.h
路径：BOOT.XF.4.1/boot_images/QcomPkg/Include/Protocol/EFIDisplayUtils.h
/* Protocol GUID definition */
/** @ingroup efi_displayUtils_protocol */
// {c0dd69ac-76ba-11e6-ab24-1fc7f5575f19}
#define EFI_DISPLAYUTILS_PROTOCOL_GUID \
{0xc0dd69ac, 0x76ba, 0x11e6, {0xab, 0x24, 0x1f, 0xc7, 0xf5, 0x57, 0x5f, 0x19}}
/**
Protocol declaration.
*/
typedef struct _EFI_QCOM_DISPLAY_UTILS_PROTOCOL EFI_QCOM_DISPLAY_UTILS_PROTOCOL;
/**
Display Utils property types
*/
typedef enum
{
EFI_DISPLAY_UTILS_DEVICE_TREE_ADDR = 0x0, /**< Device tree base address: (Type: VOID*) */
EFI_DISPLAY_UTILS_PANEL_OVERRIDE, /**< Panel override string (Type: CHAR8*) */
EFI_DISPLAY_UTILS_SUPPORTED_PANELS, /**< Newline separated list of supported panels (Type: CHAR16*) */
EFI_DISPLAY_UTILS_PANEL_CONFIG, /**< Panel raw configuration */
EFI_DISPLAY_UTILS_DYNAMIC_REFRESH, /**< Dynamic refresh settings (Type: UINT32*) */
} EFI_DISPLAY_UTILS_PROPERTY_TYPE;
/*===========================================================================
PROTOCOL INTERFACE
===========================================================================*/
/** @ingroup efi_displayUtils_protocol
@par Summary
Qualcomm Display Utils Protocol interface.
@par Parameters
@inputprotoparams{}
*/
struct _EFI_QCOM_DISPLAY_UTILS_PROTOCOL
{
UINT64 Revision;
EFI_DISPLAY_UTILS_SET_PROPERTY DisplayUtilsSetProperty;
EFI_DISPLAY_UTILS_GET_PROPERTY DisplayUtilsGetProperty;
EFI_DISPLAY_UTILS_RENDER_LOGO DisplayUtilsRenderLogo;
EFI_DISPLAY_UTILS_SET_MODE DisplayUtilsSetMode;
EFI_DISPLAY_UTILS_SET_VARIABLE DisplayUtilsSetVariable;
EFI_DISPLAY_UTILS_GET_VARIABLE DisplayUtilsGetVariable;
};
EFI_DISPLAYUTILS_PROTOCOL_GUID在AP侧中的FASTBOOT模式被调用了，用于判断是否支持显示画面。
bootable/bootloader/edk2/QcomModulePkg/Library/FastbootLib/FastbootCmds.c
STATIC UINT8
is_display_supported ( VOID )
{
EFI_STATUS Status = EFI_SUCCESS;
EfiQcomDisplayUtilsProtocol *pDisplayUtilProtocol;
EFI_GUID DisplayUtilGUID = EFI_DISPLAYUTILS_PROTOCOL_GUID;
EFI_DISPLAY_UTILS_PANEL_CONFIG_PARAMS PanelConfig;
UINT32 Index = 0;
UINT32 ParamSize = sizeof (PanelConfig);
PanelConfig.uPanelIndex = Index;
if (EFI_SUCCESS == gBS->LocateProtocol (&DisplayUtilGUID,
NULL,
(VOID **)&pDisplayUtilProtocol)) {
Status = pDisplayUtilProtocol->DisplayUtilsGetProperty (
EFI_DISPLAY_UTILS_PANEL_CONFIG,
(VOID*)&PanelConfig, &ParamSize);
if ( Status == EFI_NOT_FOUND ) {
DEBUG ((EFI_D_VERBOSE, "Display is not supported\n"));
return 0;
}
}
DEBUG ((EFI_D_VERBOSE, "Display is enabled\n"));
return 1;
}
对应接口的实现
下面我们具体看看EFI_QCOM_DISPLAY_UTILS_PROTOCOL这个实现。
BOOT.XF.4.1/boot_images/QcomPkg/Library/MDPLib/DisplayUtils.c
/* Display Utils Protocol Implementation
*/
EFI_QCOM_DISPLAY_UTILS_PROTOCOL gQcomDisplayUtilsProtocolImplementation =
{
DISPLAY_UTILS_REVISION,
Display_Utils_SetProperty,
Display_Utils_GetProperty,
Display_Utils_RenderLogo,
Display_Utils_SetMode,
Display_Utils_SetVariable,
Display_Utils_GetVariable
};
执行流程
DisplayDxeInitialize
显示驱动执环境的初始化
BOOT.XF.4.1\boot_images\QcomPkg\Drivers\DisplayDxe\DisplayDxe.c
/**********************************************************************************************************************
Public APIs
**/
/**
Initialize the state information for the Display Dxe
@param ImageHandle of the loaded driver
@param SystemTable Pointer to the System Table
@retval EFI_SUCCESS Protocol registered
@retval EFI_OUT_OF_RESOURCES Cannot allocate protocol data structure
@retval EFI_DEVICE_ERROR Hardware problems
**/
EFI_STATUS
EFIAPI
DisplayDxeInitialize (
IN EFI_HANDLE ImageHandle,
IN EFI_SYSTEM_TABLE *SystemTable
)
{
EFI_STATUS eStatus = EFI_SUCCESS;
EFI_GUID sOutputGUID = EFI_GRAPHICS_OUTPUT_PROTOCOL_GUID;
EFI_HANDLE hUEFIDisplayHandle = NULL;
MDP_InitParamsType sInitParam;
EFI_GUID UIActiveEventGuid = EFI_UI_ACTIVE_EVENT_GUID;
EFI_GUID UIIdleEventGuid = EFI_UI_IDLE_EVENT_GUID;
// Clear out global structures
MDP_OSAL_MEMZERO(&gModeInfo, sizeof(DisplayDxe_ModeInfo));
MDP_OSAL_MEMZERO(&sInitParam, sizeof(MDP_InitParamsType));
/* Register for an ExitBootServicesEvent */
// 创建了一些事件（略）： 创建一个事件，然后设定一个条件，使得条件满足的时候就执行这个事件
// ...
// 初始化有关的 时钟、电源
if (EFI_SUCCESS != DisplayPwr_InitLPMSupport(TRUE))
{
DEBUG((EFI_D_WARN, "DisplayDxe: Failed to register LPM CB!\n"));
}
// Initialize Apps BootLoader (ABL) interface
// It checks for panel override, if any, set by ABL and sets up parameters which will be used by MDPInit
if (MDP_STATUS_OK != MDPSetProperty(MDP_DISPLAY_PRIMARY, MDP_DISPLAY_PROPERTY_ABL_INTERFACE_INIT, NULL))
{
DEBUG((EFI_D_INFO, "DisplayDxe: Failed to initialize ABL!\n"));
}
// Initialize the MDP
if (MDP_STATUS_OK != MDPInit(&sInitParam, MDP_INIT_FLAG_MMU_INIT))
{
DEBUG ((EFI_D_INFO, "DisplayDxe: MDP init failed!\n"));
eStatus = EFI_DEVICE_ERROR;
}
else
{
MDP_PowerParamsType sPowerParams;
MDP_DetectParamType sDetectParams;
MDP_PropertiesParamType sDisplayProp;
MDP_OSAL_MEMZERO(&sDisplayProp, sizeof(MDP_PropertiesParamType));
MDP_OSAL_MEMZERO(&sPowerParams, sizeof(MDP_PowerParamsType));
sPowerParams.bPowerOn = TRUE;
sDisplayProp.bDisplayPwrState = TRUE;
//////////////////
// Main Display //
//////////////////
// If the primary is supported initialize it
if (TRUE == sInitParam.aSupportedDisplays[MDP_DISPLAY_PRIMARY])
{
if (MDP_STATUS_OK != MDPPower(MDP_DISPLAY_PRIMARY, &sPowerParams, 0x0))
{
DEBUG ((EFI_D_INFO, "DisplayDxe: Primary panel power up failed!\n"));
}
else
{
MDP_OSAL_MEMZERO(&sDetectParams, sizeof(MDP_DetectParamType));
// Default reporting of primary display
if (MDP_STATUS_OK != MDPDetect(MDP_DISPLAY_PRIMARY, &sDetectParams, 0x0))
{
eStatus = EFI_DEVICE_ERROR;
}
else if (TRUE == sDetectParams.bDisplayDetected)
{
eStatus = DisplayDxeSelectMode(MDP_DISPLAY_PRIMARY, &sDetectParams);
// Set the primary display to on
if (MDP_STATUS_OK != MDPSetProperty(MDP_DISPLAY_PRIMARY, MDP_DISPLAY_PROPERTY_POWER_STATE, &sDisplayProp))
{
eStatus = EFI_DEVICE_ERROR;
}
}
}
}
// If we not have detected a valid mode on both primary and external display report error
if ((0 == gModeInfo.uNumModes[MDP_DISPLAY_PRIMARY]) && (0 == gModeInfo.uNumModes[MDP_DISPLAY_EXTERNAL]))
{
eStatus = EFI_DEVICE_ERROR;
}
else
{
// Default at some dummy mode
gModeInfo.sCurrentModeInfo.Version = GRAPHICS_OUTPUT_PROTOCOL_REVISION;
gModeInfo.sCurrentModeInfo.PixelFormat = DISPLAYDXE_DEFAULT_PIXEL_FORMAT;
gModeInfo.sCurrentModeInfo.HorizontalResolution = 0;
gModeInfo.sCurrentModeInfo.VerticalResolution = 0;
gModeInfo.sCurrentModeInfo.PixelInformation.RedMask = DISPLAYDXE_RED_MASK;
gModeInfo.sCurrentModeInfo.PixelInformation.GreenMask = DISPLAYDXE_GREEN_MASK;
gModeInfo.sCurrentModeInfo.PixelInformation.BlueMask = DISPLAYDXE_BLUE_MASK;
gModeInfo.sCurrentModeInfo.PixelInformation.ReservedMask = DISPLAYDXE_ALPHA_MASK;
gModeInfo.sCurrentModeInfo.PixelsPerScanLine = 0;
// Setup the protocol information, set the current mode to an invalid mode forcing a set mode
gModeInfo.sProtocolInfo.MaxMode = 1;
gModeInfo.sProtocolInfo.Mode = (UINT32)-1;
gModeInfo.sProtocolInfo.SizeOfInfo = sizeof(EFI_GRAPHICS_OUTPUT_MODE_INFORMATION);
gModeInfo.sProtocolInfo.Info = &gModeInfo.sCurrentModeInfo;
gModeInfo.bExtSupported = sInitParam.aSupportedDisplays[MDP_DISPLAY_EXTERNAL];
// Install display protocols only if panel is detected.
// Make a new handle with EFI Graphics Protocol
if (EFI_SUCCESS != (eStatus = gBS->InstallMultipleProtocolInterfaces (&hUEFIDisplayHandle,
&gEfiDevicePathProtocolGuid,
&DisplayDevicePath,
&sOutputGUID,
&gDisplayDxeOutputProtocol,
&gQcomDisplayPwrCtrlProtocolGuid,
&gDisplayPwrCtrlProtocolImplementation,
&gEfiDisplayPowerStateProtocolGuid,
&gDisplayPwrProtocolImplementation,
&gQcomDisplayUtilsProtocolGuid,
&gQcomDisplayUtilsProtocolImplementation,
NULL)))
{
DEBUG ((EFI_D_INFO, "DisplayDxe: InstallMultipleProtocolInterfaces failed!\n"));
}
}
}
if (eStatus == EFI_SUCCESS)
{
if(EFI_SUCCESS != GetConfigValue ("EnableDisplayThread", &gModeInfo.uMultiThreadded))
{
gModeInfo.uMultiThreadded = 0;
}
// Spawn off thread to enable mode set if we are in a threadded environment
if (gModeInfo.uMultiThreadded )
{
InitLock ("DispInit", &gModeInfo.hModeLock);
if(InitLock == NULL)
{
// If single CPU core is configured, the priority of this thread should be higher than UEFI dxe thread
if (NULL != (gModeInfo.hDispThread = ThreadCreate ("Disp", &SetModeThread, 0, UEFI_THREAD_PRIORITY + 1, DEFAULT_STACK_SIZE * 3)))
{
if (MDP_STATUS_OK != MDP_SetMultiThreadState(TRUE))
{
DEBUG ((EFI_D_WARN, "DisplayDxe: Failed to set multiThread state to be enabled!\n"));
// Disable multi threadding
gModeInfo.uMultiThreadded = 0;
}
else
{
ThreadDetach (gModeInfo.hDispThread);
ThreadResume (gModeInfo.hDispThread);
}
}
else
{
// Disable multi threadding
gModeInfo.uMultiThreadded = 0;
}
}
else
{
// Disable multi threadding
gModeInfo.uMultiThreadded = 0;
}
}
}
return eStatus;
}
todo
todo高通Android UEFI中的LCD分析（1）：启动流程分析的更多相关文章
- 高通Android display架构分析
目录(?)[-] Kernel Space Display架构介绍 函数和数据结构介绍 函数和数据结构介绍 函数和数据结构介绍 数据流分析 初始化过程分析 User Space display接口 K ...
- 高通Android display分析【转】
本文转载自:http://blog.csdn.net/zhangchiytu/article/details/6777039 高通7系列硬件架构分析 如上图,高通7系列 Display的硬件部分主要由 ...
- 高通平台msm8909 LK 实现LCD 兼容
前段时间小米出现红米note2 换屏门,现在我们公司也要上演了:有两个供应商提供不同IC 的LCD panel. 软件区分的办法是读取LCD IC 的ID 寄存器,下面解析高通平台LK中LCD兼容的过 ...
- 高通Android平台硬件调试之Camera篇
之前一段时间有幸在高通android平台上调试2款camera sensor,一款是OV的5M YUV sensor,支持jpeg out,同时也支持AF,调试比较比较简单,因为别的项目已经在使用了, ...
- Cocos2d-x3.3RC0的Android编译Activity启动流程分析
本文将从引擎源代码Jni分析Cocos2d-x3.3RC0的Android Activity的启动流程,以下是具体分析. 1.引擎源代码Jni.部分Java层和C++层代码分析 watermark/2 ...
- 高通android开发摘要
一部分是开源的,可以从codeaurora.org上下载,还有一部分是高通产权的,需要从高通的网站上下载. 将高通产权的代码放到:vendor/qcom/proprietary 1. 设置bms一些参 ...
- 源码分析篇 - Android绘制流程（一）窗口启动流程分析
Activity.View.Window之间的关系可以用以下的简要UML关系图表示,在这里贴出来,比较能够帮组后面流程分析部分的阅读. 一.Activity的启动流程 在startActivity() ...
- Android 启动流程分析
原文:https://www.jianshu.com/p/a5532ecc8377 作者曾经在高通的Android性能组工作,主要工作是优化Android Application的启动时间. APP基 ...
- android PakageManagerService启动流程分析
PakageManagerService的启动流程图 1.PakageManagerService概述 PakageManagerService是android系统中一个核心的服务,它负责系统中Pac ...
- Android 7.1.1 锁屏界面启动流程
前几天遇到一个低概率复现锁屏界面不显示,仅仅显示状态栏的问题,跟了下锁屏界面启动显示的流程,在这分享下,也方便以后自己查看.前面简介了下Zygote启动流程, Zygote进程启动后会首先创建一个Sy ...
随机推荐
- Data LakeHouse_理解湖仓一体
Data Lakehouse(湖仓一体)是数据管理领域中的一种新架构范例,结合了Data Warehouse和Data Lakes的最佳特性.数据分析师和数据科学家可以在同一个数据存储中对数据进行操作 ...
- ruby on rails中sidekiq的使用
参考文章: https://www.jianshu.com/p/7ea473097023 安装redis 配置redis 配置sidekiq所依赖的redis位置,必须同时定义sidekiq的serv ...
- NASM中的ALIGN ALIGNB SECTALIGN
ALIGN与ALIGNB NASM中的ALIGN与ALIGNB是用来字节对齐的,它们接收2个参数,第一个参数是必须的,表示对齐的字节数(必须是2的幂),第二个参数是可选的,表示为了对齐而进行填充的内容 ...
- DNS(2) -- bind服务介绍及配置文件语法格式
目录 1. bind服务 1.1 bind概述 1.2 bind程序包结构 1.3 bind配置文件详解 1.3.1 bind配置文件 1.3.1.1 bind主配置文件 1.3.1.2 bind区域 ...
- iframe 高度设置为0时还有占位_iframe占位
iframe是一个内联元素,默认是跟baseline对齐的,iframe后边有个看不见.摸不着的行内空白节点,空白节点占据着高度,iframe与空白节点的基线对齐,导致了div被撑开,从而出现滚动条, ...
- 网络安全—IPSec安全策略
文章目录 网络拓扑 添加策略 ESP 添加筛选器 添加筛选器的操作 另一台主机设置 AH 使用Windows Server 2003系统 网络拓扑 client1 IP = 192.168.17.10 ...
- springcloud整合geteway网关服务
geteway网关 1. 什么是 API 网关(API Gateway)分布式服务架构.微服务架构与 API 网关在微服务架构里,服务的粒度被进一步细分,各个业务服务可以被独立的设计.开发.测试.部署 ...
- 三：nacos的配置中心
配置中心的使用: 编辑当前项目的pom.xml,加入必要的依赖配置 <!-- spring-cloud-alibaba-dependencies 依赖同注册中心 --> <depen ...
- SpringMVC在返回JSON数据时出现406错误解决方案
在SpringMVC框架的使用中常常会使用@ResponseBody注解,修饰"处理器"(Controller的方法),这样在处理器在返回完毕后,就不走逻辑视图,而是将返回的对象转 ...
- Vue cli传递数据
Nav组件和Forecast组件都是Home组件的子组件. (1)子组件传递数据给父组件 在子组件中,通过this.$emit('自定义事件名', 参数1,参数2,...)来调用父组件中定义的事件. ...