[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b8b72bde-31f3-4148-bd01-49826f9f9bd7@uclouvain.be>
Date: Mon, 2 Dec 2024 16:03:49 +0100
From: Thomas Antoine <t.antoine@...ouvain.be>
To: Krzysztof Kozlowski <krzk@...nel.org>, Sebastian Reichel
<sre@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
<conor+dt@...nel.org>, Dimitri Fedrau <dima.fedrau@...il.com>,
Catalin Marinas <catalin.marinas@....com>, Will Deacon <will@...nel.org>,
Peter Griffin <peter.griffin@...aro.org>,
Alim Akhtar <alim.akhtar@...sung.com>
Cc: linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-samsung-soc@...r.kernel.org
Subject: Re: [PATCH 4/4] arm64: dts: exynos: gs101-oriole: enable Maxim
max77759 fuel gauge
On 12/2/24 14:41, Krzysztof Kozlowski wrote:
> On 02/12/2024 14:07, Thomas Antoine via B4 Relay wrote:
>> From: Thomas Antoine <t.antoine@...ouvain.be>
>> &hsi2c_12 {
>> status = "okay";
>> /* TODO: add the devices once drivers exist */
>
>
> Is this still applicable?
Yes, there are other devices on the bus (the Maxim max77759 pmic, charger
and TPCI, the Maxim max20339 OVP and the NXP PCA9468).
>> +
>> + fuel-gauge@36 {
>> + compatible = "maxim,max77759-fg";
>> + reg = <0x36>;
>> + reg-names = "m5";
>
>
> No interrupts?
There are interrupts in the stock devicetree but they didn't compile out
of the box when adding them to the node without any other modification and
I didn't try further given the device worked without them. I can try to
get them to work for v2.
>> + };
>> +
>
>
> Do not add stray blank lines.
Will remove in v2.
Best regards,
Thomas Antoine
Powered by blists - more mailing lists