Re: [PATCH v4 1/4] mfd: wm831x: Support software nodes for DCDC regulators

[Dmitry Torokhov <dmitry.torokhov@gmail.com>]

On Thu, Nov 05, 2026 at 05:19:30PM +0000, Mark Brown wrote:
> On Thu, Nov 05, 2026 at 09:12:38AM -0800, Dmitry Torokhov wrote:
> > On Thu, Nov 05, 2026 at 02:43:17PM +0100, Arnd Bergmann wrote:
> 
> > > As far as I understand the situation, wm831x was used on the
> > > reference board (Samsung smdk6410, removed in 2019) in addition
> > > to crag6410 but never anywhere else upstream. The question
> > > then is whether we'll ever see a DT conversion of crag6410.
> > > This would require finding someone willing to actually do
> > > the work, and coming up with a way to handle the autodetection
> > > in mach-crag6410-module.c so the correct spi/i2c codec
> > > child devices are probed.
> 
> > So I guess the question then: do we need to keep this board at all? Or
> > it is time for it to go the way of the dodo? And then we could drop some
> > more drivers as well.
> 
> I don't really have a great replacement for it.
> 
> > My goal for the series was to move along legacy gpio API conversions, as
> > well as move away from the GPIO lookup tables (ideally I want them gone
> > now that we have software nodes supporting describing GPIOs).
> 
> It is a bit hard to get enthused about software nodes :/

Hopefully you do not need to pay too much attention to them as they are
hidden in the legacy board code.

The benefit is that using them makes the driver exercise the same code
paths as it would on DT system (unless you insist that the driver is
very special and should only use of_* API) and allows dropping support
for bespoke platform data (in most cases).

Thanks.

-- 
Dmitry