[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250702162620.GA10134@google.com>
Date: Wed, 2 Jul 2025 17:26:20 +0100
From: Lee Jones <lee@...nel.org>
To: Alex Elder <elder@...cstar.com>
Cc: lgirdwood@...il.com, broonie@...nel.org, alexandre.belloni@...tlin.com,
robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org,
mat.jonczyk@...pl, dlan@...too.org, paul.walmsley@...ive.com,
palmer@...belt.com, aou@...s.berkeley.edu, alex@...ti.fr,
troymitchell988@...il.com, guodong@...cstar.com,
linux-rtc@...r.kernel.org, devicetree@...r.kernel.org,
linux-riscv@...ts.infradead.org, spacemit@...ts.linux.dev,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v6 2/8] mfd: simple-mfd-i2c: specify max_register
On Wed, 02 Jul 2025, Alex Elder wrote:
> On 7/2/25 10:26 AM, Lee Jones wrote:
> > On Fri, 27 Jun 2025, Alex Elder wrote:
> >
> > > All devices supported by simple MFD use the same 8-bit register
> > > 8-bit value regmap configuration. There is an option available
> > > for a device to specify a custome configuration, but no existing
> > > device uses it.
> > >
> > > Lee Jones suggested modifying the simple MFD implementation to
> > > remove the generality of the full regmap configuration and add a
> > > max_register value to the simple_mfd_data structure. This can
> > > be used in the regmap configuration to limit the valid register
> > > addresses if desired. It's simpler, and covers all existing and
> > > anticipated device types.
> >
> > Woah, not like this. I wanted to make the framework _more_ flexible.
>
> OK, sorry I misunderstood. I'll send another new version today
> that does what you suggest.
No worries. Perhaps I wasn't clear enough.
--
Lee Jones [李琼斯]
Powered by blists - more mailing lists