Thanks for explaining,

On 17/04/18 15:54, Alban wrote:
This will not only allow reading the calibration data from nvmem, but
will also create a partition on the MTD device, which is not acceptable.
With my proposed binding this would become:

flash@0 {
        #address-cells = <1>;
        #size-cells = <1>;
        compatible = "s25sl064a";
        reg = <0>;

        nvmem-cells {
                compatible = "nvmem-cells";
                #address-cells = <1>;
                #address-cells = <1>;

                calibration: calib@404 {
                        reg = <0x404 0x10>;
                };
        };

Why can't we make nvmem-cells node a nvmem provider in this case?
Which should work!

--srini


};

Which would work fine as the MTD code will ignore the nvmem-cells
subnode thanks to its compatible string.

Reply via email to