From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id AA1FCC433F5 for ; Wed, 27 Oct 2021 16:01:18 +0000 (UTC) Received: from mail-wr1-f52.google.com (mail-wr1-f52.google.com [209.85.221.52]) by mx.groups.io with SMTP id smtpd.web08.13706.1635350476901785289 for ; Wed, 27 Oct 2021 09:01:17 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20210112 header.b=S90EKF1X; spf=pass (domain: gmail.com, ip: 209.85.221.52, mailfrom: b.hutchman@gmail.com) Received: by mail-wr1-f52.google.com with SMTP id z14so4995107wrg.6 for ; Wed, 27 Oct 2021 09:01:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=WbxwG271WB5LY2ee8jnfWqLI446GTPKKXgozF1NdCtA=; b=S90EKF1Xg8nppHHGFJwUI06uiFObGeFG4hrc/EzyVwf2Mzy6c85yxmkUmthdW6XzMf TKAEEz10VzuDb347WZgJjEhM7iRZCySMa+h5l/Y3ijfdkTgu5pfzCa2YvGVhUEO9RbFt N8EBHteR40BKcjC4hNnbl8SIAQIz+DF2p1ynb3Oo0sk2+ArpSNFNxSq8V9uUsryRFSom DLuwAvoyfAW1Lvqx5PXusWSMFXfQAxVwb9HXRxvyXaz7UmoRwzXCj2txxj+nNevgjAt2 B4gdYK1l4UZudnkdhAsa9I9YKsEQyOf5WZ+qp420s8NNlmiwtoxieuGXz/QF+2sgWOT6 QRJA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=WbxwG271WB5LY2ee8jnfWqLI446GTPKKXgozF1NdCtA=; b=lxlduBmr7B+z1uBjdi+FoG6stzUsWf70WC6NyAh4PC0QPwgbRPvuhZFuIDA3l73Hof 3gHfiElvE8Tm5+uiCw+ZAGaMPJYpCdx02X2bTlMbqJQ2J1XuPEZmFhAJWms1EDXrwSz5 7p71aalWFeHeORY7Ukqdn7nHo6DJEPFK8ShRVbgsfBj36cYRijuyrsgkMtEuG5lLV2K1 4XneW4NdKB5fhqAkg3nvBp92Ql8p8uR61d5ANSm4mkJQiT13zi3sejDBCHhB2jauaOk2 g3vQy4drIEtj/Uu2zCUeyhY10rNZEOpFG2N8nMbR+2sFE+PEaGBTxb8jLUlPDLebKLc9 22Lg== X-Gm-Message-State: AOAM530GRfZN/6O1RDg1dEkL1n1+TCO+6HgsuZfdUpuvxJX/uFbD4WTb /JfaUbaev1CJeAA6FJ2n7zpUghDV+tLb0xwbBcE= X-Google-Smtp-Source: ABdhPJx0LOlFfpN7L88OEhg4+z/btOC6udaQho0N/Ry+NoCUkzdaso0pRXCMriwTJRP04kRyX1wutJqV9fLezxyHgkQ= X-Received: by 2002:a05:6000:1563:: with SMTP id 3mr41836920wrz.20.1635350475210; Wed, 27 Oct 2021 09:01:15 -0700 (PDT) MIME-Version: 1.0 References: <16B199CF92574165.11657@lists.yoctoproject.org> In-Reply-To: From: Brian Hutchinson Date: Wed, 27 Oct 2021 12:01:04 -0400 Message-ID: Subject: Re: [meta-freescale] linux-fsl 5.10 kernels don't appear to have multi-lane in sound/soc/fsl/fsl_sai.c To: Andrey Zhizhikin Cc: Fabio Estevam , meta-freescale@lists.yoctoproject.org Content-Type: multipart/alternative; boundary="0000000000002880ff05cf57b4ce" List-Id: X-Webhook-Received: from li982-79.members.linode.com [45.33.32.79] by aws-us-west-2-korg-lkml-1.web.codeaurora.org with HTTPS for ; Wed, 27 Oct 2021 16:01:18 -0000 X-Groupsio-URL: https://lists.yoctoproject.org/g/meta-freescale/message/24774 --0000000000002880ff05cf57b4ce Content-Type: text/plain; charset="UTF-8" Hey Andrey, On Wed, Oct 27, 2021 at 10:37 AM Andrey Zhizhikin wrote: > Hello Brian, > > On Wed, Oct 27, 2021 at 3:24 PM Brian Hutchinson > wrote: > > > > Hi Andrey, > > > > > > On Wed, Oct 27, 2021 at 9:01 AM Andrey Zhizhikin > wrote: > >> > >> Hello Brian, > >> > >> On Wed, Oct 27, 2021 at 2:45 PM Brian Hutchinson > wrote: > >> > > >> > > >> > > >> > On Wed, Oct 27, 2021 at 8:18 AM Fabio Estevam > wrote: > >> >> > >> >> Hi Brian, > >> >> > >> >> On Tue, Oct 26, 2021 at 11:10 AM Brian Hutchinson < > b.hutchman@gmail.com> wrote: > >> >> > > >> >> > > >> >> > > >> >> > On Tue, Oct 26, 2021 at 10:07 AM Brian Hutchinson via > lists.yoctoproject.org > wrote: > >> >> >> > >> >> >> Hi, > >> >> >> > >> >> >> First, forgive me for posting a link in an post with no context > ... I hit a wrong button and accidentally sent before ready. > >> >> >> > >> >> >> Bottom line up front. How can I get a 5.10 kernel with > multi-lane support for IMX8MM? > >> >> >> > >> >> >> We use linux-fsl 5.4 on a IMXMM based board and have recently > stepped up to linux-fsl 5.10 and the sound/fsl/fsl_sai.c has no support for > "multi-lane" anymore which breaks our code. > >> >> >> > >> >> >> I figure this is simply a case where things in linux-imx are new > and just not picked up in linux-fslc yet but wondering if it's possible to > get multi-lane support in a 5.10 kernel for the IMX8MM. > >> >> >> > >> >> >> I still don't quite fully understand how all the releases work, > the linux-imx releases appear to be for newer boards and don't necessarily > support the older boards from what I'm seeing. > >> >> >> > >> >> >> Thanks for any advice/guidance. > >> >> >> > >> >> >> Regards, > >> >> >> > >> >> >> Brian > >> >> > > >> >> > > >> >> > And that link I accidentally posted by itself > https://source.codeaurora.org/external/imx/linux-imx/tree/sound/soc/fsl/fsl_sai.c?h=lf-5.10.y > >> >> > > >> >> > ... is the reference I mentioned where I see multi-lane support in > linux-imx 5.10. > >> >> > >> >> With the mainline SAI driver, it is possible to use several channels. > >> >> Not sure what you mean by "multi-lane" in your use-case. > >> >> > >> >> Please check: > >> >> https://bootlin.com/blog/eight-channels-audio-on-i-mx7-with-pcm3168/ > >> > > >> > > >> > I hoped folks would know what I was talking about without getting too > far into the weeds. But I guess I need to explain more. > >> > > >> > The older 5.4 kernels (and even 4 series kernels) had a > imx8mm-evk.dts sai section that looked like this: > >> > > >> > &sai1 { > >> > pinctrl-names = "default"; > >> > pinctrl-0 = <&pinctrl_sai1>; > >> > assigned-clocks = <&clk IMX8MM_CLK_SAI1>; > >> > assigned-clock-parents = <&clk IMX8MM_AUDIO_PLL1_OUT>; > >> > assigned-clock-rates = <24576000>; > >> > clocks = <&clk IMX8MM_CLK_SAI1_IPG>, <&clk IMX8MM_CLK_DUMMY>, > >> > <&clk IMX8MM_CLK_SAI1_ROOT>, <&clk IMX8MM_CLK_DUMMY>, > >> > <&clk IMX8MM_CLK_DUMMY>, <&clk IMX8MM_AUDIO_PLL1_OUT>, > >> > <&clk IMX8MM_AUDIO_PLL2_OUT>; > >> > clock-names = "bus", "mclk0", "mclk1", "mclk2", "mclk3", > "pll8k", "pll11k"; > >> > fsl,sai-multi-lane; > >> > fsl,dataline,dsd = <0 0xff 0xff 2 0xff 0x11>; > >> > fsl,sai-synchronous-rx; > >> > dmas = <&sdma2 0 25 0>, <&sdma2 1 25 0>; > >> > #sound-dai-cells = <0>; > >> > status = "okay"; > >> > }; > >> > > >> > ... which has fsl,sai-multi-lane support. > >> > > >> > The current linux-fslc 5.10 kernel does not have fsl,sai-multi-lane > support. > >> > >> linux-fslc-imx kernel recipe on the [master] branch on meta-freescale > >> provides a kernel, which has linux-imx as a base and latest LTS > >> applied on top. > >> > >> Assuming you're building now off the [master] branch and do not set > >> the IMX_DEFAULT_BSP to any value anywhere in your conf files - you > >> will be building a Mainline BSP (see [1]), which does select > >> linux-fslc as a preferred provider for your kernel, see [2]. > >> > >> You can try to either switch your BSP to NXP one by setting > >> IMX_DEFAULT_BSP = "nxp", or switch your kernel provider to > >> "linux-fslc-imx" one. > > > > > > I really would like to stick with linux-fslc since that's what we've > been using for more than a year now. Kind of scared to switch back to > linux-fslc-imx (I'll try to do better with my terminology) but if you guys > think that's best then I'll try it. Worried that our custom apps might be > impacted by the switch. > > > >> > >> As a quick GIT grep in the linux-fslc repo on [5.10-2.1.x-imx] branch: > >> git grep sai-multi-lane > >> arch/arm64/boot/dts/freescale/imx8mm-evk-ak4497.dts: > fsl,sai-multi-lane; > >> arch/arm64/boot/dts/freescale/imx8mm-evk.dtsi: fsl,sai-multi-lane; > >> arch/arm64/boot/dts/freescale/imx8mp-ab2.dts: fsl,sai-multi-lane; > >> arch/arm64/boot/dts/freescale/imx8mq-evk-ak4497.dts: > fsl,sai-multi-lane; > >> arch/arm64/boot/dts/freescale/imx8mq-evk.dts: fsl,sai-multi-lane; > >> sound/soc/fsl/fsl_sai.c: if (of_find_property(np, > >> "fsl,sai-multi-lane", NULL)) > >> > >> Guess this is what you're looking for, right? > > > > > > I'd be ok with doing a build of just the kernel on master branch as long > as it supports imx8mm-evk (what our board is based on) but the rest of our > rootfs is based on Dunfell release. > > > > So if I'm following you correctly, you're saying the linux-fslc repo has > imx 5.10 with multi-lane in it. > > There are 2 kernel repositories here at play, namely: > - linux-fslc from Freescale GitHub > - linux-imx from CodeAurora > > They both stem from stable korg, but using different strategy to evolve. > > linux-imx is an NXP kernel fork, which they use to commit their > internal patches on top of some stable release. In case of 5.10 - it > is v5.10.54 from stable korg, which resides on [lf-5.10.y] branch. > > linux-fslc is combination of various branches, and if we look at the > 5.10 - there is a corresponding branch [5.10.x+fslc], and it is > practically a vanilla 5.10.y kernel from stable korg, with only > handful of patches on top. > > If I to examine this like that: > $ git log --oneline --no-merges stable/linux-5.10.y..5.10.x+fslc | wc -l > 9 > > As one can see, it has only 9 patches on top of stable korg. > > What comes in addition inside linux-fslc repository, is the branch > [5.10-2.1.x-imx], which is a combination of [lf-5.10.y] branch from > linux-imx repo and latest stable patch applied on top of it (with > merge conflict resolution, of course). > > When examined, it brings the following: > $ git log --oneline --no-merges stable/linux-5.10.y..5.10-2.1.x-imx | wc > -l > 5456 > > Here we see, that there is a substantial difference in terms of number > of patches applied. It might be a new functionality (like your desired > multi-lane support), but can also contain a code in question, which > might not work for all scenarios you're applying your kernel to. > > Hope that clears it a bit, and would help you to drive your decision > further on which kernel to use. > > > > > How come linux-fslc 5.10 doesn't have it? Is it a case where imx > released it later and hasn't worked it's way into linux-fslc yet? > > That is the trick: you most probably used the NXP-based up-merged > branch in your BSP, but now when switched to new Yocto release - you > received a vanilla kernel, which does not have those NXP patches > applied. > So I was in error. I looked back at the local.conf where our 5.4 kernel came from that we are happy with (and has multi-lane) and it was linux-fslc-imx so I guess it's linux-fslc with some imx releases merged in. When I switched to 5.10 in hardknott it looks like it pulled in linux-fslc by default which looks pretty vanilla as you mentioned. So I'll try what you said about "You can try to either switch your BSP to NXP one by setting IMX_DEFAULT_BSP = "nxp", or switch your kernel provider to "linux-fslc-imx" one." To try and get a linux-fslc-imx 5.10 build and see if it's got multi-lane in it. I was using hardknott when I originally got 5.10 so don't know if I need to do a repo sync to get newer stuff or checkout master but would only be interested in getting kernel and keeping our Dunfell based rootfs. I'll go try some stuff. Thanks for the input and advice. Regards, Brian > > > > I'd be willing to "try" 5.10.2.1.x-imx just to see if it solves our > problem but still would prefer to stick with linux-fslc ... but if that's > the only way to get this feature back I guess I'll have to do what I need > to do. > > > > I still get confused by linux-fslc, linux-imx linux-fslc-imx some. > Which one would be the safest (aka most stable) for imx8mm ... and have > multi-lane support? > > > > Thanks again for putting up with my dumb questions and weird issues. > Everything was ok until we had to step up to 5.4 in order to pick up some > DSA PTP (1588) patches. > > > > Regards, > > > > Brian > > > > > -- > Regards, > Andrey. > --0000000000002880ff05cf57b4ce Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hey Andrey,

On Wed, Oct 27, 2021 at 10= :37 AM Andrey Zhizhikin <andrey.z@gmail.com> wrote:
Hello Brian,

On Wed, Oct 27, 2021 at 3:24 PM Brian Hutchinson <b.hutchman@gmail.com> wrote:
>
> Hi Andrey,
>
>
> On Wed, Oct 27, 2021 at 9:01 AM Andrey Zhizhikin <andrey.z@gmail.com> wrote: >>
>> Hello Brian,
>>
>> On Wed, Oct 27, 2021 at 2:45 PM Brian Hutchinson <b.hutchman@gmail.com> w= rote:
>> >
>> >
>> >
>> > On Wed, Oct 27, 2021 at 8:18 AM Fabio Estevam <festevam@gmail.com> wro= te:
>> >>
>> >> Hi Brian,
>> >>
>> >> On Tue, Oct 26, 2021 at 11:10 AM Brian Hutchinson <b.hutchman@gmail.com= > wrote:
>> >> >
>> >> >
>> >> >
>> >> > On Tue, Oct 26, 2021 at 10:07 AM Brian Hutchinson vi= a lists.yoctoproject.org <b.hutchman=3Dgmail.com@lists.yoctoproject.o= rg> wrote:
>> >> >>
>> >> >> Hi,
>> >> >>
>> >> >> First, forgive me for posting a link in an post = with no context ... I hit a wrong button and accidentally sent before ready= .
>> >> >>
>> >> >> Bottom line up front.=C2=A0 How can I get a 5.10= kernel with multi-lane support for IMX8MM?
>> >> >>
>> >> >> We use linux-fsl 5.4 on a IMXMM based board and = have recently stepped up to linux-fsl 5.10 and the sound/fsl/fsl_sai.c has = no support for "multi-lane" anymore which breaks our code.
>> >> >>
>> >> >> I figure this is simply a case where things in l= inux-imx are new and just not picked up in linux-fslc yet but wondering if = it's possible to get multi-lane support in a 5.10 kernel for the IMX8MM= .
>> >> >>
>> >> >> I still don't quite fully understand how all= the releases work, the linux-imx releases appear to be for newer boards an= d don't necessarily support the older boards from what I'm seeing.<= br> >> >> >>
>> >> >> Thanks for any advice/guidance.
>> >> >>
>> >> >> Regards,
>> >> >>
>> >> >> Brian
>> >> >
>> >> >
>> >> > And that link I accidentally posted by itself https://sou= rce.codeaurora.org/external/imx/linux-imx/tree/sound/soc/fsl/fsl_sai.c?h=3D= lf-5.10.y
>> >> >
>> >> > ... is the reference I mentioned where I see multi-l= ane support in linux-imx 5.10.
>> >>
>> >> With the mainline SAI driver, it is possible to use sever= al channels.
>> >> Not sure what you mean by "multi-lane" in your = use-case.
>> >>
>> >> Please check:
>> >> https://bootli= n.com/blog/eight-channels-audio-on-i-mx7-with-pcm3168/
>> >
>> >
>> > I hoped folks would know what I was talking about without get= ting too far into the weeds.=C2=A0 But I guess I need to explain more.
>> >
>> > The older 5.4 kernels (and even 4 series kernels) had a imx8m= m-evk.dts sai section that looked like this:
>> >
>> > &sai1 {
>> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 pinctrl-names =3D "default&qu= ot;;
>> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 pinctrl-0 =3D <&pinctrl_sai= 1>;
>> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 assigned-clocks =3D <&clk I= MX8MM_CLK_SAI1>;
>> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 assigned-clock-parents =3D <&am= p;clk IMX8MM_AUDIO_PLL1_OUT>;
>> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 assigned-clock-rates =3D <24576= 000>;
>> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 clocks =3D <&clk IMX8MM_CLK= _SAI1_IPG>, <&clk IMX8MM_CLK_DUMMY>,
>> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <&a= mp;clk IMX8MM_CLK_SAI1_ROOT>, <&clk IMX8MM_CLK_DUMMY>,
>> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <&a= mp;clk IMX8MM_CLK_DUMMY>, <&clk IMX8MM_AUDIO_PLL1_OUT>,
>> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <&a= mp;clk IMX8MM_AUDIO_PLL2_OUT>;
>> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 clock-names =3D "bus", &= quot;mclk0", "mclk1", "mclk2", "mclk3", = "pll8k", "pll11k";
>> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 fsl,sai-multi-lane;
>> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 fsl,dataline,dsd =3D <0 0xff 0x= ff 2 0xff 0x11>;
>> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 fsl,sai-synchronous-rx;
>> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 dmas =3D <&sdma2 0 25 0>= , <&sdma2 1 25 0>;
>> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 #sound-dai-cells =3D <0>; >> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 status =3D "okay";
>> > };
>> >
>> > ... which has fsl,sai-multi-lane support.
>> >
>> > The current linux-fslc 5.10 kernel does not have fsl,sai-mult= i-lane support.
>>
>> linux-fslc-imx kernel recipe on the [master] branch on meta-freesc= ale
>> provides a kernel, which has linux-imx as a base and latest LTS >> applied on top.
>>
>> Assuming you're building now off the [master] branch and do no= t set
>> the IMX_DEFAULT_BSP to any value anywhere in your conf files - you=
>> will be building a Mainline BSP (see [1]), which does select
>> linux-fslc as a preferred provider for your kernel, see [2].
>>
>> You can try to either switch your BSP to NXP one by setting
>> IMX_DEFAULT_BSP =3D "nxp", or switch your kernel provide= r to
>> "linux-fslc-imx" one.
>
>
> I really would like to stick with linux-fslc since that's what we&= #39;ve been using for more than a year now.=C2=A0 Kind of scared to switch = back to linux-fslc-imx (I'll try to do better with my terminology) but = if you guys think that's best then I'll try it.=C2=A0 Worried that = our custom apps might be impacted by the switch.
>
>>
>> As a quick GIT grep in the linux-fslc repo on [5.10-2.1.x-imx] bra= nch:
>> git grep sai-multi-lane
>> arch/arm64/boot/dts/freescale/imx8mm-evk-ak4497.dts:=C2=A0 =C2=A0 = fsl,sai-multi-lane;
>> arch/arm64/boot/dts/freescale/imx8mm-evk.dtsi:=C2=A0 fsl,sai-multi= -lane;
>> arch/arm64/boot/dts/freescale/imx8mp-ab2.dts:=C2=A0 =C2=A0fsl,sai-= multi-lane;
>> arch/arm64/boot/dts/freescale/imx8mq-evk-ak4497.dts:=C2=A0 =C2=A0 = fsl,sai-multi-lane;
>> arch/arm64/boot/dts/freescale/imx8mq-evk.dts:=C2=A0 =C2=A0fsl,sai-= multi-lane;
>> sound/soc/fsl/fsl_sai.c:=C2=A0 =C2=A0 =C2=A0 =C2=A0 if (of_find_pr= operty(np,
>> "fsl,sai-multi-lane", NULL))
>>
>> Guess this is what you're looking for, right?
>
>
> I'd be ok with doing a build of just the kernel on master branch a= s long as it supports imx8mm-evk (what our board is based on) but the rest = of our rootfs is based on Dunfell release.
>
> So if I'm following you correctly, you're saying the linux-fsl= c repo has imx 5.10 with multi-lane in it.

