From: Karel Balej <karelb@gimli.ms.mff.cuni.cz>
To: Karel Balej <balejk@matfyz.cz>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>, Lee Jones <lee@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: "Duje Mihanović" <duje.mihanovic@skole.hr>,
~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org
Subject: [RFC PATCH v2 0/6] support for Marvell 88PM886 PMIC
Date: Sun, 11 Feb 2024 10:35:50 +0100 [thread overview]
Message-ID: <20240211094609.2223-1-karelb@gimli.ms.mff.cuni.cz> (raw)
From: Karel Balej <balejk@matfyz.cz>
Hello,
the following implements basic support for Marvell's 88PM886 PMIC which
is found for instance as a component of the samsung,coreprimevelte
smartphone which inspired this and also serves as a testing platform.
The code for the MFD is based primarily on this old series [1] with the
addition of poweroff based on the smartphone's downstream kernel tree
[2]. The onkey and regulators drivers are based on the latter. I am not
in possesion of the datasheet.
[1] https://lore.kernel.org/all/1434098601-3498-1-git-send-email-yizhang@marvell.com/
[2] https://github.com/CoderCharmander/g361f-kernel
Thank you and kind regards,
K. B.
---
RFC v2:
- Merge with the regulators series to have multiple devices and thus
justify the use of the MFD framework.
- Rebase on v6.8-rc3.
- Reorder patches.
- MFD RFC v1: https://lore.kernel.org/all/20231217131838.7569-1-karelb@gimli.ms.mff.cuni.cz/
- regulators RFC v1: https://lore.kernel.org/all/20231228100208.2932-1-karelb@gimli.ms.mff.cuni.cz/
Karel Balej (6):
dt-bindings: mfd: add entry for Marvell 88PM886 PMIC
mfd: add driver for Marvell 88PM886 PMIC
regulator: add regulators driver for Marvell 88PM886 PMIC
dt-bindings: input: add entry for Marvell 88PM88X PMICs onkey
input: add onkey driver for Marvell 88PM88X PMICs
MAINTAINERS: add myself for Marvell 88PM886 PMIC
.../bindings/input/marvell,88pm88x-onkey.yaml | 32 +++
.../bindings/mfd/marvell,88pm88x.yaml | 82 +++++++
.../regulator/marvell,88pm88x-regulator.yaml | 28 +++
MAINTAINERS | 11 +
drivers/input/misc/88pm88x-onkey.c | 95 ++++++++
drivers/input/misc/Kconfig | 7 +
drivers/input/misc/Makefile | 1 +
drivers/mfd/88pm88x.c | 211 ++++++++++++++++++
drivers/mfd/Kconfig | 12 +
drivers/mfd/Makefile | 1 +
drivers/regulator/88pm88x-regulator.c | 206 +++++++++++++++++
drivers/regulator/Kconfig | 6 +
drivers/regulator/Makefile | 1 +
include/linux/mfd/88pm88x.h | 46 ++++
14 files changed, 739 insertions(+)
create mode 100644 Documentation/devicetree/bindings/input/marvell,88pm88x-onkey.yaml
create mode 100644 Documentation/devicetree/bindings/mfd/marvell,88pm88x.yaml
create mode 100644 Documentation/devicetree/bindings/regulator/marvell,88pm88x-regulator.yaml
create mode 100644 drivers/input/misc/88pm88x-onkey.c
create mode 100644 drivers/mfd/88pm88x.c
create mode 100644 drivers/regulator/88pm88x-regulator.c
create mode 100644 include/linux/mfd/88pm88x.h
--
2.43.0
next reply other threads:[~2024-02-11 9:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-11 9:35 Karel Balej [this message]
2024-02-11 9:35 ` [RFC PATCH v2 1/6] dt-bindings: mfd: add entry for Marvell 88PM886 PMIC Karel Balej
2024-02-15 14:20 ` Rob Herring
2024-02-18 15:10 ` Karel Balej
2024-02-19 7:29 ` Krzysztof Kozlowski
2024-02-11 9:35 ` [RFC PATCH v2 2/6] mfd: add driver " Karel Balej
2024-02-11 9:35 ` [RFC PATCH v2 3/6] regulator: add regulators " Karel Balej
2024-02-11 9:35 ` [RFC PATCH v2 4/6] dt-bindings: input: add entry for Marvell 88PM88X PMICs onkey Karel Balej
2024-02-15 14:22 ` Rob Herring
2024-02-11 9:35 ` [RFC PATCH v2 5/6] input: add onkey driver for Marvell 88PM88X PMICs Karel Balej
2024-02-11 9:35 ` [RFC PATCH v2 6/6] MAINTAINERS: add myself for Marvell 88PM886 PMIC Karel Balej
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=20240211094609.2223-1-karelb@gimli.ms.mff.cuni.cz \
--to=karelb@gimli.ms.mff.cuni.cz \
--cc=balejk@matfyz.cz \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=duje.mihanovic@skole.hr \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).