Devicetree
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Svyatoslav Ryhel <clamor95@gmail.com>
Cc: linux-input@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org,
	Conor Dooley <conor+dt@kernel.org>,
	Pavel Machek <pavel@kernel.org>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>
Subject: Re: [PATCH v7 0/6] mfd: cpcap: convert documentation to schema and add Mot board support
Date: Thu, 27 Aug 2026 15:14:57 +0100	[thread overview]
Message-ID: <20260827141457.GA2943942@google.com> (raw)
In-Reply-To: <CAPVz0n3u0D=0swsO4n6LROFurO=as1w-ZRwaje08BN9dY=JhXQ@mail.gmail.com>

On Wed, 19 Aug 2026, Svyatoslav Ryhel wrote:

> вт, 21 лип. 2026 р. о 12:57 Svyatoslav Ryhel <clamor95@gmail.com> пише:
> >
> > 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
> >
> > Changes in v4:
> > - dropped regulator patches (applied)
> >
> > Changes in v5:
> > - switched to MFD_CELL_* macros
> > - switched to use determinator of model
> > - switched to spi_get_device_match_data
> >
> > Changes in v6:
> > - removed address-cells and size-cells from main node
> > - changed macros formatting and OF matches
> > - factored out common devices and made device addition staged
> > - dropped cpcap->variant check for 0
> > - EINVAL > ENODEV in variant checking switch
> >
> > Changes in v7:
> > - adjusted spi_device_id entries (name/driver_data)
> > ---
> >
> > Svyatoslav Ryhel (6):
> >   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          | 408 ++++++++++++++++++
> >  .../bindings/mfd/motorola-cpcap.txt           |  78 ----
> >  drivers/mfd/motorola-cpcap.c                  | 143 +++---
> >  include/linux/mfd/motorola-cpcap.h            |   7 +
> >  8 files changed, 571 insertions(+), 188 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
> >
> > --
> > 2.53.0
> >
> 
> Hello Lee! May you please pick this patch set? I have included changes
> asked by Rob and Uwe. Thank you!

Nope! =:-)

There are still a bunch of unanswered Sashiko reviews and one from Rob's bot.

-- 
Lee Jones

  reply	other threads:[~2026-08-27 14:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21  9:56 [PATCH v7 0/6] mfd: cpcap: convert documentation to schema and add Mot board support Svyatoslav Ryhel
2026-07-21  9:56 ` [PATCH v7 1/6] dt-bindings: leds: leds-cpcap: convert to DT schema Svyatoslav Ryhel
2026-07-21 10:06   ` sashiko-bot
2026-07-21 12:01   ` Rob Herring (Arm)
2026-07-21  9:56 ` [PATCH v7 2/6] dt-bindings: input: cpcap-pwrbutton: " Svyatoslav Ryhel
2026-07-21 10:08   ` sashiko-bot
2026-07-21  9:56 ` [PATCH v7 3/6] dt-bindings: mfd: motorola-cpcap: " Svyatoslav Ryhel
2026-07-21 10:15   ` sashiko-bot
2026-07-21  9:56 ` [PATCH v7 4/6] dt-bindings: mfd: motorola-cpcap: document Mapphone and Mot CPCAP Svyatoslav Ryhel
2026-07-21 10:16   ` sashiko-bot
2026-07-21  9:56 ` [PATCH v7 5/6] mfd: motorola-cpcap: diverge configuration per-board Svyatoslav Ryhel
2026-07-21 10:23   ` sashiko-bot
2026-07-21  9:56 ` [PATCH v7 6/6] mfd: motorola-cpcap: add support for Mot CPCAP composition Svyatoslav Ryhel
2026-07-21 10:20   ` sashiko-bot
2026-08-19  9:12 ` [PATCH v7 0/6] mfd: cpcap: convert documentation to schema and add Mot board support Svyatoslav Ryhel
2026-08-27 14:14   ` Lee Jones [this message]
2026-08-27 17:17     ` Svyatoslav Ryhel

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=20260827141457.GA2943942@google.com \
    --to=lee@kernel.org \
    --cc=clamor95@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=krzk+dt@kernel.org \
    --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 \
    /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