From: Randy Dunlap <rdunlap@infradead.org>
To: Quentin Schulz <quentin.schulz@free-electrons.com>,
linus.walleij@linaro.org
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
thomas.petazzoni@free-electrons.com,
linux-sunxi@googlegroups.com
Subject: Re: [PATCH] pinctrl: axp209: add missing Kconfig dependencies
Date: Thu, 14 Dec 2017 10:22:38 -0800 [thread overview]
Message-ID: <0aa972ed-dc37-4d03-7e08-95cc32f7a45e@infradead.org> (raw)
In-Reply-To: <20171214094335.899-1-quentin.schulz@free-electrons.com>
On 12/14/2017 01:43 AM, Quentin Schulz wrote:
> This fixes some compilation issues.
>
> GENERIC_PINCONF and OF at least for pinconf_generic_dt_*, PINMUX at
> least for pinmux_ops and GPIOLIB for at least gpio_chip.
>
> Fixes: 23f75d7dfa92 ("pinctrl: axp209: add pinctrl features")
>
> Reported-by: Randy Dunlab <rdunlap@infradead.org>
> Signed-off-by: Quentin Schulz <quentin.schulz@free-electrons.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> ---
> drivers/pinctrl/Kconfig | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/pinctrl/Kconfig b/drivers/pinctrl/Kconfig
> index ce126955212c..1dd445116432 100644
> --- a/drivers/pinctrl/Kconfig
> +++ b/drivers/pinctrl/Kconfig
> @@ -66,6 +66,10 @@ config PINCTRL_AS3722
> config PINCTRL_AXP209
> tristate "X-Powers AXP209 PMIC pinctrl and GPIO Support"
> depends on MFD_AXP20X
> + depends on OF
> + select PINMUX
> + select GENERIC_PINCONF
> + select GPIOLIB
> help
> AXP PMICs provides multiple GPIOs that can be muxed for different
> functions. This driver bundles a pinctrl driver to select the function
>
--
~Randy
next prev parent reply other threads:[~2017-12-14 18:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-14 9:43 Quentin Schulz
2017-12-14 18:22 ` Randy Dunlap [this message]
2017-12-20 8:14 ` Linus Walleij
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=0aa972ed-dc37-4d03-7e08-95cc32f7a45e@infradead.org \
--to=rdunlap@infradead.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=quentin.schulz@free-electrons.com \
--cc=thomas.petazzoni@free-electrons.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®