From: Lee Jones <lee@kernel.org>
To: Charles Keepax <ckeepax@opensource.cirrus.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Peter Griffin <peter.griffin@linaro.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Russell King <linux@armlinux.org.uk>,
Mark Brown <broonie@kernel.org>,
Linus Walleij <linusw@kernel.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
mfd@lists.linux.dev, linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
patches@opensource.cirrus.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/4] mfd: wm831x: Support software nodes for DCDC regulators
Date: Thu, 5 Nov 2026 14:13:12 +0000 [thread overview]
Message-ID: <20261105141312.GL1650678@google.com> (raw)
In-Reply-To: <auyK50dqvwxIGIar@opensource.cirrus.com>
On Thu, 05 Nov 2026, Charles Keepax wrote:
> On Thu, Nov 05, 2026 at 02:43:17PM +0100, Arnd Bergmann wrote:
> > On Thu, Nov 5, 2026, at 09:53, Lee Jones wrote:
> > > On Wed, 04 Nov 2026, Dmitry Torokhov wrote:
> > >> On Wed, Nov 04, 2026 at 06:14:29PM +0000, Lee Jones wrote:
> > >> > On Sat, 24 Oct 2026, Dmitry Torokhov wrote:
> > - if there is a reason to expect any future user of the driver,
> > extend the wlf,arizona.yaml binding to cover wm831x as well,
> > replace all the platform data with swnode properties according
> > to that binding and have the drivers use those.
>
> I really don't like adding wm831x to the Arizona binding. Fine if
> we want to create a new binding in a similar style but Arizona is
> a binding for a specific series of audio parts, wm831x predates
> those and is a pmic. Trying to combine them feels likely to cause
> problems.
I don't personally mind how this gets resolved, as long as we avoid the
monstrosity suggested in the original submission. =:-]
--
Lee Jones
next prev parent reply other threads:[~2026-11-05 14:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-25 5:03 [PATCH v4 0/4] ARM: s3c: crag6410: Convert to software nodes and properties Dmitry Torokhov
2026-10-25 5:03 ` [PATCH v4 1/4] mfd: wm831x: Support software nodes for DCDC regulators Dmitry Torokhov
2026-10-26 10:15 ` Charles Keepax
2026-10-28 9:38 ` Bartosz Golaszewski
2026-11-04 18:14 ` Lee Jones
2026-11-05 1:15 ` Dmitry Torokhov
2026-11-05 8:53 ` Lee Jones
2026-11-05 13:43 ` Arnd Bergmann
2026-11-05 13:55 ` Charles Keepax
2026-11-05 14:13 ` Lee Jones [this message]
2026-10-25 5:03 ` [PATCH v4 2/4] ARM: s3c: crag6410: convert PMIC DVS GPIO to software properties Dmitry Torokhov
2026-10-28 9:38 ` Bartosz Golaszewski
2026-10-25 5:03 ` [PATCH v4 3/4] ARM: s3c: crag6410: convert basic-mmio-gpio and LEDs " Dmitry Torokhov
2026-10-25 5:03 ` [PATCH v4 4/4] ARM: s3c: crag6410: convert WM1250 and SPI0 GPIO lookup tables to property entries Dmitry Torokhov
2026-10-26 13:51 ` [PATCH v4 0/4] ARM: s3c: crag6410: Convert to software nodes and properties Arnd Bergmann
2026-10-27 1:07 ` Dmitry Torokhov
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=20261105141312.GL1650678@google.com \
--to=lee@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=arnd@arndb.de \
--cc=brgl@bgdev.pl \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=dmitry.torokhov@gmail.com \
--cc=krzk@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mfd@lists.linux.dev \
--cc=patches@opensource.cirrus.com \
--cc=peter.griffin@linaro.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