[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CACRpkdaiG+Gr+asDHsztR3A=iNNCUsCFXfrW2ZUidWYLn9RcVA@mail.gmail.com>
Date: Mon, 5 Aug 2024 09:48:44 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Frank Li <Frank.Li@....com>
Cc: Lee Jones <lee@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>,
Bartosz Golaszewski <brgl@...ev.pl>, Uwe Kleine-König <ukleinek@...nel.org>,
Shawn Guo <shawnguo@...nel.org>, Sascha Hauer <s.hauer@...gutronix.de>,
Pengutronix Kernel Team <kernel@...gutronix.de>, Fabio Estevam <festevam@...il.com>, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-gpio@...r.kernel.org,
linux-pwm@...r.kernel.org, imx@...ts.linux.dev,
linux-arm-kernel@...ts.infradead.org, Haibo Chen <haibo.chen@....com>,
Jun Li <jun.li@....com>
Subject: Re: [PATCH 2/6] mfd: adp5585: add ADI adp5585 core support
Hi Frank,
thanks for your patch!
On Tue, Jul 16, 2024 at 9:29 PM Frank Li <Frank.Li@....com> wrote:
> +struct adp5585_dev {
> + struct device *dev;
> + struct i2c_client *i2c_client;
> +
> + int (*read_reg)(struct adp5585_dev *adp5585, u8 reg, u8 *val);
> + int (*write_reg)(struct adp5585_dev *adp5585, u8 reg, u8 val);
> +};
The read_reg() and write_reg() accessors looks like a reimplementation
of regmap.
Can you check if you can just let the subdrivers access a regmap
for the parent MFD device and use that to read/write registers?
There are many examples of this in recent MFD drivers.
Yours,
Linus Walleij
Powered by blists - more mailing lists