[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190627143208.eeca4xyygml7s4n3@kahuna>
Date: Thu, 27 Jun 2019 09:32:08 -0500
From: Nishanth Menon <nm@...com>
To: Keerthy <j-keerthy@...com>
CC: <t-kristo@...com>, <will.deacon@....com>,
<catalin.marinas@....com>, <shawnguo@...nel.org>,
<linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>, <lokeshvutla@...com>
Subject: Re: [PATCH v2] arm64: Kconfig.platforms: Enable GPIO_DAVINCI for
ARCH_K3
On 16:39-20190627, Keerthy wrote:
> Enable GPIO_DAVINCI and related configs for TI K3 AM6 platforms.
>
> Signed-off-by: Keerthy <j-keerthy@...com>
> ---
>
> Changes in v2:
>
> * Enabling configs in Kconfig.platforms file instead of defconfig.
> * Removed GPIO_DEBUG config.
>
> arch/arm64/Kconfig.platforms | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/arm64/Kconfig.platforms b/arch/arm64/Kconfig.platforms
> index 4778c775de1b..6e43a0995ed4 100644
> --- a/arch/arm64/Kconfig.platforms
> +++ b/arch/arm64/Kconfig.platforms
> @@ -97,6 +97,8 @@ config ARCH_K3
> select TI_SCI_PROTOCOL
> select TI_SCI_INTR_IRQCHIP
> select TI_SCI_INTA_IRQCHIP
> + select GPIO_SYSFS
> + select GPIO_DAVINCI
Could you help explain the logic of doing this? commit message is
basically the diff in English. To me, this does NOT make sense.
I understand GPIO_DAVINCI is the driver compatible, but we cant do this for
every single SoC driver that is NOT absolutely mandatory for basic
functionality.
Also keep in mind the impact to arm64/configs/defconfig -> every single
SoC in the arm64 world will be now rebuild with GPIO_SYSFS.. why force
that?
--
Regards,
Nishanth Menon
Powered by blists - more mailing lists