From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on archive.lwn.net X-Spam-Level: X-Spam-Status: No, score=-6.0 required=5.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI autolearn=unavailable autolearn_force=no version=3.4.1 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by archive.lwn.net (Postfix) with ESMTP id 677DC7D2EE for ; Tue, 21 Aug 2018 05:07:39 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726390AbeHUI0L (ORCPT ); Tue, 21 Aug 2018 04:26:11 -0400 Received: from mail.bootlin.com ([62.4.15.54]:57725 "EHLO mail.bootlin.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726346AbeHUI0L (ORCPT ); Tue, 21 Aug 2018 04:26:11 -0400 Received: by mail.bootlin.com (Postfix, from userid 110) id 0E35D20717; Tue, 21 Aug 2018 07:07:35 +0200 (CEST) Received: from bbrezillon (91-160-177-164.subs.proxad.net [91.160.177.164]) by mail.bootlin.com (Postfix) with ESMTPSA id 4190720703; Tue, 21 Aug 2018 07:07:34 +0200 (CEST) Date: Tue, 21 Aug 2018 07:07:34 +0200 From: Boris Brezillon To: Alban , Srinivas Kandagatla , Rob Herring Cc: Bartosz Golaszewski , Jonathan Corbet , Sekhar Nori , Kevin Hilman , Russell King , Arnd Bergmann , Greg Kroah-Hartman , David Woodhouse , Brian Norris , Marek Vasut , Richard Weinberger , Grygorii Strashko , "David S . Miller" , Naren , Mauro Carvalho Chehab , Andrew Morton , Lukas Wunner , Dan Carpenter , Florian Fainelli , Ivan Khoronzhuk , Sven Van Asbroeck , Paolo Abeni , David Lechner , Andrew Lunn , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-i2c@vger.kernel.org, linux-mtd@lists.infradead.org, linux-omap@vger.kernel.org, netdev@vger.kernel.org, Bartosz Golaszewski Subject: Re: [PATCH v2 06/29] mtd: Add support for reading MTD devices via the nvmem API Message-ID: <20180821070734.6dd1734d@bbrezillon> In-Reply-To: <20180820232748.608c3667@tock> References: <20180810080526.27207-1-brgl@bgdev.pl> <20180810080526.27207-7-brgl@bgdev.pl> <20180817182720.6a6e5e8e@bbrezillon> <20180819133106.0420df5f@tock> <20180819184609.6dcdbb9a@bbrezillon> <5b8c30b8-41e1-d59e-542b-fef6c6469ff0@linaro.org> <20180820202038.5d3dc195@bbrezillon> <20180820232748.608c3667@tock> X-Mailer: Claws Mail 3.15.0-dirty (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-doc-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-doc@vger.kernel.org On Mon, 20 Aug 2018 23:27:48 +0200 Alban wrote: > On Mon, 20 Aug 2018 20:20:38 +0200 > Boris Brezillon wrote: > > > On Mon, 20 Aug 2018 11:43:34 +0100 > > Srinivas Kandagatla wrote: > > > > > > > > Overall am still not able to clear visualize on how MTD bindings with > > > nvmem cells would look in both partition and un-partition usecases? > > > An example DT would be nice here!! > > > > Something along those lines: > > We must also have a compatible string on the nvmem-cells node to make > sure we don't clash with the old style MTD partitions, That's not possible, because we don't have a reg prop in the nvmem-cells node. > or some other > device specific binding. This one might happen. Was Rob okay with this compatible? If he was, I guess we can go for this binding. Srinivas, any objection? > > > > > mtdnode { > > nvmem-cells { > compatible = "nvmem-cells"; > > #address-cells = <1>; > > #size-cells = <1>; > > > > cell@0 { > > reg = <0x0 0x14>; > > }; > > }; > > > > partitions { > > compatible = "fixed-partitions"; > > #address-cells = <1>; > > #size-cells = <1>; > > > > partition@0 { > > reg = <0x0 0x20000>; > > > > nvmem-cells { > compatible = "nvmem-cells"; > > #address-cells = <1>; > > #size-cells = <1>; > > > > cell@0 { > > reg = <0x0 0x10>; > > }; > > }; > > }; > > }; > > }; > > > Alban