MIME-Version: 1.0
From:   Linus Walleij <linus.walleij@linaro.org>
Date:   Sat, 25 Feb 2023 15:28:52 +0100
Message-ID: <CACRpkdamxDX6EBVjKX5=D3rkHp17f5pwGdBVhzFU90-0MHY6dQ@mail.gmail.com>
Subject: Regression in probing some AMBA devices possibly devlink related
To:     Saravana Kannan <saravanak@google.com>,
        Linux ARM <linux-arm-kernel@lists.infradead.org>,
        linux-kernel <linux-kernel@vger.kernel.org>,
        Ulf Hansson <ulf.hansson@linaro.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

Hi Saravana,

I have a boot regression for Ux500 on mainline, but bisecting mainline
isn't quite working for misc reasons :/

I'm not sure about this regression, but it smells like devlink-related.

Ux500 have a bunch of normal and some AMBA devices. After
boot this happens and we hang waiting for rootfs (which is on eMMC):

[   31.849586] amba 80126000.mmc: deferred probe pending
[   31.854801] amba 80118000.mmc: deferred probe pending
[   31.859895] amba 80005000.mmc: deferred probe pending
[   31.870297] amba 80120000.uart: deferred probe pending
[   31.875472] amba 80121000.uart: deferred probe pending
[   31.880689] amba 80004000.i2c: deferred probe pending
[   31.885799] amba 80128000.i2c: deferred probe pending
[   31.890932] amba 80110000.i2c: deferred probe pending
[   51.688361] vmem_3v3: disabling

The last regulator (vmem_3v3) is something the eMMC that didn't
probe was supposed to use.

All the failing drivers are AMBA PrimeCell devices:
drivers/mmc/host/mmci.c
drivers/tty/serial/amba-pl011.c
drivers/i2c/busses/i2c-nomadik.c

This makes me suspect something was done for ordinary (platform)
devices that didn't happen for AMBA devices?

This is the main portion of the device tree containing these
devices and their resources:
arch/arm/boot/dts/ste-dbx5x0.dtsi

Any hints?

Yours,
Linus Walleij