Hi All,
I have an i2c controlled MIPI OLED display mounted on the expansion board of an HDK 865/SM8250.
I need to control the AB/LAB/ELVDD/Amoled Boost and IBB/ELVSS/Inverted Block Boost regulators via my own driver with custom values.
I followed the Qualcomm documentation and did:
- Replace the vendor/qcom/proprietary/devicetree-4.19/qcom/pm8150l.dtsi::pm8150a_amoled::compatible from "qcom,qpnp-amoled-regulator" to "qcom,qpnp-labibb-regulator"
- Modified kernel/msm-4.19/arch/arm64/configs/vendor/kona_defconfig from (CONFIG_REGULATOR_QPNP_AMOLED=y, CONFIG_REGULATOR_QPNP_LABIBB=n) to (CONFIG_REGULATOR_QPNP_AMOLED=n, CONFIG_REGULATOR_QPNP_LABIBB=y),
- Trace the kernel/msm-4.19/drivers/regulator/qpnp-labibb-regulator.c and adapted the device tree until the qpnp-labibb-regulator load happily.
I seem to be able to controlled the AB and IBB regulators with (1. to 3.) above.
However, when switching the regulator control from 'amoled' to 'labibb' (see 1. above), the expansion board i2c controller is no longer powered when turning on Android which prevent me to send commands to my MIPI OLED display over i2c.
Question: "What am I misssing to turn-on the power on the expansion board when using the 'qcom,qpnp-labibb-regulator' driver"?
Thanks and regards,
Bruno