From mboxrd@z Thu Jan 1 00:00:00 1970 From: Srinivas Kandagatla Subject: Re: [PATCH v3 1/3] nvmem: Update the OF binding to use a subnode for the cells list Date: Tue, 17 Apr 2018 16:44:01 +0100 Message-ID: <8c4b48ad-e99e-030a-a4ee-b6df0fa59c79@linaro.org> References: <1521933899-362-1-git-send-email-albeu@free.fr> <1521933899-362-2-git-send-email-albeu@free.fr> <344e0087-7410-aebb-8a66-c6976064df10@linaro.org> <20180417165420.423a691b@avionic-0020> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20180417165420.423a691b@avionic-0020> Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org To: Alban Cc: linux-kernel@vger.kernel.org, Rob Herring , Mark Rutland , David Woodhouse , Brian Norris , Boris Brezillon , Marek Vasut , Richard Weinberger , Cyrille Pitchen , devicetree@vger.kernel.org, linux-mtd@lists.infradead.org List-Id: devicetree@vger.kernel.org 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.