From: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>
To: Svyatoslav Ryhel <clamor95@gmail.com>,
Linus Walleij <linusw@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Lee Jones <lee@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Daniel Lezcano <daniel.lezcano@kernel.org>,
Zhang Rui <rui.zhang@intel.com>,
Lukasz Luba <lukasz.luba@arm.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
linux-rtc@vger.kernel.org
Subject: Re: [PATCH v4 3/5] dt-bindings: mfd: max77620: convert to DT schema
Date: Mon, 16 Mar 2026 16:03:36 +0100 [thread overview]
Message-ID: <e3b1fedd-79a3-41be-a94e-a08ad0c85b66@oss.qualcomm.com> (raw)
In-Reply-To: <20260312085258.11431-4-clamor95@gmail.com>
On 3/12/26 09:52, Svyatoslav Ryhel wrote:
> Convert max77620 devicetree bindings from TXT to YAML format. This patch
> does not change any functionality; the bindings remain the same. The
> thermal bindings are incorporated into the binding. GPIO controller
> function in MAX77620 has no dedicated node and is folded into the parent
> node itself.
>
> Signed-off-by: Svyatoslav Ryhel <clamor95@gmail.com>
> ---
For the thermal part:
Acked-by: Daniel Lezcano <daniel.lezcano@kernel.org>
next prev parent reply other threads:[~2026-03-16 15:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 8:52 [PATCH v4 0/5] rtc: max77686: convert to i2c_new_ancillary_device Svyatoslav Ryhel
2026-03-12 8:52 ` [PATCH v4 1/5] regulator: dt-bindings: regulator-max77620: convert to DT schema Svyatoslav Ryhel
2026-03-12 15:18 ` Rob Herring (Arm)
2026-03-12 8:52 ` [PATCH v4 2/5] dt-bindings: pinctrl: pinctrl-max77620: " Svyatoslav Ryhel
2026-03-12 15:20 ` Rob Herring
2026-03-12 15:33 ` Svyatoslav Ryhel
2026-03-12 15:39 ` Rob Herring
2026-03-12 16:26 ` Svyatoslav Ryhel
2026-03-12 8:52 ` [PATCH v4 3/5] dt-bindings: mfd: max77620: " Svyatoslav Ryhel
2026-03-12 15:22 ` Rob Herring (Arm)
2026-03-16 15:03 ` Daniel Lezcano [this message]
2026-03-19 18:23 ` (subset) " Lee Jones
2026-03-12 8:52 ` [PATCH v4 4/5] dt-bindings: mfd: max77620: document optional RTC address for MAX77663 Svyatoslav Ryhel
2026-03-12 15:31 ` Rob Herring (Arm)
2026-03-19 18:26 ` (subset) " Lee Jones
2026-03-12 8:52 ` [PATCH v4 5/5] rtc: max77686: convert to i2c_new_ancillary_device Svyatoslav Ryhel
2026-03-12 16:56 ` (subset) [PATCH v4 0/5] " Alexandre Belloni
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=e3b1fedd-79a3-41be-a94e-a08ad0c85b66@oss.qualcomm.com \
--to=daniel.lezcano@oss.qualcomm.com \
--cc=alexandre.belloni@bootlin.com \
--cc=brgl@kernel.org \
--cc=broonie@kernel.org \
--cc=clamor95@gmail.com \
--cc=conor+dt@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=daniel.lezcano@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=rui.zhang@intel.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
all inboxes | Powered by JetHome®