From: Linus Walleij <linus.walleij@linaro.org>
To: Esteban Blanc <eblanc@baylibre.com>
Cc: lgirdwood@gmail.com, broonie@kernel.org, a.zummo@towertech.it,
alexandre.belloni@bootlin.com, linux-kernel@vger.kernel.org,
linux-gpio@vger.kernel.org, linux-rtc@vger.kernel.org,
jpanis@baylibre.com, jneanne@baylibre.com,
aseketeli@baylibre.com, sterzik@ti.com, u-kumar1@ti.com
Subject: Re: [PATCH v3 2/3] pinctrl: tps6594: add for TPS6594 PMIC
Date: Fri, 21 Apr 2023 10:34:34 +0200 [thread overview]
Message-ID: <CACRpkdab_26D9BMGeSygy_oa6SFa62ytXcy+Ydi3yPzQO3tU4A@mail.gmail.com> (raw)
In-Reply-To: <20230414101217.1342891-3-eblanc@baylibre.com>
Hi Esteban,
thanks for your patch!
On Fri, Apr 14, 2023 at 12:12 PM Esteban Blanc <eblanc@baylibre.com> wrote:
> TI TPS6594 PMIC has 11 GPIOs which can be used for different
> functions.
>
> This add a pinctrl and pinmux drivers in order to use those functions.
>
> Signed-off-by: Esteban Blanc <eblanc@baylibre.com>
(...)
> +config PINCTRL_TPS6594
> + tristate "Pinctrl and GPIO driver for TI TPS6594 PMIC"
> + depends on MFD_TPS6594
> + default MFD_TPS6594
> + select PINMUX
> + select GPIOLIB
select GPIO_REGMAP
?
I think this driver can use the GPIO_REGMAP helper library.
Please look into other drivers using this, such as
drivers/gpio/gpio-sl28cpld.c
Yours,
Linus Walleij
next prev parent reply other threads:[~2023-04-21 8:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 10:12 [PATCH v3 0/3] TI TPS6594 PMIC support (RTC, pinctrl, regulators) Esteban Blanc
2023-04-14 10:12 ` [PATCH v3 1/3] rtc: tps6594: add driver for TPS6594 PMIC RTC Esteban Blanc
2023-04-14 10:12 ` [PATCH v3 2/3] pinctrl: tps6594: add for TPS6594 PMIC Esteban Blanc
2023-04-21 8:34 ` Linus Walleij [this message]
2023-05-03 11:37 ` Esteban Blanc
2023-05-05 11:23 ` Linus Walleij
2023-05-05 11:31 ` Michael Walle
2023-05-05 12:10 ` Esteban Blanc
2023-04-14 10:12 ` [PATCH v3 3/3] regulator: tps6594-regulator: Add driver for TI TPS6594 regulators Esteban Blanc
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=CACRpkdab_26D9BMGeSygy_oa6SFa62ytXcy+Ydi3yPzQO3tU4A@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=aseketeli@baylibre.com \
--cc=broonie@kernel.org \
--cc=eblanc@baylibre.com \
--cc=jneanne@baylibre.com \
--cc=jpanis@baylibre.com \
--cc=lgirdwood@gmail.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=sterzik@ti.com \
--cc=u-kumar1@ti.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).