[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <d05578a6-eedc-4c2e-94e3-e00fa293e4bb@app.fastmail.com>
Date: Fri, 20 Jun 2025 15:45:44 +0200
From: "Arnd Bergmann" <arnd@...db.de>
To: "Bartosz Golaszewski" <brgl@...ev.pl>, "Arnd Bergmann" <arnd@...nel.org>
Cc: "Linus Walleij" <linus.walleij@...aro.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@...aro.org>,
"Sai Krishna Potthuri" <sai.krishna.potthuri@....com>,
"Geert Uytterhoeven" <geert+renesas@...der.be>,
"Bartosz Golaszewski" <bartosz.golaszewski@...aro.org>,
"Pratap Nirujogi" <pratap.nirujogi@....com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] pinctrl: zynq: add CONFIG_OF dependency
On Fri, Jun 20, 2025, at 15:36, Bartosz Golaszewski wrote:
> On Fri, Jun 20, 2025 at 3:08 PM Arnd Bergmann <arnd@...nel.org> wrote:
>> --- a/drivers/pinctrl/Kconfig
>> +++ b/drivers/pinctrl/Kconfig
>> @@ -603,6 +603,7 @@ config PINCTRL_TH1520
>> config PINCTRL_ZYNQ
>> bool "Pinctrl driver for Xilinx Zynq"
>> depends on ARCH_ZYNQ || COMPILE_TEST
>> + depends on OF
>> select PINMUX
>
> I don't think this is the actual problem. I can build (and link)
> pinctrl-zynq with COMPILE_OF disabled alright. Can you paste the
> entire offending .config somewhere?
This is from a randconfig build: https://pastebin.com/ism57RPe
Arnd
Powered by blists - more mailing lists