SIM hot swap does not work when SIM hot swap detect pin is with“EINT0”
时间:10-02
整理:3721RD
点击:
[SIM] SIM hot swap does not work when SIM hot swap detect pin is with“EINT0”
[Description]
SIM hot swap function does not work when SIM hot swap detect pin is with “EINT0”.
[Solution]
Function sim_reg_hot_plug_eint() without handler “eintNo: 0” is the cause of why SIM
hot swap does not work.
To solve it, modify the source code “custom_sim_driver.c” and function
“sim_reg_hot_plug_eint()” of Modem.
custom_sim_driver.c(MAUI\custom\drv\misc_drv\$(customer project)) 11AMDW**SP
custom_sim_driver.c(MOLY\custom\driver\drv\misc_drv\_Default_BB\MT6589) WR8.W**.MD
Then build “modem” img and add it to “alps” project build “alps” img.
Note:
dct tool path:
\alps\mediatek\dct\DrvGen.exe
codegen.dws path:
\alps\mediatek\custom\${custom project}\kernel\dct\dct\codegen.dws
MT6575/MT6577:
AP & modem share “one” EINT module. AP of EINT in “EINT Setting” of DCT tool
(codegen.dws) starts fROM EINT0. EINT of modem also starts from EINT0.
MT6589:
AP -> EINT (AP owned EINT module) AP DCT tool (codegen.dws) “EINT Setting” starts
from EINT0.
MD1 -> MD1_EINT (Modem1 owned EINT module) AP DCT tool (codegen.dws) “MD1_EINT
Setting” starts from EINT1.
EINT of Modem1 starts from EINT0.
MD2 -> MD2_EINT (Modem2 owned EINT module) AP DCT tool (codegen.dws) “MD2_EINT
Setting” starts from EINT1.
EINT of Modem2 starts from EINT0.
MT6572:
AP -> EINT (AP owned EINT module) AP DCT tool (codegen.dws) “EINT Setting” starts
from EINT0.
MD1 -> MD1_EINT (Modem1 owned EINT module) AP DCT tool (codegen.dws) “MD1_EINT
Setting” starts from EINT0.
EINT of Modem1 starts from EINT0.
[Description]
SIM hot swap function does not work when SIM hot swap detect pin is with “EINT0”.
[Solution]
Function sim_reg_hot_plug_eint() without handler “eintNo: 0” is the cause of why SIM
hot swap does not work.
To solve it, modify the source code “custom_sim_driver.c” and function
“sim_reg_hot_plug_eint()” of Modem.
custom_sim_driver.c(MAUI\custom\drv\misc_drv\$(customer project)) 11AMDW**SP
custom_sim_driver.c(MOLY\custom\driver\drv\misc_drv\_Default_BB\MT6589) WR8.W**.MD
Then build “modem” img and add it to “alps” project build “alps” img.
Note:
dct tool path:
\alps\mediatek\dct\DrvGen.exe
codegen.dws path:
\alps\mediatek\custom\${custom project}\kernel\dct\dct\codegen.dws
MT6575/MT6577:
AP & modem share “one” EINT module. AP of EINT in “EINT Setting” of DCT tool
(codegen.dws) starts fROM EINT0. EINT of modem also starts from EINT0.
MT6589:
AP -> EINT (AP owned EINT module) AP DCT tool (codegen.dws) “EINT Setting” starts
from EINT0.
MD1 -> MD1_EINT (Modem1 owned EINT module) AP DCT tool (codegen.dws) “MD1_EINT
Setting” starts from EINT1.
EINT of Modem1 starts from EINT0.
MD2 -> MD2_EINT (Modem2 owned EINT module) AP DCT tool (codegen.dws) “MD2_EINT
Setting” starts from EINT1.
EINT of Modem2 starts from EINT0.
MT6572:
AP -> EINT (AP owned EINT module) AP DCT tool (codegen.dws) “EINT Setting” starts
from EINT0.
MD1 -> MD1_EINT (Modem1 owned EINT module) AP DCT tool (codegen.dws) “MD1_EINT
Setting” starts from EINT0.
EINT of Modem1 starts from EINT0.