There are 2 kernel repositories here at play, namely:
- linux-fslc from Freescale GitHub
- linux-imx from CodeAurora

They both stem from stable korg, but using different strategy to evolve.
linux-imx is an NXP kernel fork, which they use to commit their
internal patches on top of some stable release. In case of 5.10 - it
is v5.10.54 from stable korg, which resides on [lf-5.10.y] branch.

linux-fslc is combination of various branches, and if we look at the
5.10 - there is a corresponding branch [5.10.x+fslc], and it is
practically a vanilla 5.10.y kernel from stable korg, with only
handful of patches on top.

If I to examine this like that:
$ git log --oneline --no-merges=C2=A0 stable/linux-5.10.y..5.10.x+fslc | wc= -l
9

As one can see, it has only 9 patches on top of stable korg.

What comes in addition inside linux-fslc repository, is the branch
[5.10-2.1.x-imx], which is a combination of [lf-5.10.y] branch from
linux-imx repo and latest stable patch applied on top of it (with
merge conflict resolution, of course).

When examined, it brings the following:
$ git log --oneline=C2=A0 --no-merges stable/linux-5.10.y..5.10-2.1.x-imx= =C2=A0 | wc -l
5456

Here we see, that there is a substantial difference in terms of number
of patches applied. It might be a new functionality (like your desired
multi-lane support), but can also contain a code in question, which
might not work for all scenarios you're applying your kernel to.

