Hi everybody
we are using BSP L4.19.35 but appears NVCC_SNVS_1V8 (PMIC LDO1) phenomenon changed from 1V8 -> 3V
Waveform:
+ When trying 3 BSP versions on IMX8MM EVK board, we have the following results
- BSP L4.14.78 → LDO1 unchanged
- BSP L4.19.35 → LDO1 Has been changed
- BSP L5.4.24 → LDO1 unchanged
+ Check register set PMIC LDO1_ 0x18 corresponding to get the results
Command: i2cget -f -y 0 0x4b 0x18
- L4.14.78 -> result = 0x62 (1.8V)
- L4.19.35 -> result = 0x40 (3V)
- L5.4.24 -> result = 0x62 (1.8V)
* See the attached Log file and PMIC_LDO1_reg.png Image
Can you help me confirm this below
1. You can test on your EVK board with BSP 4.19.35
https://www.nxp.com/webapp/Download?colCode=L4.19.35_1.0.0_MX8MM&appType=license
-> Has the above phenomenon happened?
2. The Operating range of the CPU IMX8MM NVCC_SNVS_1P8 is 1.62V ~ 1.98V?
Does it matter when it becomes 3V?
3. Why is this phenomenon on the L4.19.35 version? Has PMIC driver been changed?
4. It seems that in bd71837-regulator.c file set LDO1 range is 3V ~ 3.3V?
is not 1.6V ~ 1.9V, is this the cause?
/*
* LDO1
* 3.0 to 3.3V (100mV step)
*/
static const struct regulator_linear_range bd71837_ldo1_voltage_ranges[] = {
REGULATOR_LINEAR_RANGE(3000000, 0x00, 0x03, 100000),
};
We appreciate your feedback
Thanks and Regards,
Huy
Solved! Go to Solution.
Hi Huy
there are different patches for this issue, please appy the correct patch on the right release branch:
1). imx_4.14.98_2.3.0:
0001-MLK-23275-1-ARM64-dts-freescale-fsl-imx8mm-evk-corre.patch
0002-MLK-23275-2-ARM64-dts-freescale-fsl-imx8mn-ddr4-evk-.patch
0003-MLK-23275-3-regulator-bd71837-correct-ldo1-ldo2-grou.patch
2). imx_4.19.35_1.1.0:
0001-MLK-23275-1-ARM64-dts-freescale-fsl-imx8mm-evk-corre.patch
0002-MLK-23275-2-ARM64-dts-freescale-fsl-imx8mn-ddr4-evk-.patch
0003-MLK-23846-ARM64-dts-freescale-fsl-imx8mn-ddr4-evk-co.patch
3). imx_5.4.3_2.0.0:
0001-MLK-23275-1-ARM64-dts-freescale-fsl-imx8mm-evk-corre.patch
0002-MLK-23275-2-ARM64-dts-freescale-imx8mn-ddr4-evk-corr.patch
0003-MLK-23844-1-ARM64-dts-freescale-imx8mn-ddr4-evk-clea.patch
0004-MLK-23844-2-ARM64-dts-freescale-imx8mm-correct-VDDAR.patch
make search on link
https://source.codeaurora.org/external/imx/linux-imx/log/?h=imx_5.4.3_2.0.0&qt=grep&q=MLK-23275
Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
Hi Huy
there are different patches for this issue, please appy the correct patch on the right release branch:
1). imx_4.14.98_2.3.0:
0001-MLK-23275-1-ARM64-dts-freescale-fsl-imx8mm-evk-corre.patch
0002-MLK-23275-2-ARM64-dts-freescale-fsl-imx8mn-ddr4-evk-.patch
0003-MLK-23275-3-regulator-bd71837-correct-ldo1-ldo2-grou.patch
2). imx_4.19.35_1.1.0:
0001-MLK-23275-1-ARM64-dts-freescale-fsl-imx8mm-evk-corre.patch
0002-MLK-23275-2-ARM64-dts-freescale-fsl-imx8mn-ddr4-evk-.patch
0003-MLK-23846-ARM64-dts-freescale-fsl-imx8mn-ddr4-evk-co.patch
3). imx_5.4.3_2.0.0:
0001-MLK-23275-1-ARM64-dts-freescale-fsl-imx8mm-evk-corre.patch
0002-MLK-23275-2-ARM64-dts-freescale-imx8mn-ddr4-evk-corr.patch
0003-MLK-23844-1-ARM64-dts-freescale-imx8mn-ddr4-evk-clea.patch
0004-MLK-23844-2-ARM64-dts-freescale-imx8mm-correct-VDDAR.patch
make search on link
https://source.codeaurora.org/external/imx/linux-imx/log/?h=imx_5.4.3_2.0.0&qt=grep&q=MLK-23275
Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
Thanks for your help
We will reconfirm it