From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.bootlin.com ([62.4.15.54]) by bombadil.infradead.org with esmtp (Exim 4.90_1 #2 (Red Hat Linux)) id 1f9yC2-0001sO-O3 for linux-mtd@lists.infradead.org; Sat, 21 Apr 2018 19:29:08 +0000 Date: Sat, 21 Apr 2018 21:28:53 +0200 From: Boris Brezillon To: Miquel Raynal Cc: Richard Weinberger , David Woodhouse , Brian Norris , Marek Vasut , linux-mtd@lists.infradead.org Subject: Re: [PATCH 0/2] Uniform way to pass a NAND ID table to the core Message-ID: <20180421212853.34bf15b9@bbrezillon> In-Reply-To: <20180421201900.6c6e4a33@xps13> References: <20180321131235.9822-1-miquel.raynal@bootlin.com> <20180327091737.7d09b189@bbrezillon> <20180421201900.6c6e4a33@xps13> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Sat, 21 Apr 2018 20:19:00 +0200 Miquel Raynal wrote: > Hi Boris, > > On Tue, 27 Mar 2018 09:17:37 +0200, Boris Brezillon > wrote: > > > Hi Miquel, > > > > On Wed, 21 Mar 2018 14:12:33 +0100 > > Miquel Raynal wrote: > > > > > Hello, > > > > > > As part of the work of migrating all the drivers to nand_scan(), and > > > because nand_scan() does not provide a way to pass any ID table, create > > > a field in NAND chip so a controller driver can expose its ID table to > > > the core through it and stop using the last parameter of > > > nand_scan_ident() for that. > > > > I'm not a big fan of adding yet another field to the nand_chip struct. > > Could we instead create a nand_scan_with_ids() function that takes an > > extra ID table in argument and then make nand_scan() a wrapper around > > this new function? > > > > int nand_scan_with_ids(struct mtd_info *mtd, int max_chips, > > struct nand_flash_dev *ids); > > > > static inline int nand_scan(struct mtd_info *mtd, int max_chips) > > { > > return nand_scan_with_ids(mtd, max_chips, NULL); > > } > > Sure I can do that, but I found too impacting the fact that we should > patch all the drivers to call nand_scan_with_ids() from your example. Nope we don't have to do that, see the nand_scan() wrapper proposed above. > > I added another exported function called nand_scan_with_ids() but > nand_scan() is still visible so that I only have to patch one driver. > > You'll tell me what you think. That's exactly what I suggested, so I think we're good ;-).