arm64: dts: rockchip: vdd_log is not an i2c slave
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): 20180218154359.9362-1-vicencb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Am Sonntag, 18. Februar 2018, 16:43:59 CET schrieb Vicente Bergas:
Quoted 11 lines
The
vdd_logpower supply is controlled by a PWM pin, not by i2c register access. There is a boot message that reports an error about not being able to bring that supply up. Also, the eMMC is not detected and/dev/mmcblk2does not exist.References:
[1]
Schematic page 16, search forLOG_DVS_PWM
https://dl.vamrs.com/products/sapphire_excavator/RK_SAPPHIRE_SOCBOARD_RK3399_LPDDR3D178P232SD8_V12_20161109HXS.pdf
(alternate link)
http://opensource.rock-chips.com/images/f/f0/RK_Sapphire_RK3399.rar
Quoted 4 lines
[2]
arch/arm64/boot/dts/rockchip/rk3399-firefly.dtsSigned-off-by Vicente Bergas <[email protected]>
I've adapted the commit message a bit and applied the patch for 4.17
For the emmc, that is a separate issue and you'll need to look at the logs to see if there is anything shown. Especially device-numbering (your mmcblk2) is not guaranteed, so this could very well also be mmcblk0 or mmcblk1
Thanks
Heiko
Quoted 20 lines · Heiko Stuebner
Am Sonntag, 18. Februar 2018, 16:43:59 CET schrieb Vicente Bergas:
Quoted 11 lines
The
vdd_logpower supply is controlled by a PWM pin, not by i2c register access. There is a boot message that reports an error about not being able to bring that supply up. Also, the eMMC is not detected and/dev/mmcblk2does not exist.References:
[1]
Schematic page 16, search forLOG_DVS_PWM
https://dl.vamrs.com/products/sapphire_excavator/RK_SAPPHIRE_SOCBOARD_RK3399_LPDDR3D178P232SD8_V12_20161109HXS.pdf
(alternate link)
http://opensource.rock-chips.com/images/f/f0/RK_Sapphire_RK3399.rarQuoted 4 lines
[2]
arch/arm64/boot/dts/rockchip/rk3399-firefly.dtsSigned-off-by Vicente Bergas <[email protected]>I've adapted the commit message a bit and applied the patch for 4.17
Quoted 8 lines
For the emmc, that is a separate issue and you'll need to look at the logs to see if there is anything shown. Especially device-numbering (your mmcblk2) is not guaranteed, so this could very well also be mmcblk0 or mmcblk1
Thanks
Heiko
Sorry, I did not mention it because I thought it was implicit:
both issues, the one related to the vdd_log and the other related to
eMMC, are fixed with this patch.
Anyways, thanks for applying it!
Regards,
Vicente.