From: Svyatoslav Ryhel <clamor95@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Lee Jones <lee@kernel.org>,
Pavel Machek <pavel@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Svyatoslav Ryhel <clamor95@gmail.com>,
David Lechner <dlechner@baylibre.com>,
Tony Lindgren <tony@atomide.com>
Cc: linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org
Subject: [PATCH v3 0/9] mfd: cpcap: convert documentation to schema and add Mot board support
Date: Mon, 23 Feb 2026 08:38:49 +0200 [thread overview]
Message-ID: <20260223063858.12208-1-clamor95@gmail.com> (raw)
The initial goal was only to add support for the CPCAP used in the Mot
Tegra20 board; however, since the documentation was already partially
converted, I decided to complete the conversion to schema too.
The CPCAP regulator, leds, rtc, pwrbutton and core files were converted
from TXT to YAML while preserving the original structure. Mot board
compatibility was added to the regulator and core schema. Since these
were one-line patches, they were not separated into dedicated commits;
however, the commit message notes this for both cases.
Finally, the CPCAP MFD was slightly refactored to improve support for
multiple subcell compositions.
---
Changes in v2:
- fixed code style
- rtc conversion was picked, so patch dropped
- added audio ports description into mfd schema
- splitted schema conversion and compatible addition
- minor style improvements and typo fixes
Changes in v3:
- added regulator node names list into pattern
- filled spi_device_id with driver data
- ADC patches were picked, so changes dropped
---
Svyatoslav Ryhel (9):
dt-bindings: regulator: cpcap-regulator: convert to DT schema
dt-bindings: regulator: cpcap-regulator: document Mot regulator
regulator: cpcap-regulator: add support for Mot regulators
dt-bindings: leds: leds-cpcap: convert to DT schema
dt-bindings: input: cpcap-pwrbutton: convert to DT schema
dt-bindings: mfd: motorola-cpcap: convert to DT schema
dt-bindings: mfd: motorola-cpcap: document Mapphone and Mot CPCAP
mfd: motorola-cpcap: diverge configuration per-board
mfd: motorola-cpcap: add support for Mot CPCAP composition
.../bindings/input/cpcap-pwrbutton.txt | 20 -
.../input/motorola,cpcap-pwrbutton.yaml | 32 ++
.../devicetree/bindings/leds/leds-cpcap.txt | 29 --
.../bindings/leds/motorola,cpcap-leds.yaml | 42 ++
.../bindings/mfd/motorola,cpcap.yaml | 416 ++++++++++++++++++
.../bindings/mfd/motorola-cpcap.txt | 78 ----
.../bindings/regulator/cpcap-regulator.txt | 35 --
.../regulator/motorola,cpcap-regulator.yaml | 47 ++
drivers/mfd/motorola-cpcap.c | 151 ++++++-
drivers/regulator/cpcap-regulator.c | 105 +++++
10 files changed, 775 insertions(+), 180 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/input/cpcap-pwrbutton.txt
create mode 100644 Documentation/devicetree/bindings/input/motorola,cpcap-pwrbutton.yaml
delete mode 100644 Documentation/devicetree/bindings/leds/leds-cpcap.txt
create mode 100644 Documentation/devicetree/bindings/leds/motorola,cpcap-leds.yaml
create mode 100644 Documentation/devicetree/bindings/mfd/motorola,cpcap.yaml
delete mode 100644 Documentation/devicetree/bindings/mfd/motorola-cpcap.txt
delete mode 100644 Documentation/devicetree/bindings/regulator/cpcap-regulator.txt
create mode 100644 Documentation/devicetree/bindings/regulator/motorola,cpcap-regulator.yaml
--
2.51.0
next reply other threads:[~2026-02-23 6:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 6:38 Svyatoslav Ryhel [this message]
2026-02-23 6:38 ` [PATCH v3 1/9] dt-bindings: regulator: cpcap-regulator: convert to DT schema Svyatoslav Ryhel
2026-02-23 9:54 ` Rob Herring (Arm)
2026-02-23 15:50 ` Rob Herring (Arm)
2026-02-26 18:55 ` Mark Brown
2026-02-23 6:38 ` [PATCH v3 2/9] dt-bindings: regulator: cpcap-regulator: document Mot regulator Svyatoslav Ryhel
2026-02-23 6:38 ` [PATCH v3 3/9] regulator: cpcap-regulator: add support for Mot regulators Svyatoslav Ryhel
2026-02-23 6:38 ` [PATCH v3 4/9] dt-bindings: leds: leds-cpcap: convert to DT schema Svyatoslav Ryhel
2026-02-23 9:54 ` Rob Herring (Arm)
2026-02-23 6:38 ` [PATCH v3 5/9] dt-bindings: input: cpcap-pwrbutton: " Svyatoslav Ryhel
2026-02-23 9:54 ` Rob Herring (Arm)
2026-02-23 16:46 ` Rob Herring (Arm)
2026-02-23 22:02 ` Dmitry Torokhov
2026-02-23 6:38 ` [PATCH v3 6/9] dt-bindings: mfd: motorola-cpcap: " Svyatoslav Ryhel
2026-03-05 23:57 ` Rob Herring (Arm)
2026-02-23 6:38 ` [PATCH v3 7/9] dt-bindings: mfd: motorola-cpcap: document Mapphone and Mot CPCAP Svyatoslav Ryhel
2026-03-05 23:58 ` Rob Herring (Arm)
2026-02-23 6:38 ` [PATCH v3 8/9] mfd: motorola-cpcap: diverge configuration per-board Svyatoslav Ryhel
2026-02-23 6:38 ` [PATCH v3 9/9] mfd: motorola-cpcap: add support for Mot CPCAP composition Svyatoslav Ryhel
2026-02-26 22:13 ` (subset) [PATCH v3 0/9] mfd: cpcap: convert documentation to schema and add Mot board support Mark Brown
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=20260223063858.12208-1-clamor95@gmail.com \
--to=clamor95@gmail.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=dmitry.torokhov@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@kernel.org \
--cc=robh@kernel.org \
--cc=tony@atomide.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