From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-out.m-online.net ([212.18.0.10]) by merlin.infradead.org with esmtps (Exim 4.76 #1 (Red Hat Linux)) id 1SpjQ4-0003xT-QU for linux-mtd@lists.infradead.org; Fri, 13 Jul 2012 17:12:45 +0000 From: Marek Vasut To: Brian Norris Subject: Re: [PATCH] mtd: nand: allow NAND_NO_SUBPAGE_WRITE to be set from driver Date: Fri, 13 Jul 2012 19:12:42 +0200 References: <1342196904-13850-1-git-send-email-computersforpeace@gmail.com> In-Reply-To: <1342196904-13850-1-git-send-email-computersforpeace@gmail.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <201207131912.42495.marex@denx.de> Cc: Scott Wood , David Woodhouse , linux-mtd@lists.infradead.org, Huang Shijie , Artem Bityutskiy List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Dear Brian Norris, > The NAND_CHIPOPTIONS_MSK has limited utility and is causing real bugs. It > silently masks off at least one flag that might be set by the driver > (NAND_NO_SUBPAGE_WRITE). This breaks the GPMI NAND driver and possibly > others. > > Really, as long as driver writers exercise a small amount of care with > NAND_* options, this mask is not necessary at all; it was only here to > prevent certain options from accidentally being set by the driver. But the > original thought turns out to be a bad idea occasionally. Thus, kill it. > > Signed-off-by: Brian Norris > Cc: Huang Shijie > Cc: Marek Vasut [...] Maybe we should simply split it into two sets of flags to make it clear -- chip ones and controller ones ? Best regards, Marek Vasut