[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210201105204.GA1467@martin-debian-1.paytec.ch>
Date: Mon, 1 Feb 2021 11:52:04 +0100
From: Martin Kaiser <martin@...ser.cx>
To: Saravana Kannan <saravanak@...gle.com>
Cc: Rob Herring <robh+dt@...nel.org>,
Frank Rowand <frowand.list@...il.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-tegra <linux-tegra@...r.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>,
Linus Walleij <linus.walleij@...aro.org>,
Bartosz Golaszewski <bgolaszewski@...libre.com>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
Jon Hunter <jonathanh@...dia.com>,
Marc Zyngier <maz@...nel.org>,
Kevin Hilman <khilman@...libre.com>,
Android Kernel Team <kernel-team@...roid.com>
Subject: Re: [PATCH v2 0/2] of: property: Add fw_devlink support for more
props
Hi Saravana,
Thus wrote Saravana Kannan (saravanak@...gle.com):
> This series [1] has a high chance of fixing it for you if
> CONFIG_MODULES is disabled in your set up. Can you give it a shot?
sure. This fixes things for me if CONFIG_MODULES is disabled. Booting is
still stuck if modules are enabled.
> The real problem is that arch/arm/mach-imx/avic.c doesn't set the
> OF_POPULATED flag for the "fsl,avic" node. fw_devlink uses this
> information to know that this device node will never have a struct
> device created for it. The proper way to do this for root IRQCHIP
> nodes is to use IRQCHIP_DECLARE(). I Cc'ed you on a clean up patch for
> IMX [2], can you please give [2] a shot *without* [1] and with
> CONFIG_MODULES enabled? Things should boot properly with this
> combination too.
This works as well.
Thanks,
Martin
Powered by blists - more mailing lists