[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZaUAS2syv-hnE7qS@v2202401214221251712.nicesrv.de>
Date: Mon, 15 Jan 2024 10:52:11 +0100
From: Martin Kaiser <martin@...ser.cx>
To: Peng Fan <peng.fan@....com>
Cc: Linus Walleij <linus.walleij@...aro.org>,
Bartosz Golaszewski <brgl@...ev.pl>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] gpio: vf610: allow disabling the vf610 driver
Hi Peng,
Thus wrote Peng Fan (peng.fan@....com):
> Thanks Linus for Ccing me.
I did already Cc you on the initial patch. My hope was to get feedback about
unwanted side effects.
> > Subject: [PATCH] gpio: vf610: allow disabling the vf610 driver
> > The vf610 gpio driver is enabled by default for all i.MX machines, without any
> > option to disable it in a board-specific config file.
> > Most i.MX chipsets have no hardware for this driver. Change the default to
> > enable GPIO_VF610 for SOC_VF610 and disable it otherwise.
> > Add a text description after the bool type, this makes the driver selectable by
> > make config etc. i.MX chips other than SOC_VF610 can now enable the driver
> > from their board config.
> This will break i.MX8QM,DXL,ULP/i.MX93 boot. You could add text description
> to make it selectable, but please not drop def y. Or you need update defconfig.
Thanks for bringing this up.
It seems to me that other gpio drivers are disabled by default and enabled
where needed. I suggest adding CONFIG_GPIO_VF610=y to
arch/arm64/configs/defconfig and probably also to
arch/arm/configs/imx_v6_v7_defconfig.
I'll send a v2 with these changes unless you (or someone else) disagree.
Thanks,
Martin
Powered by blists - more mailing lists