[Q2] The driver's loading order is not as we have set--[i.MX53-WEC7 ]

cancel
Showing results for 
Search instead for 
Did you mean: 

[Q2] The driver's loading order is not as we have set--[i.MX53-WEC7 ]

510 Views
johnphy
Contributor I

Hi,

   Thanks for your attenion.

   We use I.MX53 running WEC7. The registery storage is "Hive-based Registry" and the file system is  "RAM and ROM file system".

   There are some problems need your help. Any suggestion is welcome, thanks!

0 Kudos
2 Replies

211 Views
johnphy
Contributor I

Can anybody give any suggestion?

0 Kudos

211 Views
johnphy
Contributor I

[Q2] The driver's loading order is not as we have set--[i.MX53-WEC7 ]

   We want the display driver to be loaded befor backlight, so we set the platform.reg as below:

             ..........

;------------------------------------------------------------------------------

; GWES Display Driver

;

#if ((defined BSP_DISPLAY_DVI_TFP410 && defined BSP_I2CBUS2) || defined BSP_DISPLAY_CHUNGHWA_CLAA070VC01 || defined BSP_DISPLAY_VGA || defined BSP_DISPLAY_LVDS || defined BSP_DISPLAY_TVE)

[HKEY_LOCAL_MACHINE\System\GDI\Drivers]

    "Display"="ddraw_ipu.dll"

    "Order"=dword:10          ; load order

[HKEY_LOCAL_MACHINE\Drivers\Display\DDIPU]

   "Bpp"=dword:10                ; RGB565

   "VideoBpp"=dword:20           ; RGB666 (32bpp internal)

   "VideoMemSize"=dword:8000000  ; 128MB

; @CESYSGEN IF CE_MODULES_COMPOSITOR

; Compositor Registry Configuration:

;

; CompositorPlugin          SZ       Plugin module name.

; FramePeriodMs             DWORD    Expected period, in milliseconds, for each render frame.

; DefaultOpaqueBpp          DWORD    Default pixel depth used when allocating window surfaces. 

;

[HKEY_LOCAL_MACHINE\System\Gwe\Compositor]

        "FramePeriodMs"=dword:20

        "DefaultOpaqueBpp"=dword:10          ; 32bpp

; @CESYSGEN ENDIF CE_MODULES_COMPOSITOR

  

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\VDI]

   "Prefix"="VDI"

   "Dll"="vdi.dll"

   "Order"=dword:20

   "Index"=dword:1  

#endif

;------------------------------------------------------------------------------

;------------------------------------------------------------------------------

;  Backlight Driver

;

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Backlight]

    "Dll" = "backLight.Dll"

    "Prefix" = "BKL"

    "Flags"=dword:8 ;DEVFLAGS_NAKEDENTRIES

    "Index" = dword:1

    "Order" = dword:11            ; After display driver

    "IClass" = multi_sz:"{F922DDE3-6A6D-4775-B23C-6842DB4BF094}",

                        "{0007AE3D-413C-4e7e-8786-E2A696E73A6E}"

;------------------------------------------------------------------------------

  But when the system boot up, the driver's load order is not as we have set, why?

             ..........

PID:00400002 TID:01840006 +BSPBacklightInitialize

PID:00400002 TID:01840006 BKL::Backlight SPI Init.

PID:00400002 TID:01840006 -BSPBacklightInitialize

PID:00400002 TID:01840006 BKL::Sharememory Keypad

PID:00400002 TID:01840006 BKL::OK:CreateThread-g_hThreadKPBK

PID:00400002 TID:038D0002 ThreadProcKPBK ID = 0x38d0002

     ..........

PID:00400002 TID:01840006 GKP_Init:InterruptInitialize (dwSysIntr[i]-29,ISTEvent[i]-60817411) !

            ..........

PID:00400002 TID:01A40006 GKP::IOCTL_POWER_CAPABILITIES

PID:00400002 TID:01840006 ConfigOTGHost BoardId = 0x901

            ..........

PID:00400002 TID:03900002 BKL::Power state is = D0.

PID:00400002 TID:03900002 +BSPBacklightSetIntensity

PID:00400002 TID:03900002 BKL::Backlight to Level = +27

PID:00400002 TID:03900002 -BSPBacklightSetIntensity

PID:00400002 TID:04A6001E WARNING: possible performance issue: timeInit() not called, calling it in timeSetEvent()PID:00400002 TID:04A6001E BSPDisplayIOMUXSetup IOMUX setted.

PID:00400002 TID:04A6001E ===============DisplaySetMode===================.

PID:00400002 TID:04A6001E start initilization of LCD

PID:00400002 TID:04A6001E Initialize LD9042

PID:00400002 TID:04A6001E In CLAA.cpp set

           ..........

0 Kudos