On 24/03/18 23:24, Alban Bedel wrote:
Having the cells as subnodes of the provider device without any
compatible property might clash with other bindings. To avoid this
problem update the binding to have all the cells in a 'nvmem-cells'
subnode with a 'nvmem-cells' compatible string. This new binding
guarantee that we can turn any kind of device in a nvmem provider.
While discouraged for new uses the old scheme is still supported for
backward compatibility.
Am not sure if this a really good idea to change nvmem bindings based on
provider requirements. This can be a beginning of other problems!!
Did you know that we can pass nvmem cells info via nvmem config ?
Why can't mtd-nvmem provider populate the nvmem_config->cells from its
dt "nvmem-cells" subnode before it registers the provider?
Doing this way will make the binding very much specific to the provider
rather than changing nvmem core bindings.
thanks,
srini
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
