All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Julien Panis <jpanis@baylibre.com>
Cc: lee@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	corbet@lwn.net, arnd@arndb.de, gregkh@linuxfoundation.org,
	derek.kiernan@xilinx.com, dragan.cvetic@xilinx.com,
	eric.auger@redhat.com, jgg@ziepe.ca, razor@blackwall.org,
	stephen@networkplumber.org, davem@davemloft.net,
	christian.koenig@amd.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 v2 0/4] TI TPS6594 PMIC support (Core, ESM, PFSM)
Date: Mon, 20 Mar 2023 10:40:05 -0500	[thread overview]
Message-ID: <20230320154005.GA1733616-robh@kernel.org> (raw)
In-Reply-To: <20230315110736.35506-1-jpanis@baylibre.com>

On Wed, Mar 15, 2023 at 12:07:32PM +0100, 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 LP8764X are derivatives.
> 
> This series adds support to TI TPS6594 PMIC and its derivatives.
> 
> The features implemented in this series are:
> - Core (MFD I2C and SPI entry points)
> - ESM (child device)
> - PFSM (child device)
> 
> - Core description:
> I2C and SPI interface protocols are implemented, with and without
> the bit-integrity error detection feature (CRC mode).
> In multi-PMIC configuration, all instances share a single GPIO of
> the SoC to generate interrupt requests via their respective nINT
> output pin.
> 
> - ESM description:
> This device monitors the SoC error output signal at its nERR_SOC
> input pin. In error condition, ESM toggles its nRSTOUT_SOC pin
> to reset the SoC.
> Basically, ESM driver starts ESM hardware.
> 
> - PFSM description:
> Strictly speaking, PFSM is not hardware. It is a piece of code.
> PMIC integrates a state machine which manages operational modes.
> Depending on the current operational mode, some voltage domains
> remain energized while others can be off.
> PFSM driver can be used to trigger transitions between configured
> states.
> 
> Link to v1:
> https://lore.kernel.org/all/20230216114410.183489-1-jpanis@baylibre.com/
> 
> Others series will be submitted over the next few weeks, providing
> drivers for others child devices like GPIOs (pinctrl), RTC, and
> regulators. Board support will also be added (device trees).

I don't care about the drivers, but I need a complete binding for 
the device to review it.

Rob

      parent reply	other threads:[~2023-03-20 15:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-15 11:07 [PATCH v2 0/4] TI TPS6594 PMIC support (Core, ESM, PFSM) Julien Panis
2023-03-15 11:07 ` [PATCH v2 1/4] dt-bindings: mfd: Add TI TPS6594 PMIC Julien Panis
2023-03-20 15:53   ` Rob Herring
2023-03-20 16:35     ` Julien Panis
2023-03-21  7:36       ` Krzysztof Kozlowski
2023-03-21  9:03         ` Julien Panis
2023-03-21 10:32           ` Krzysztof Kozlowski
2023-03-21 10:48             ` Julien Panis
2023-03-21 16:37     ` [EXTERNAL] " Sterzik, Chris
2023-03-15 11:07 ` [PATCH v2 2/4] mfd: tps6594: Add driver for " Julien Panis
2023-03-16 16:20   ` Lee Jones
2023-03-15 11:07 ` [PATCH v2 3/4] misc: tps6594-esm: Add driver for TI TPS6594 ESM Julien Panis
2023-03-15 11:07 ` [PATCH v2 4/4] misc: tps6594-pfsm: Add driver for TI TPS6594 PFSM Julien Panis
2023-03-15 11:34   ` Greg KH
2023-03-15 11:48     ` Julien Panis
2023-03-20 15:40 ` Rob Herring [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=20230320154005.GA1733616-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=arnd@arndb.de \
    --cc=christian.koenig@amd.com \
    --cc=contact@emersion.fr \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=derek.kiernan@xilinx.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dragan.cvetic@xilinx.com \
    --cc=eblanc@baylibre.com \
    --cc=eric.auger@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jgg@ziepe.ca \
    --cc=jneanne@baylibre.com \
    --cc=jpanis@baylibre.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lee@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=razor@blackwall.org \
    --cc=stephen@networkplumber.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.