Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Maksim Kiselev <bigunclemax@gmail.com>
To:     olof@lixom.net
Cc:     ansuelsmth@gmail.com, devicetree@vger.kernel.org,
        gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
        rafael@kernel.org, saravanak@google.com, zajec5@gmail.com,
        fido_max@inbox.ru, =bigunclemax@gmail.com
Subject: Re: fw_devlink=on breaks probing devices when of_platform_populate() is used
Date:   Sun, 11 Dec 2022 11:46:31 +0300
Message-Id: <20221211084631.3942082-1-bigunclemax@gmail.com>
In-Reply-To: <Yyj7wJlqJkCwObRn@lx2k>
References: <Yyj7wJlqJkCwObRn@lx2k>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk


Hi, I have the same problem.
https://lore.kernel.org/all/CALHCpMgEZjnR39upkR6iozSk-b5A_GHRo9rcDSPXzzQi6x_qCw@mail.gmail.com/

I think the root of the problem was the choice of 'compatible'
device tree property to marking mtd partition node as a nvmem provider. 

This property used only inside 'mtd_nvmem_add' function to setup 
'no_of_node' flag.

> config.no_of_node = !of_device_is_compatible(node, "nvmem-cells");

This is how this flag processed by 'nvmem_register' function.

>	if (config->of_node)
>		nvmem->dev.of_node = config->of_node;
>	else if (!config->no_of_node)
>		nvmem->dev.of_node = config->dev->of_node;

Thats all, there is no such driver which compatible with 'nvmem-cells'.


So, maybe we should change the 'compatible' property to something else?