[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2e1495ab-2773-a3bb-0ad2-4af607cccc11@linaro.org>
Date: Sat, 9 Apr 2022 14:47:23 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Paul Cercueil <paul@...pouillou.net>
Cc: "H. Nikolaus Schaller" <hns@...delico.com>,
Rob Herring <robh+dt@...nel.org>,
Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
linux-mips@...r.kernel.org, letux-kernel@...nphoenux.org
Subject: Re: [PATCH 13/18] dt-bindings: fix jz4780-nemc issue as reported by
dtbscheck
On 09/04/2022 14:37, Paul Cercueil wrote:
>> The true question is whether you need simple-mfd. Isn't the binding
>> (and
>> the driver) expected to instantiate its children?
>
> I can explain that one. There is the EFUSE controller located inside
> the nemc's memory area, and the two are pretty much unrelated, hence
> the "simple-mfd" compatible string.
I saw the efuse children and that's why I asked who is expected to
populate them. You said that simple-mfd is required for this, I say no.
It should work without simple-mfd...
I am kind of repeating myself but I really do not see the need of
simple-mfd in the bindings.
Best regards,
Krzysztof
Powered by blists - more mailing lists