[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a1R=K5c7e9c72b4j612YVUoFzPs_+v8jN4FfBfWs+Ut-A@mail.gmail.com>
Date: Mon, 16 Oct 2017 14:34:33 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Bin Meng <bmeng.cn@...il.com>
Cc: Cyrille Pitchen <cyrille.pitchen@...ev4u.fr>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Boris Brezillon <boris.brezillon@...e-electrons.com>,
Marek Vasut <marek.vasut@...il.com>,
Brian Norris <computersforpeace@...il.com>,
Richard Weinberger <richard@....at>,
David Woodhouse <dwmw2@...radead.org>,
linux-mtd <linux-mtd@...ts.infradead.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
Stefan Roese <sr@...x.de>
Subject: Re: [PATCH] spi-nor: intel-spi: Fix Kconfig dependency to LPC_ICH
On Sun, Oct 15, 2017 at 3:38 PM, Bin Meng <bmeng.cn@...il.com> wrote:
> On Fri, Oct 13, 2017 at 7:15 PM, Arnd Bergmann <arnd@...db.de> wrote:>> On Wed, Oct 11, 2017 at 10:03 AM, Cyrille Pitchen
>> warning: (SPI_INTEL_SPI_PLATFORM && ITCO_WDT) selects LPC_ICH which
>> has unmet direct dependencies (HAS_IOMEM && PCI)
>> drivers/mfd/lpc_ich.c: In function 'lpc_ich_init_spi':
>> drivers/mfd/lpc_ich.c:1137:3: error: implicit declaration of function
>> 'pci_bus_write_config_byte'; did you mean 'pci_write_config_byte'?
>> [-Werror=implicit-function-declaration]
>>
>
> Thanks for your testing. However, I believe this build error cannot be
> seen in a real system due to x86 always has PCI on. But I see you were
> doing build testing with COMPILE_TEST.
I don't think there is a general dependency on PCI for x86, other
than the fact that most device drivers require it and you'd normally
want to enable it.
>> Also, the 'depends on EXPERT' statement looks misplaced,
>> enabling EXPERT should only be there to allow you to turn
>> extra things *off*, not to hide device drivers.
>>
>
> I will leave this to Mika to comment the "EXPERT" usage. If we remove
> this, I think that should be another patch and the documentation of
> this driver should be updated too.
Ok.
>> How about this:
>>
>> diff --git a/drivers/mtd/spi-nor/Kconfig b/drivers/mtd/spi-nor/Kconfig
>> index 19bcb63a1ce7..b81d9b4dae7b 100644
>> --- a/drivers/mtd/spi-nor/Kconfig
>> +++ b/drivers/mtd/spi-nor/Kconfig
>> @@ -90,7 +90,7 @@ config SPI_INTEL_SPI
>> tristate
>>
>> config SPI_INTEL_SPI_PCI
>> - tristate "Intel PCH/PCU SPI flash PCI driver" if EXPERT
>> + tristate "Intel PCH/PCU SPI flash PCI driver"
>> depends on X86 && PCI
>> select SPI_INTEL_SPI
>> help
>> @@ -106,10 +106,10 @@ config SPI_INTEL_SPI_PCI
>> will be called intel-spi-pci.
>>
>> config SPI_INTEL_SPI_PLATFORM
>> - tristate "Intel PCH/PCU SPI flash platform driver" if EXPERT
>> - depends on X86
>> + tristate "Intel PCH/PCU SPI flash platform driver"
>> + depends on X86 && (PCI || COMPILE_TEST)
>> select SPI_INTEL_SPI
>> - select LPC_ICH
>> + select LPC_ICH if PCI
>
> I think we just need do:
>
> depends on X86 && PCI
>
> then
>
> select LPC_ICH
Right, that would solve this particular build issue, just not
allow the compile-test alternative.
We could also try to fix this more broadly, to allow compile-testing
independent of X86: It is bad style to have a 'select' statement for
a user-visible symbol (both in my version above, and yours).
The only connection I see between LPC_ICH and
SPI_INTEL_SPI_PCI is that at the moment that MFD driver is the
only thing that provides a platform device named "intel-spi", but I
see no reason why the spi-nor driver needs to know about this.
In similar cases on ARM, I tend to recommend something like
config SPI_INTEL_SPI_PLATFORM
tristate "Intel PCH/PCU SPI flash platform driver" if LPC_ICH
|| COMPILE_TEST
select SPI_INTEL_SPI
and then change all the other 'select LPC_ICH' to 'depends on
as well. If we leave the 'select' in place here, it might be good to
remove the prompt from the LPC_ICH option and have it only
selected by the other drivers.
Arnd
Powered by blists - more mailing lists