On Wed, Feb 2, 2022 at 5:04 AM Michael Nazzareno Trimarchi <mich...@amarulasolutions.com> wrote: > > Hi Adam > > On Wed, Feb 2, 2022 at 2:02 PM Adam Ford <aford...@gmail.com> wrote: > > > > On Wed, Feb 2, 2022 at 6:24 AM Michael Nazzareno Trimarchi > > <mich...@amarulasolutions.com> wrote: > > > > > > Hi all > > > > > > I have now able to pack those combination and all of them look ok > > > > > > - mainline uboot > > > - optee 3.15.0 > > > - atf 2.5 > > > - mainline kernel > > > > > > - mainline uboot > > > - optee 3.15.0 > > > - imx-atf rel_imx_5.4.70_2.3.2 > > > - Linux rel_imx_5.4.70_2.3.2 > > > > > > I have a setup where I can test some peripherals. I can run an optee > > > test on both combinations > > > The big issue I have it's the DSIM display it's not working and > > > crashes the kernel using the rel_imx_5.4.70_2.3.2 nxp version. The > > > mipi > > > randomly deadlock the booting. If I don't register the mipi part it's > > > ok. Can someone have an idea? > > > > Are you using the Linux rel_imx_5.4.70_2.3.2 with imx-atf > > rel_imx_5.4.70_2.3.2? > > > > The NXP kernel expects the NXP ATF code. The power-domain drivers in > > the NXP branch make secure calls to ATF which enable/disable the > > power-domains which control a bunch of peripherals like DSI, CSI, USB > > and GPU. If you're using the mainline ATF, I don't believe it > > contains the power-domain controllers, so when the Linux power-domain > > drivers make the secure calls, it's likely the power-domains won't > > change. > > - mainline uboot > - optee 3.15.0 > - imx-atf rel_imx_5.4.70_2.3.2 > - Linux rel_imx_5.4.70_2.3.2 > > I have tried even to not load optee in the image but still the same > > Michael > > > > adam > > > > > > All of them can be test using a buildroot setup > > > > > > Michael >
Michael, I have not bothered with NXP's kernel, but I do have DSIM working on 5.15 with a set of patches here https://github.com/Gateworks/linux-venice if it is helpful. I've been using this with a mainline U-Boot, imx-atf lf_v2.4. Tim
