[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2c491166-d8ae-4fb6-a4f7-74e823e1205d@kernel.org>
Date: Thu, 26 Jun 2025 21:49:25 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: André Draszik <andre.draszik@...aro.org>,
Catalin Marinas <catalin.marinas@....com>, Will Deacon <will@...nel.org>,
Peter Griffin <peter.griffin@...aro.org>,
Tudor Ambarus <tudor.ambarus@...aro.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
<conor+dt@...nel.org>, Alim Akhtar <alim.akhtar@...sung.com>
Cc: Will McVicker <willmcvicker@...gle.com>, kernel-team@...roid.com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-samsung-soc@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH v2 2/4] arm64: dts: exynos: gs101-pixel-common: add Maxim
MAX77759 PMIC
On 24/05/2025 07:21, André Draszik wrote:
> +
> + gpio {
> + compatible = "maxim,max77759-gpio";
> +
> + gpio-controller;
> + #gpio-cells = <2>;
> + /*
> + * "Human-readable name [SIGNAL_LABEL]" where the
> + * latter comes from the schematic
> + */
> + gpio-line-names = "OTG boost [OTG_BOOST_EN]",
> + "max20339 IRQ [MW_OVP_INT_L]";
> +
> + interrupt-controller;
> + #interrupt-cells = <2>;
> + };
> +
> + nvmem-0 {
Why is this called nvmem-0, not nvmem? Is there nvmem-1? I see binding
does it, but why?
Best regards,
Krzysztof
Powered by blists - more mailing lists