[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <22ed864d-8d71-7042-4d55-2b0b65d4d281@kernel.org>
Date: Tue, 10 May 2022 10:40:11 +0300
From: Roger Quadros <rogerq@...nel.org>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
Tony Lindgren <tony@...mide.com>,
"open list:TI ETHERNET SWITCH DRIVER (CPSW)"
<linux-omap@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] memory: OMAP_GPMC should depend on ARCH_OMAP2PLUS ||
ARCH_K3
Geert,
On 10/05/2022 10:30, Geert Uytterhoeven wrote:
> Hi Roger,
>
> On Tue, May 10, 2022 at 9:22 AM Roger Quadros <rogerq@...nel.org> wrote:
>> On 09/05/2022 16:48, Geert Uytterhoeven wrote:
>>> The Texas Instruments OMAP General Purpose Memory Controller (GPMC) is
>>> only present on TI OMAP2/3/4/5, AM33xx, AM43x, DRA7xx, TI81xx, and K3
>>> SoCs. Hence add a dependency on ARCH_OMAP2PLUS || ARCH_K3, to prevent
>>> asking the user about this driver when configuring a kernel without
>>> OMAP2+ or K3 SoC family support.
>>>
>>> Fixes: be34f45f0d4aa91c ("memory: omap-gpmc: Make OMAP_GPMC config visible and selectable")
>>> Signed-off-by: Geert Uytterhoeven <geert+renesas@...der.be>
>
>>> --- a/drivers/memory/Kconfig
>>> +++ b/drivers/memory/Kconfig
>>> @@ -105,6 +105,7 @@ config TI_EMIF
>>> config OMAP_GPMC
>>> tristate "Texas Instruments OMAP SoC GPMC driver"
>>> depends on OF_ADDRESS
>>> + depends on ARCH_OMAP2PLUS || ARCH_K3 || COMPILE_TEST
>>> select GPIOLIB
>>> help
>>> This driver is for the General Purpose Memory Controller (GPMC)
>>
>> Is there any possibility that CONFIG_IRQ_DOMAIN is not set while both
>> OF_ADDRESS and COMPILE_TEST are set?
>>
>> That particular case will lead to build failures.
>>
>> e.g.
>> https://krzk.eu/#/builders/63/builds/162
>
> So it needs an additional dependency on IRQ_DOMAIN.
> That is a pre-existing problem, not caused by my patch (which adds
> more dependencies, and doesn't remove any).
Fair enough.
Could you please also add ARCH_KEYSTONE in the 'depends on' list
as some SoCs in that architecture do have the GPMC block.
cheers,
-roger
Powered by blists - more mailing lists