From: Michael Walle <mwalle@kernel.org>
To: Lee Jones <lee@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linus Walleij <linus.walleij@linaro.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Julien Panis <jpanis@baylibre.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-gpio@vger.kernel.org
Subject: Re: [PATCH v2 1/7] mfd: tps6594: Add TI TPS652G1 support
Date: Thu, 10 Jul 2025 11:06:11 +0200 [thread overview]
Message-ID: <baa1eccc55fd406b3c42f6a5466b6be5@kernel.org> (raw)
In-Reply-To: <20250710090025.GD10134@google.com>
Hi Lee,
>> @@ -82,6 +87,7 @@ static const struct of_device_id
>> tps6594_spi_of_match_table[] = {
>> { .compatible = "ti,tps6593-q1", .data = (void *)TPS6593, },
>> { .compatible = "ti,lp8764-q1", .data = (void *)LP8764, },
>> { .compatible = "ti,tps65224-q1", .data = (void *)TPS65224, },
>> + { .compatible = "ti,tps652g1", .data = (void *)TPS652G1, },
>
> I get warnings about this being undocumented.
>
> Should it be added to:
>
> Documentation/devicetree/bindings/mfd/ti,tps6594.yaml
I've accidentally forgot the DT patch in v2 of this series. This series
was
superseeded by v3 which has the DT patch again.
https://lore.kernel.org/all/20250703113153.2447110-1-mwalle@kernel.org/
-michael
next prev parent reply other threads:[~2025-07-10 9:06 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 11:45 [PATCH v2 0/7] mfd: tps6594: Add TI TPS652G1 support Michael Walle
2025-06-13 11:45 ` [PATCH v2 1/7] " Michael Walle
2025-06-19 13:35 ` Lee Jones
2025-07-10 9:00 ` Lee Jones
2025-07-10 9:06 ` Michael Walle [this message]
2025-07-10 9:47 ` Lee Jones
2025-06-13 11:45 ` [PATCH v2 2/7] misc: tps6594-pfsm: Add TI TPS652G1 PMIC PFSM Michael Walle
2025-06-30 7:48 ` Arnd Bergmann
2025-06-13 11:45 ` [PATCH v2 3/7] pinctrl: pinctrl-tps6594: Add TPS652G1 PMIC pinctrl and GPIO Michael Walle
2025-06-18 11:52 ` Linus Walleij
2025-06-13 11:45 ` [PATCH v2 4/7] regulator: tps6594-regulator: remove interrupt_count Michael Walle
2025-06-13 12:06 ` Mark Brown
2025-06-13 11:45 ` [PATCH v2 5/7] regulator: tps6594-regulator: remove hardcoded buck config Michael Walle
2025-06-13 12:06 ` Mark Brown
2025-06-13 11:45 ` [PATCH v2 6/7] regulator: tps6594-regulator: refactor variant descriptions Michael Walle
2025-06-13 12:07 ` Mark Brown
2025-06-13 11:45 ` [PATCH v2 7/7] regulator: tps6594-regulator: Add TI TPS652G1 PMIC regulators Michael Walle
2025-06-13 12:07 ` Mark Brown
2025-07-02 15:30 ` [PATCH v2 0/7] mfd: tps6594: Add TI TPS652G1 support Lee Jones
2025-07-10 8:58 ` (subset) " Lee Jones
2025-07-10 9:49 ` [GIT PULL] Immutable branch between MFD, Misc and Pinctrl due for the v6.17 merge window Lee Jones
2025-07-10 9:57 ` Mark Brown
2025-07-10 10:46 ` Michael Walle
2025-07-10 11:04 ` Mark Brown
2025-07-18 7:13 ` Lee Jones
2025-07-18 13:27 ` Mark Brown
2025-07-18 13:38 ` Lee Jones
2025-07-18 14:33 ` Mark Brown
2025-07-11 17:37 ` Linus Walleij
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=baa1eccc55fd406b3c42f6a5466b6be5@kernel.org \
--to=mwalle@kernel.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jpanis@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).