From: Randy Dunlap <rdunlap@infradead.org>
To: Wells Lu <wellslutw@gmail.com>,
linus.walleij@linaro.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
devicetree@vger.kernel.org
Cc: qinjian@cqplus1.com, dvorkin@tibbo.com, Wells Lu <wells.lu@sunplus.com>
Subject: Re: [PATCH 1/3] pinctrl: Add driver for Sunplus SP7021
Date: Wed, 27 Oct 2021 15:12:04 -0700 [thread overview]
Message-ID: <3ed37bf9-d698-2a03-60e7-9b357e3abfb4@infradead.org> (raw)
In-Reply-To: <1635324926-22319-2-git-send-email-wells.lu@sunplus.com>
Hi--
On 10/27/21 1:55 AM, Wells Lu wrote:
> diff --git a/drivers/pinctrl/sunplus/Kconfig b/drivers/pinctrl/sunplus/Kconfig
> new file mode 100644
> index 0000000..93b5ccf
> --- /dev/null
> +++ b/drivers/pinctrl/sunplus/Kconfig
> @@ -0,0 +1,32 @@
> +# SPDX-License-Identifier: GPL-2.0
> +#
> +# Sunplus Pin control driver configuration
> +#
> +
> +config PINCTRL_SPPCTL
> + bool "Sunplus SP7021 pinmux and gpio driver"
Preferably GPIO
> + depends on SOC_SP7021
> + select PINMUX
> + select GENERIC_PINCTRL_GROUPS
> + select CONFIG_GENERIC_PINMUX_FUNCTIONS
Drop CONFIG_
> + select PINCONF
> + select GENERIC_PINCONF
> + select OF_GPIO
Probably
depends on OF && HAS_IOMEM
Otherwise how do you know that it's safe to do
select OF_GPIO
?
> + select GPIOLIB
> + select GPIO_SYSFS
> + select GENERIC_IRQ_CHIP
> + select GPIOLIB_IRQCHIP
> + help
> + Say Y here to support Sunplus SP7021 pinmux controller.
> + The driveer is selected automatically by platform.
driver
> + This driver requires the pinctrl framework.
> + GPIO is provided by the same driver.
> +
> +config PINCTRL_SPPCTL_DEBUG
> + bool "Sunplus pinmux specific debug"
> + depends on SOC_SP7021 && DEBUG_PINCTRL
> + help
> + Say Y if you need to debug Sunplus pinmux driver in-depth.
> + Pin control driver will output more messages if you enable
> + this item. This function is dependent on DEBUG_PINCTRL. It
> + should be enabled first.
thanks.
--
~Randy
next prev parent reply other threads:[~2021-10-27 22:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 8:55 [PATCH 0/3] Add pin control driver for Sunplus SP7021 SoC Wells Lu
2021-10-27 8:55 ` [PATCH 1/3] pinctrl: Add driver for Sunplus SP7021 Wells Lu
2021-10-27 22:12 ` Randy Dunlap [this message]
2021-10-29 3:40 ` Wells Lu 呂芳騰
2021-10-29 4:38 ` Randy Dunlap
2021-10-27 8:55 ` [PATCH 2/3] dt-bindings: pinctrl: Add dt-bindings " Wells Lu
2021-10-27 8:55 ` [PATCH 3/3] devicetree: bindings: pinctrl: Add bindings doc " Wells Lu
2021-11-09 3:59 ` Linus Walleij
[not found] ` <f315d79da3e742b4a4ec0131d6035046@sphcmbx02.sunplus.com.tw>
2021-11-18 12:20 ` Dvorkin Dmitry
2021-11-01 8:11 ` [PATCH v2 0/3] This is a patch series for pinctrl driver for Sunplus SP7021 SoC Wells Lu
2021-11-01 8:11 ` [PATCH v2 1/3] pinctrl: Add driver for Sunplus SP7021 Wells Lu
2021-11-09 4:30 ` Linus Walleij
2021-11-17 8:35 ` Wells Lu 呂芳騰
2021-11-01 8:11 ` [PATCH v2 2/3] dt-bindings: pinctrl: Add dt-bindings " Wells Lu
2021-11-12 15:37 ` Rob Herring
2021-11-18 9:03 ` Wells Lu 呂芳騰
2021-11-01 8:11 ` [PATCH v2 3/3] devicetree: bindings: pinctrl: Add bindings doc " Wells Lu
2021-11-12 15:40 ` Rob Herring
2021-11-18 9:15 ` Wells Lu 呂芳騰
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=3ed37bf9-d698-2a03-60e7-9b357e3abfb4@infradead.org \
--to=rdunlap@infradead.org \
--cc=devicetree@vger.kernel.org \
--cc=dvorkin@tibbo.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qinjian@cqplus1.com \
--cc=robh+dt@kernel.org \
--cc=wells.lu@sunplus.com \
--cc=wellslutw@gmail.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;
as well as URLs for NNTP newsgroup(s).