On Mon, May 13, 2019 at 4:11 PM Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx> wrote: > > On Mon, May 13, 2019 at 03:32:52PM +0200, Sedat Dilek wrote: > > BTW, which Linux Kconfig setting are minimum? > > > > scripts/config -m NFC_NCI -m NFC_NXP_NCI -m NFC_NXP_NCI_I2C > > > > What about? > > > > scripts/config -m NFC_NCI_SPI -m NFC_NCI_UART -m I2C_GPIO -m SPI_GPIO > > > > Required? > > Not needed? > > I2C_GPIO and SPI_GPIO has nothing to do with all this. What indeed is needed is > the pin control of the actual Intel SoC (unfortunately I don't know what > exactly you have, so, you better to check yourself), something like > CONFIG_PINCTRL_SKYLAKE=y. > OK. What is with NFC_NCI_SPI and NFC_NCI_UART Kconfigs? I had never changed PINCTRL Kconfigs, so what I have is/was... $ grep PINCTRL .config | grep ^CONFIG | sort CONFIG_PINCTRL_AMD=y CONFIG_PINCTRL_BAYTRAIL=y CONFIG_PINCTRL_BROXTON=y CONFIG_PINCTRL_CHERRYVIEW=y CONFIG_PINCTRL_INTEL=y CONFIG_PINCTRL_SUNRISEPOINT=y CONFIG_PINCTRL=y Which one is this? And if PINCTRL_XXX is mandatory, shall it be added as Kconfig dependency in drivers/nfc/nxp-nci/Kconfig? - Sedat - P.S.: List of unset PINCTRL Kconfigs $ grep PINCTRL .config | grep ^'# CONFIG' | sort # CONFIG_DEBUG_PINCTRL is not set # CONFIG_PINCTRL_CANNONLAKE is not set # CONFIG_PINCTRL_CEDARFORK is not set # CONFIG_PINCTRL_DENVERTON is not set # CONFIG_PINCTRL_GEMINILAKE is not set # CONFIG_PINCTRL_ICELAKE is not set # CONFIG_PINCTRL_LEWISBURG is not set # CONFIG_PINCTRL_MCP23S08 is not set # CONFIG_PINCTRL_SX150X is not set
