We are planning on using the PF1510 with the i.MX6ULL processor. I see this device tree example:
https://github.com/Freescale/linux-fslc/blob/5.4-2.1.x-imx/arch/arm/boot/dts/imx7ulp-evk.dts#L85
So for this driver do I not need to specify the i2c address with the i2c controller section of device tree?
Solved! Go to Solution.
Hi,
Thank you for your interest in NXP Semiconductor products
Have you seen this patches? Even though they're not in the latest version I think they might be useful for the integration https://community.nxp.com/t5/Power-Management-Knowledge-Base/PMIC-PF1550-i-MX-Processors-Resource/ta....
Thank you for your patience.
Regards
Hi,
Thank you for your interest in NXP Semiconductor products
Have you seen this patches? Even though they're not in the latest version I think they might be useful for the integration https://community.nxp.com/t5/Power-Management-Knowledge-Base/PMIC-PF1550-i-MX-Processors-Resource/ta....
Thank you for your patience.
Regards
So the driver pf1550-rpmsg.c uses rpmsg, as opposed to the pfuze100.c driver that uses i2c.
rpmsg uses the rpmsg driver, which in turn talks to the mailbox driver?
The mailbox driver is mu, and is only found on certain i.MX processors such as the i.MX7ULP>
Is this correct? So the pf1550-rpmsg.c driver is not compatible with the i.mx6ULL which has no mu hardware feature?
I think the problem is that the pf1550.c driver is the right driver for i2c, but the source code does not exist in Linux in NXP sources on github.
The Linux guide for the i.MX family points to:
drivers/regulator/pf1550.c
on page 29 of Rev. LF6.1.1_1.0.0 — 31 March 2023 of the i.MX Linux Reference Manual.
Unfortunately in the repository:
regulator directory of Linux
the file pf1550.c does not exist.
And this driver which is present does not use i2c:
rpmsg driver
I noticed the mcimx6ull-evk kit which runs Linux does not use this part either.