From mboxrd@z Thu Jan 1 00:00:00 1970 From: Boris Brezillon Subject: Re: [PATCH 12/14] mtd: maps: Merge gpio-addr-flash.c into physmap-core.c Date: Sun, 14 Oct 2018 09:06:06 +0200 Message-ID: <20181014090606.12c9baac@bbrezillon> References: <20181008201027.17952-1-boris.brezillon@bootlin.com> <20181008201027.17952-13-boris.brezillon@bootlin.com> <20181009091106.7f25a314@bbrezillon> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20181009091106.7f25a314@bbrezillon> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-mtd" Errors-To: linux-mtd-bounces+gldm-linux-mtd-36=gmane.org@lists.infradead.org To: Ricardo Ribalda Delgado Cc: Mark Rutland , devicetree@vger.kernel.org, Pawel Moll , Ian Campbell , Richard Weinberger , Marek Vasut , Rob Herring , linux-mtd@lists.infradead.org, Kumar Gala , Brian Norris , David Woodhouse List-Id: devicetree@vger.kernel.org On Tue, 9 Oct 2018 09:11:06 +0200 Boris Brezillon wrote: > On Tue, 9 Oct 2018 09:04:51 +0200 > Ricardo Ribalda Delgado wrote: > > > Hi Boris > > > > Maybe we want to leave the pdata example. > > > > /** > > * The platform resource layout expected looks something like: > > * struct mtd_partition partitions[] = { ... }; > > * struct physmap_flash_data flash_data = > > ..... > > Sure, I'll add it back. Actually I changed my mind on that one. The physmap driver did not document that in the first place, so, if we want to add this example, we should do it in a separate patch, and maybe place it next to the physmap_flash_data struct definition. This being said, I don't see a lot of drivers documenting this sort of things and I doubt new platforms will use pdata to describe their device anyway. ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/