From: Lee Jones <lee@kernel.org>
To: "André Draszik" <andre.draszik@linaro.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Srinivas Kandagatla <srini@kernel.org>,
Kees Cook <kees@kernel.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Peter Griffin <peter.griffin@linaro.org>,
Tudor Ambarus <tudor.ambarus@linaro.org>,
Will McVicker <willmcvicker@google.com>,
kernel-team@android.com, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-hardening@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH v10 0/3] Maxim Integrated MAX77759 PMIC MFD-based drivers
Date: Fri, 9 May 2025 15:26:04 +0100 [thread overview]
Message-ID: <20250509142604.GF2492385@google.com> (raw)
In-Reply-To: <20250509-max77759-mfd-v10-0-962ac15ee3ef@linaro.org>
On Fri, 09 May 2025, André Draszik wrote:
> Hi,
>
> This series improves support for the Maxim Integrated MAX77759
> companion PMIC for USB Type-C applications using the MFD framework.
>
> This series must be applied in-order, due to interdependencies of some
> of the patches:
> * to avoid use of undocumented compatibles by the newly added drivers,
> the bindings are added first in this series
> * patch 1 ("dt-bindings: gpio: add max77759 binding") also creates a
> new MAINTAINERS entry, including a wildcard match for the other
> bindings in this series
> * patch 3 ("dt-bindings: mfd: add max77759 binding") references the
> bindings added in patch 1 and 2 and can not work if those aren't
> available
> * patch 4 ("mfd: max77759: add Maxim MAX77759 core mfd driver") adds
> the core MFD driver, which also exposes an API to its leaf drivers
> and is used by patches 5 and 6
> * patches 5 and 6 won't compile without patch 4
>
> The MAX77759 PMIC includes Battery Charger, Fuel Gauge, temperature
> sensors, USB Type-C Port Controller (TCPC), NVMEM, and a GPIO expander.
>
> This PMIC is used on the Google Pixel 6 and 6 Pro (oriole / raven).
>
> This series adds support for the top-level MFD device, the gpio, and
> nvmem cells. Other components are excluded for the following reasons:
>
> While in the same package, Fuel Gauge and TCPC have separate and
> independent I2C addresses, register maps, interrupt lines, and
> aren't part of the top-level package interrupt hierarchy.
> Furthermore, a driver for the TCPC part exists already (in
> drivers/usb/typec/tcpm/tcpci_maxim_core.c).
>
> I'm leaving out temperature sensors and charger in this submission,
> because the former are not in use on Pixel 6 and I therefore can
> not test them, and the latter can be added later, once we look at
> the whole charging topic in more detail.
>
> To make maintainers' work easier, I am planning to send the relevant
> DTS and defconfig changes via a different series, unless everything
> is expected to go via Lee's MFD tree in one series?
>
> Cheers,
> Andre'
Okay, this (and the DT bindings) has been applied and submitted for
testing. Once successful, I'll get a PR out for the other maintainers
to pull from.
Note to self: ib-mfd-gpio-nvmem-6.16
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2025-05-09 14:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 13:22 [PATCH v10 0/3] Maxim Integrated MAX77759 PMIC MFD-based drivers André Draszik
2025-05-09 13:22 ` [PATCH v10 1/3] mfd: max77759: add Maxim MAX77759 core mfd driver André Draszik
2025-05-09 13:22 ` [PATCH v10 2/3] gpio: max77759: add Maxim MAX77759 gpio driver André Draszik
2025-05-13 13:23 ` Linus Walleij
2025-05-09 13:22 ` [PATCH v10 3/3] nvmem: max77759: add Maxim MAX77759 NVMEM driver André Draszik
2025-05-09 13:52 ` [PATCH v10 0/3] Maxim Integrated MAX77759 PMIC MFD-based drivers Peter Griffin
2025-05-09 14:21 ` Lee Jones
2025-05-09 14:26 ` Lee Jones [this message]
2025-05-13 9:33 ` [GIT PULL] Immutable branch between MFD, GPIO and NVMEM due for the v6.16 merge window 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=20250509142604.GF2492385@google.com \
--to=lee@kernel.org \
--cc=andre.draszik@linaro.org \
--cc=bartosz.golaszewski@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=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=robh@kernel.org \
--cc=srini@kernel.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 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.