Hope that clears it a bit, and would help you to drive your decision
further on which kernel to use.

>
> How come linux-fslc 5.10 doesn't have it?=C2=A0 Is it a case where= imx released it later and hasn't worked it's way into linux-fslc y= et?

That is the trick: you most probably used the NXP-based up-merged
branch in your BSP, but now when switched to new Yocto release - you
received a vanilla kernel, which does not have those NXP patches
applied.

So I was in error.=C2=A0 I loo= ked back at the local.conf where our 5.4 kernel came from that we are happy= with (and has multi-lane) and it was linux-fslc-imx so I guess it's li= nux-fslc with some imx releases merged in.

When I = switched to 5.10 in hardknott it looks like it pulled in linux-fslc by defa= ult which looks pretty vanilla as you mentioned.

S= o I'll try what you said about "You can try to either switch your = BSP to NXP one by setting
IMX_DEFAULT_BSP =3D "nxp", or switch your kernel provider to
"linux-fslc-imx" one."

To try and g= et a linux-fslc-imx 5.10 build and see if it's got multi-lane in it.=C2= =A0 I was using hardknott when I originally got 5.10 so don't know if I= need to do a repo sync to get newer stuff or checkout master but would onl= y be interested in getting kernel and keeping our Dunfell based rootfs.

I'll go try some stuff.=C2=A0 Thanks for the inpu= t and advice.

Regards,

Br= ian



>
> I'd be willing to "try" 5.10.2.1.x-imx just to see if it= solves our problem but still would prefer to stick with linux-fslc ... but= if that's the only way to get this feature back I guess I'll have = to do what I need to do.
>
> I still get confused by linux-fslc, linux-imx linux-fslc-imx some.=C2= =A0 Which one would be the safest (aka most stable) for imx8mm ... and have= multi-lane support?
>
> Thanks again for putting up with my dumb questions and weird issues.= =C2=A0 Everything was ok until we had to step up to 5.4 in order to pick up= some DSA PTP (1588) patches.
>
> Regards,
>
> Brian
>


--
Regards,
Andrey.
--0000000000002880ff05cf57b4ce--