From: "Rob Herring (Arm)" <robh@kernel.org>
To: "André Draszik" <andre.draszik@linaro.org>
Cc: "Gustavo A. R. Silva" <gustavoars@kernel.org>,
devicetree@vger.kernel.org,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
kernel-team@android.com, linux-gpio@vger.kernel.org,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Lee Jones <lee@kernel.org>,
Tudor Ambarus <tudor.ambarus@linaro.org>,
Kees Cook <kees@kernel.org>,
Will McVicker <willmcvicker@google.com>,
Peter Griffin <peter.griffin@linaro.org>,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org,
Bartosz Golaszewski <brgl@bgdev.pl>
Subject: Re: [PATCH v2 2/6] dt-bindings: nvmem: add max77759 binding
Date: Thu, 27 Feb 2025 07:05:12 -0600 [thread overview]
Message-ID: <174066151161.1829485.16000199455497636028.robh@kernel.org> (raw)
In-Reply-To: <20250226-max77759-mfd-v2-2-a65ebe2bc0a9@linaro.org>
On Wed, 26 Feb 2025 17:51:21 +0000, André Draszik wrote:
> The Maxim MAX77759 is a companion PMIC for USB Type-C applications and
> includes Battery Charger, Fuel Gauge, temperature sensors, USB Type-C
> Port Controller (TCPC), NVMEM, and a GPIO expander.
>
> This describes its storage module (NVMEM).
>
> Signed-off-by: André Draszik <andre.draszik@linaro.org>
>
> ---
> v2:
> * drop example as the MFD binding has a complete one (Rob)
>
> Note: MAINTAINERS doesn't need updating, the binding update for the
> first leaf device (gpio) adds a wildcard matching all max77759 bindings
> ---
> .../bindings/nvmem/maxim,max77759-nvmem.yaml | 32 ++++++++++++++++++++++
> 1 file changed, 32 insertions(+)
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2025-02-27 13:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 17:51 [PATCH v2 0/6] Maxim Integrated MAX77759 PMIC MFD-based drivers André Draszik
2025-02-26 17:51 ` [PATCH v2 1/6] dt-bindings: gpio: add max77759 binding André Draszik
2025-02-26 20:30 ` Rob Herring (Arm)
2025-02-27 11:19 ` André Draszik
2025-02-27 12:51 ` Rob Herring
2025-02-27 12:56 ` André Draszik
2025-02-27 13:01 ` Rob Herring (Arm)
2025-02-26 17:51 ` [PATCH v2 2/6] dt-bindings: nvmem: " André Draszik
2025-02-26 20:30 ` Rob Herring (Arm)
2025-02-27 13:05 ` Rob Herring (Arm) [this message]
2025-02-26 17:51 ` [PATCH v2 3/6] dt-bindings: mfd: " André Draszik
2025-02-27 13:04 ` Rob Herring
2025-02-27 13:13 ` André Draszik
2025-02-28 13:01 ` Rob Herring
2025-02-28 13:59 ` André Draszik
2025-02-26 17:51 ` [PATCH v2 4/6] mfd: max77759: add Maxim MAX77759 core mfd driver André Draszik
2025-02-26 17:51 ` [PATCH v2 5/6] gpio: max77759: add Maxim MAX77759 gpio driver André Draszik
2025-02-28 7:10 ` Linus Walleij
2025-02-28 10:58 ` André Draszik
2025-02-28 11:37 ` André Draszik
2025-02-26 17:51 ` [PATCH v2 6/6] nvmem: max77759: add Maxim MAX77759 NVMEM driver André Draszik
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=174066151161.1829485.16000199455497636028.robh@kernel.org \
--to=robh@kernel.org \
--cc=andre.draszik@linaro.org \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gustavoars@kernel.org \
--cc=kees@kernel.org \
--cc=kernel-team@android.com \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.griffin@linaro.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=tudor.ambarus@linaro.org \
--cc=willmcvicker@google.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