[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 2 Feb 2021 22:22:31 +0100
From: Martin Kaiser <martin@...ser.cx>
To: Saravana Kannan <saravanak@...gle.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Marek Szyprowski <m.szyprowski@...sung.com>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
Marc Zyngier <maz@...nel.org>,
Tudor Ambarus <Tudor.Ambarus@...rochip.com>,
Linus Walleij <linus.walleij@...aro.org>,
Bartosz Golaszewski <bgolaszewski@...libre.com>,
Rob Herring <robh+dt@...nel.org>,
Frank Rowand <frowand.list@...il.com>,
Len Brown <lenb@...nel.org>, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, linux-acpi@...r.kernel.org,
kernel-team@...roid.com
Subject: Re: [PATCH v2 0/3] Make fw_devlink=on more forgiving
Hi Saravana,
Thus wrote Saravana Kannan (saravanak@...gle.com):
> Martin,
> If you tested this series, can you please give a Tested-by?
I tested this v2 series on top of next-20210202 (without the fsl,avic
patch).
If modules are enabled, the kernel doesn't boot on my imx25 board. This
is expected, I guess.
With modules disabled, the kernel boots but probe fails for some
(non-mainline) drivers in my tree. All of those drivers have a gpio in
their device-tree node, such as
my_driver {
gpio_test1 = <&gpio1 0 0>;
...
};
with gpio1 from arch/arm/boot/dts/imx25.dtsi.
The probe function calls
of_get_named_gpio(np, "gpio_test1", 0);
to get the gpio. This fails with -EINVAL.
Best regards,
Martin
Powered by blists - more mailing lists