[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <c3270109-406f-49bd-9c11-e323d1b6e84d@kernel.org>
Date: Wed, 18 Dec 2024 08:56:06 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Dzmitry Sankouski <dsankouski@...il.com>
Cc: Sebastian Reichel <sre@...nel.org>, Chanwoo Choi <cw00.choi@...sung.com>,
Lee Jones <lee@...nel.org>, Rob Herring <robh@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Dmitry Torokhov <dmitry.torokhov@...il.com>, Pavel Machek <pavel@....cz>,
Hans de Goede <hdegoede@...hat.com>,
Marek Szyprowski <m.szyprowski@...sung.com>,
Sebastian Krzyszkowiak <sebastian.krzyszkowiak@...i.sm>,
Purism Kernel Team <kernel@...i.sm>, linux-pm@...r.kernel.org,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
linux-input@...r.kernel.org, linux-leds@...r.kernel.org
Subject: Re: [PATCH v11 3/9] dt-bindings: power: supply: max17042: split on 2
files
On 11/12/2024 15:59, Dzmitry Sankouski wrote:
> Ah, indeed, the device tree in this and previous patches doesn't
> reflect hardware wiring.
>
> MAX77705 fuel gauge has a separate i2c address, i.e. I may move it out of the
> MAX77705 MFD node. However, the device on that address has additional features,
> like measuring system and input current, which is out of fuel gauge
> responsibility.
This is fuel gauge job.
>
> So I guess I should create another MFD for fuel gauge, i. e. max77705 example
> would look like:
>
> ...
> pmic@66 {
> compatible = "maxim,max77705";
> ...
> };
>
> meter@36 {
> compatible = "maxim,max77705-meter";
>
No resources here, so not a MFD. This is one device.
Best regards,
Krzysztof
Powered by blists - more mailing lists