Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <696cb2da-20b9-b3dd-46d9-de4bf91a1506@gmail.com>
 <22bc845c-dffc-7967-a542-f0697feec603@gmail.com> <7be3df2e-2250-8542-1707-121373213fe1@gmail.com>
In-Reply-To: <7be3df2e-2250-8542-1707-121373213fe1@gmail.com>
From:   Saravana Kannan <saravanak@google.com>
Date:   Tue, 30 Aug 2022 00:18:21 -0700
Message-ID: <CAGETcx-3AkOjmx+=vwiiYfDc8tGNnSa+MTyEeB92Xgou0zWKPA@mail.gmail.com>
Subject: Re: fw_devlink=on breaks probing devices when of_platform_populate()
 is used
To:     =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= <zajec5@gmail.com>
Cc:     Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        "Rafael J. Wysocki" <rafael@kernel.org>,
        "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
        Ansuel Smith <ansuelsmth@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Sun, Aug 28, 2022 at 7:39 AM Rafa=C5=82 Mi=C5=82ecki <zajec5@gmail.com> =
wrote:
>
> On 30.07.2022 09:36, Rafa=C5=82 Mi=C5=82ecki wrote:
> > On 16.07.2022 22:50, Rafa=C5=82 Mi=C5=82ecki wrote:
> >> I added of_platform_populate() calls in mtd subsystem in the commit
> >> bcdf0315a61a2 ("mtd: call of_platform_populate() for MTD partitions"):
> >> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/com=
mit/?id=3Dbcdf0315a61a29eb753a607d3a85a4032de72d94
> >>
> >> I recently backported that commit in OpenWrt to kernels 5.10 and 5.15.
> >> We started receiving reports that probing Ethernet devices stopped
> >> working in kernel 5.15. I bisected it down to the kernel 5.13 change:
> >>
> >> commit ea718c699055c8566eb64432388a04974c43b2ea (refs/bisect/bad)
> >> Author: Saravana Kannan <saravanak@google.com>
> >> Date:   Tue Mar 2 13:11:32 2021 -0800
> >>
> >>      Revert "Revert "driver core: Set fw_devlink=3Don by default""
> >>
> >>      This reverts commit 3e4c982f1ce75faf5314477b8da296d2d00919df.
> >>
> >>      Since all reported issues due to fw_devlink=3Don should be addres=
sed by
> >>      this series, revert the revert. fw_devlink=3Don Take II.
> >>
> >>      Signed-off-by: Saravana Kannan <saravanak@google.com>
> >>      Link: https://lore.kernel.org/r/20210302211133.2244281-4-saravana=
k@google.com
> >>      Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> >>
> >> For me with above commit kernel just never calls bcm4908_enet_probe().
> >> Reverting it from the top of 5.13.19 and 5.15.50 fixes it. I believe t=
he
> >> same issue happens with other drivers.
> >>
> >> Critical detail is that in DT Ethernet block node references NVMEM cel=
l
> >> of MTD partition (see below).
> >>
> >> Could you help me dealing with this issue, please? Can you see somethi=
ng
> >> obvious breaking fw_devlink=3Don + of_platform_populate() case? Can I
> >> provide some extra information to help fixing it?
> >
> > Any ideas about this problem / solution?
>
> I didn't get any reponse for this bug for 6 weeks now. Is that OK if I
> send a revert patch then?

fw_devlink=3Don and of_platform_populate() have been working without any
problems for a while now. If your MTD change is causing an issue, why
not start debugging from there instead of suggesting reverting a
change that has been there before your change?

Most of us are busy getting stuff ready for LPC. So, things are going
to be a bit slow. I'm also working on other fw_devlink fixes. I can't
get to this quickly. So if you can debug this further and point out
where exactly it's getting caught up that'd help.

Enabling debug logs in drivers/base/core.c and drivers/base/dd.c might
make it easier for you to debug. Also, you can check the
<debugfs>/devices_deferred to tell why a device isn't getting probed
yet.

-Saravana

>
>
> >> Relevant DT part:
> >>
> >> partitions {
> >>      compatible =3D "fixed-partitions";
> >>      #address-cells =3D <1>;
> >>      #size-cells =3D <1>;
> >>
> >>      partition@0 {
> >>          compatible =3D "nvmem-cells";
> >>          reg =3D <0x0 0x100000>;
> >>          label =3D "bootloader";
> >>
> >>          #address-cells =3D <1>;
> >>          #size-cells =3D <1>;
> >>          ranges =3D <0 0x0 0x100000>;
> >>
> >>          base_mac_addr: mac@106a0 {
> >>              reg =3D <0x106a0 0x6>;
> >>          };
> >>      };
> >>
> >>      partition@100000 {
> >>          reg =3D <0x100000 0x5700000>;
> >>          label =3D "firmware";
> >>      };
> >> };
> >>
> >> ethernet@2000 {
> >>      compatible =3D "brcm,bcm4908-enet";
> >>      reg =3D <0x2000 0x1000>;
> >>
> >>      interrupts =3D <GIC_SPI 86 IRQ_TYPE_LEVEL_HIGH>,
> >>              <GIC_SPI 87 IRQ_TYPE_LEVEL_HIGH>;
> >>      interrupt-names =3D "rx", "tx";
> >>
> >>      nvmem-cells =3D <&base_mac_addr>;
> >>      nvmem-cell-names =3D "mac-address";
> >> };
> >>
> >> OpenWrt bug report:
> >> https://github.com/openwrt/openwrt/issues/10232
>