On Mon, Oct 21, 2019 at 3:46 AM Rasmus Villemoes <linux@xxxxxxxxxxxxxxxxxx> wrote: > > On 18/10/2019 23.52, Li Yang wrote: > > On Fri, Oct 18, 2019 at 3:54 PM Rasmus Villemoes > > <linux@xxxxxxxxxxxxxxxxxx> wrote: > >> > >> On 18/10/2019 22.16, Leo Li wrote: > >>> > >>>> > >>>> There have been several attempts in the past few years to allow building the > >>>> QUICC engine drivers for platforms other than PPC. This is (the beginning of) > >>>> yet another attempt. I hope I can get someone to pick up these relatively > >>>> trivial patches (I _think_ they shouldn't change functionality at all), and then > >>>> I'll continue slowly working towards removing the PPC32 dependency for > >>>> CONFIG_QUICC_ENGINE. > >>> > >>> Hi Rasmus, > >>> > >>> I don't fully understand the motivation of this work. As far as I know the QUICC ENGINE is only used on PowerPC based SoCs. > >> > >> Hm, you're not the Leo Li that participated in this thread > >> <https://lore.kernel.org/lkml/AM3PR04MB11857AE8D2B0BE56121B97D391C90@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/T/#u>? > > > > Oops, I totally forgot about this discussion which is just three years > > ago. :) The QE-HDLC on LS1021a is kind of a special case. > > > >> > >> > >> Can you give an example on how is it used on ARM system? > >> > >> LS1021A, for example, which is the one I'm aiming for getting fully > >> supported in mainline. > >> <https://www.nxp.com/products/processors-and-microcontrollers/arm-processors/layerscape-communication-process/qoriq-layerscape-1021a-dual-core-communications-processor-with-lcd-controller:LS1021A> > >> > >> The forks at https://github.com/qoriq-open-source/linux.git have various > >> degrees of support (grep for commits saying stuff like "remove PPCisms" > >> - some versions can be found on > >> <https://lore.kernel.org/lkml/?q=remove+ppcisms>). Our current kernel is > >> based on commits from the now-vanished 4.1 branch, and unfortunately at > >> least the 4.14 branch (LSDK-18.06-V4.14) trivially doesn't build on ARM, > >> despite the PPC32 dependency having been removed from CONFIG_QUICC_ENGINE. > > > > Can you try the 4.14 branch from a newer LSDK release? LS1021a should > > be supported platform on LSDK. If it is broken, something is wrong. > > What newer release? LSDK-18.06-V4.14 is the latest -V4.14 tag at > https://github.com/qoriq-open-source/linux.git, and identical to the That tree has been abandoned for a while, we probably should state that in the github. The latest tree can be found at https://source.codeaurora.org/external/qoriq/qoriq-components/linux/ > linux-4.14 branch. And despite commit 4c33e2d0576b removing the PPC32 > dependency from QUICC_ENGINE, it clearly hasn't been built on arm, since > back around v4.12, mainline's qe.c grew a call to pvr_version_is which > is ppc-only. So from that I sort of assumed that NXP had dropped trying > to support the LS1021A even in their own kernels. > > In any case, we have zero interest in running an NXP kernel. Maybe I > should clarify what I meant by "based on commits from" above: We're > currently running a mainline 4.14 kernel on LS1021A, with a few patches > inspired from the NXP 4.1 branch applied on top - but also with some > manual fixes for e.g. the pvr_version_is() issue. Now we want to move > that to a 4.19-based kernel (so that it aligns with our MPC8309 platform). We also provide 4.19 based kernel in the codeaurora repo. I think it will be helpful to reuse patches there if you want to make your own tree. > > >> This is just some first few steps, and I'm not claiming > >> that this is sufficient to make the QE drivers build on ARM yet. But I > >> have a customer with both mpc8309-based and ls1021a-based platforms, and > >> they want to run the same, as-close-to-mainline-as-possible, kernel on > >> both. So I will take a piecemeal approach, and try to make sure I don't > >> break the ppc boards in the process (just building and booting one board > >> is of course not sufficient, but better than nothing). Once I get to > >> actually build some of the QE drivers for ARM, I'll of course also test > >> them. > > > > Understood. Zhao Qiang also maintains some patches similar to your > > patchset and I think they are tested on ARM. But the review of these > > patches from last submission didn't finish. It looks like your > > patches are better divided but not really verified on ARM. Zhao > > Qiang's patches are tested but maybe need some final touch for > > cleaning up. I will let you guys decide what is the best approach to > > make this upstreamed. > > Yes, as I said, I wanted to try a fresh approach since Zhao > Qiang's patches seemed to be getting nowhere. Splitting the patches into > smaller pieces is definitely part of that - for example, the completely > trivial whitespace fix in patch 1 is to make sure the later coccinelle > generated patch is precisely that (i.e., a later respin can just rerun > the coccinelle script, with zero manual fixups). I also want to avoid > mixing the ppcism cleanups with other things (e.g. replacing some > of_get_property() by of_property_read_u32()). And the "testing on ARM" > part comes once I get to actually building on ARM. But there's not much > point doing all that unless there's some indication that this can be > applied to some tree that actually feeds into Linus', which is why I > started with a few trivial patches and precisely to start this discussion. Right. I'm really interested in getting this applied to my tree and make it upstream. Zhao Qiang, can you help to review Rasmus's patches and comment? Regards, Leo
