Problem IMX8MN booting legacy kernel and mipi display
Adam Ford
aford173 at gmail.com
Sun Feb 13 17:03:43 CET 2022
On Sat, Feb 12, 2022 at 1:27 PM Michael Nazzareno Trimarchi
<michael at amarulasolutions.com> wrote:
>
> Hi Tim
>
> You are using the imx8mm. I have problems on imx8mn. It's like some
> part is not implemented. Time to time power domain timeout if I
> enabled
> mipi pipeline
If you're using ATF from its mainline branch, it likely does not have
the power domain code enabled, so many peripherals (including DSI and
CSI) likely won't work.
The power-domain code would be located in gpc.v [1], but as far as I
know, attempts to push that upstream were abandoned in favor of having
Linux do the power domain stuff, so to use NXP's kernel, you'll need
NXP's ATF.
[1] - https://source.codeaurora.org/external/imx/imx-atf/tree/plat/imx/imx8m/imx8mn/gpc.c?h=lf_v2.4
adam
>
> Michael
>
> On Wed, Feb 2, 2022 at 4:54 PM Tim Harvey <tharvey at gateworks.com> wrote:
> >
> > On Wed, Feb 2, 2022 at 5:04 AM Michael Nazzareno Trimarchi
> > <michael at amarulasolutions.com> wrote:
> > >
> > > Hi Adam
> > >
> > > On Wed, Feb 2, 2022 at 2:02 PM Adam Ford <aford173 at gmail.com> wrote:
> > > >
> > > > On Wed, Feb 2, 2022 at 6:24 AM Michael Nazzareno Trimarchi
> > > > <michael at 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
>
>
>
> --
> Michael Nazzareno Trimarchi
> Co-Founder & Chief Executive Officer
> M. +39 347 913 2170
> michael at amarulasolutions.com
> __________________________________
>
> Amarula Solutions BV
> Joop Geesinkweg 125, 1114 AB, Amsterdam, NL
> T. +31 (0)85 111 9172
> info at amarulasolutions.com
> www.amarulasolutions.com
More information about the U-Boot
mailing list