From: Tero Kristo <t-kristo@ti.com>
To: Keerthy <j-keerthy@ti.com>, <will.deacon@arm.com>,
<catalin.marinas@arm.com>, <shawnguo@kernel.org>
Cc: <lokeshvutla@ti.com>, <nm@ti.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: configs: Enable GPIO_DAVINCI
Date: Tue, 11 Jun 2019 21:19:28 +0300 [thread overview]
Message-ID: <09a60289-2747-a570-54e0-822b0ea4b01a@ti.com> (raw)
In-Reply-To: <20190605061401.25806-1-j-keerthy@ti.com>
On 05/06/2019 09:14, Keerthy wrote:
> Enable GPIO_DAVINCI and related configs for TI K3 AM6 platforms.
>
> Signed-off-by: Keerthy <j-keerthy@ti.com>
> ---
> arch/arm64/configs/defconfig | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
> index d1b72f99e2f4..57d7a4c207bd 100644
> --- a/arch/arm64/configs/defconfig
> +++ b/arch/arm64/configs/defconfig
> @@ -385,6 +385,9 @@ CONFIG_PINCTRL_QCS404=y
> CONFIG_PINCTRL_QDF2XXX=y
> CONFIG_PINCTRL_QCOM_SPMI_PMIC=y
> CONFIG_PINCTRL_SDM845=y
> +CONFIG_DEBUG_GPIO=y
Why DEBUG_GPIO?
> +CONFIG_GPIO_SYSFS=y
Also, why GPIO_SYSFS?
Both of the above are nice for debugging purposes, but should not be
enabled by default imho, as they are not needed by drivers.
> +CONFIG_GPIO_DAVINCI=y
I think you should not modify defconfig, rather add these as platform
required features under arch/arm64/Kconfig.platforms?
-Tero
> CONFIG_GPIO_DWAPB=y
> CONFIG_GPIO_MB86S7X=y
> CONFIG_GPIO_PL061=y
>
--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
next prev parent reply other threads:[~2019-06-11 18:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 6:14 Keerthy
2019-06-11 18:19 ` Tero Kristo [this message]
2019-06-12 1:44 ` keerthy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=09a60289-2747-a570-54e0-822b0ea4b01a@ti.com \
--to=t-kristo@ti.com \
--cc=catalin.marinas@arm.com \
--cc=j-keerthy@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=nm@ti.com \
--cc=shawnguo@kernel.org \
--cc=will.deacon@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®