From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Jerome Neanne <jneanne@baylibre.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Tony Lindgren <tony@atomide.com>, Lee Jones <lee@kernel.org>,
khilman@baylibre.com, msp@baylibre.com, francesco@dolcini.it,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-omap@vger.kernel.org,
Jonathan Cormier <jcormier@criticallink.com>
Subject: Re: [PATCH v5 1/2] gpio: tps65219: add GPIO support for TPS65219 PMIC
Date: Tue, 13 Jun 2023 14:50:29 +0200 [thread overview]
Message-ID: <CAMRc=MdsGEePA55NSP3A7MBGWY_a-vNH9z8dOfCM_d0MphA4uQ@mail.gmail.com> (raw)
In-Reply-To: <20230511-tps65219-add-gpio-support-v5-1-ebb94281c854@baylibre.com>
On Wed, Jun 7, 2023 at 4:39 PM Jerome Neanne <jneanne@baylibre.com> wrote:
>
> Add support for TPS65219 PMICs GPIO interface.
>
> 3 GPIO pins:
> - GPIO0 only is IO but input mode reserved for MULTI_DEVICE_ENABLE usage.
> - GPIO1 and GPIO2 are Output only and referred as GPO1 and GPO2 in spec.
>
> GPIO0 is statically configured as input or output prior to Linux boot.
> it is used for MULTI_DEVICE_ENABLE function.
> This setting is statically configured by NVM.
> GPIO0 can't be used as a generic GPIO (specification Table 8-34).
> It's either a GPO when MULTI_DEVICE_EN=0 or a GPI when MULTI_DEVICE_EN=1.
>
> Datasheet describes specific usage for non standard GPIO.
>
> Datasheet: https://www.ti.com/lit/ds/symlink/tps65219.pdf
> Co-developed-by: Jonathan Cormier <jcormier@criticallink.com>
> Signed-off-by: Jonathan Cormier <jcormier@criticallink.com>
> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
> Signed-off-by: Jerome Neanne <jneanne@baylibre.com>
> ---
Applied, thanks!
Bart
next prev parent reply other threads:[~2023-06-13 12:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 14:39 [PATCH v5 0/2] Add support for TI TPS65219 PMIC GPIO interface Jerome Neanne
2023-06-07 14:39 ` [PATCH v5 1/2] gpio: tps65219: add GPIO support for TPS65219 PMIC Jerome Neanne
2023-06-07 16:44 ` andy.shevchenko
2023-06-13 12:50 ` Bartosz Golaszewski [this message]
2023-06-07 14:39 ` [PATCH v5 2/2] mfd: tps65219: Add gpio cell instance Jerome Neanne
2023-06-08 12:34 ` Lee Jones
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='CAMRc=MdsGEePA55NSP3A7MBGWY_a-vNH9z8dOfCM_d0MphA4uQ@mail.gmail.com' \
--to=brgl@bgdev.pl \
--cc=francesco@dolcini.it \
--cc=jcormier@criticallink.com \
--cc=jneanne@baylibre.com \
--cc=khilman@baylibre.com \
--cc=lee@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=msp@baylibre.com \
--cc=tony@atomide.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).