From: Lee Jones <lee@kernel.org>
To: Julien Panis <jpanis@baylibre.com>
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
corbet@lwn.net, arnd@arndb.de, gregkh@linuxfoundation.org,
derek.kiernan@xilinx.com, dragan.cvetic@xilinx.com,
yi.l.liu@intel.com, jgg@ziepe.ca, razor@blackwall.org,
stephen@networkplumber.org, prabhakar.csengg@gmail.com,
contact@emersion.fr, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
sterzik@ti.com, u-kumar1@ti.com, eblanc@baylibre.com,
jneanne@baylibre.com
Subject: Re: [PATCH v5 0/4] TI TPS6594 PMIC support (Core, ESM, PFSM)
Date: Thu, 30 Mar 2023 18:10:05 +0100 [thread overview]
Message-ID: <20230330171005.GC548901@google.com> (raw)
In-Reply-To: <20230330082006.11216-1-jpanis@baylibre.com>
On Thu, 30 Mar 2023, Julien Panis wrote:
> TPS6594 is a Power Management IC which provides regulators and others
> features like GPIOs, RTC, watchdog, ESMs (Error Signal Monitor), and
> PFSM (Pre-configurable Finite State Machine). The SoC and the PMIC can
> communicate through the I2C or SPI interfaces.
> TPS6594 is the super-set device while TPS6593 and LP8764 are derivatives.
Note to future me: once the misc drivers are good to go, route through MFD.
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2023-03-30 17:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 8:20 [PATCH v5 0/4] TI TPS6594 PMIC support (Core, ESM, PFSM) Julien Panis
2023-03-30 8:20 ` [PATCH v5 1/4] dt-bindings: mfd: Add TI TPS6594 PMIC Julien Panis
2023-03-30 8:40 ` Krzysztof Kozlowski
2023-03-30 14:25 ` Rob Herring
2023-03-30 8:20 ` [PATCH v5 2/4] mfd: tps6594: Add driver for " Julien Panis
2023-03-30 8:20 ` [PATCH v5 3/4] misc: tps6594-esm: Add driver for TI TPS6594 ESM Julien Panis
2023-03-30 8:20 ` [PATCH v5 4/4] misc: tps6594-pfsm: Add driver for TI TPS6594 PFSM Julien Panis
2023-03-30 8:35 ` Greg KH
2023-03-30 15:45 ` Julien Panis
2023-03-30 17:10 ` Lee Jones [this message]
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=20230330171005.GC548901@google.com \
--to=lee@kernel.org \
--cc=arnd@arndb.de \
--cc=contact@emersion.fr \
--cc=corbet@lwn.net \
--cc=derek.kiernan@xilinx.com \
--cc=devicetree@vger.kernel.org \
--cc=dragan.cvetic@xilinx.com \
--cc=eblanc@baylibre.com \
--cc=gregkh@linuxfoundation.org \
--cc=jgg@ziepe.ca \
--cc=jneanne@baylibre.com \
--cc=jpanis@baylibre.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prabhakar.csengg@gmail.com \
--cc=razor@blackwall.org \
--cc=robh+dt@kernel.org \
--cc=stephen@networkplumber.org \
--cc=sterzik@ti.com \
--cc=u-kumar1@ti.com \
--cc=yi.l.liu@intel.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).