From: "André Draszik" <andre.draszik@linaro.org>
To: Lee Jones <lee@kernel.org>, 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 <srinivas.kandagatla@linaro.org>,
Kees Cook <kees@kernel.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>
Cc: "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,
"André Draszik" <andre.draszik@linaro.org>
Subject: [PATCH v2 0/6] Maxim Integrated MAX77759 PMIC MFD-based drivers
Date: Wed, 26 Feb 2025 17:51:19 +0000 [thread overview]
Message-ID: <20250226-max77759-mfd-v2-0-a65ebe2bc0a9@linaro.org> (raw)
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'
Signed-off-by: André Draszik <andre.draszik@linaro.org>
---
Changes in v2:
- reorder bindings patches to avoid validation failures
- add dependency information to cover letter (Krzysztof)
- fix max77759_gpio_direction_from_control() in gpio driver
- Link to v1: https://lore.kernel.org/r/20250224-max77759-mfd-v1-0-2bff36f9d055@linaro.org
---
André Draszik (6):
dt-bindings: gpio: add max77759 binding
dt-bindings: nvmem: add max77759 binding
dt-bindings: mfd: add max77759 binding
mfd: max77759: add Maxim MAX77759 core mfd driver
gpio: max77759: add Maxim MAX77759 gpio driver
nvmem: max77759: add Maxim MAX77759 NVMEM driver
.../bindings/gpio/maxim,max77759-gpio.yaml | 44 ++
.../devicetree/bindings/mfd/maxim,max77759.yaml | 104 +++
.../bindings/nvmem/maxim,max77759-nvmem.yaml | 32 +
MAINTAINERS | 10 +
drivers/gpio/Kconfig | 13 +
drivers/gpio/Makefile | 1 +
drivers/gpio/gpio-max77759.c | 528 +++++++++++++++
drivers/mfd/Kconfig | 20 +
drivers/mfd/Makefile | 1 +
drivers/mfd/max77759.c | 737 +++++++++++++++++++++
drivers/nvmem/Kconfig | 12 +
drivers/nvmem/Makefile | 2 +
drivers/nvmem/max77759-nvmem.c | 156 +++++
include/linux/mfd/max77759.h | 98 +++
14 files changed, 1758 insertions(+)
---
base-commit: 0226d0ce98a477937ed295fb7df4cc30b46fc304
change-id: 20250224-max77759-mfd-aaa7a3121b62
Best regards,
--
André Draszik <andre.draszik@linaro.org>
next reply other threads:[~2025-02-26 17:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 17:51 André Draszik [this message]
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)
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=20250226-max77759-mfd-v2-0-a65ebe2bc0a9@linaro.org \
--to=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=robh@kernel.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;
as well as URLs for NNTP newsgroup(s).