Re: [PATCH v2 2/2] hwmon: ltc4282: add support for the LTC4282 chip

From: Linus Walleij <linus.walleij@linaro.org>
To: "Nuno Sá" <noname.nuno@gmail.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
	Andy Shevchenko <andy@kernel.org>,
	nuno.sa@analog.com,  linux-hwmon@vger.kernel.org,
	devicetree@vger.kernel.org,  linux-doc@vger.kernel.org,
	Jean Delvare <jdelvare@suse.com>,
	 Rob Herring <robh+dt@kernel.org>,
	 Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	 Jonathan Corbet <corbet@lwn.net>,
	Bartosz Golaszewski <brgl@bgdev.pl>
Subject: Re: [PATCH v2 2/2] hwmon: ltc4282: add support for the LTC4282 chip
Date: Mon, 4 Dec 2023 00:08:51 +0100	[thread overview]
Message-ID: <CACRpkdYfe68aVNcnvfmLz8y3QOfsyA9vFHsaTL6Y9mZJ31wKRg@mail.gmail.com> (raw)
In-Reply-To: <ba123831d7956b0437158a6928ddafb4510ab62b.camel@gmail.com>

On Sat, Dec 2, 2023 at 10:42 AM Nuno Sá <noname.nuno@gmail.com> wrote:

 Hopefully, I'll get into the gpio stuff later on. From a brief look,
the auxiliary
> bus might feet and easier than mfd.

You can also just spawn a random platform_device from the HWMON driver
and let that probe a driver down in drivers/gpio/*.

static struct platform_device my_gpio_device = {
        .name = "my-gpio",
        .id = -1,
};

my_gpio_device.dev.platform_data = ... ;
my_gpio_device.dev.parent = dev;
return platform_device_register(&my_gpio_device);

You can then pass any accessors as platform data. This in a way is what
the MFD or aux buses do just more organized.

Yours
Linus Walleij