From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andy Gross Subject: Re: [PATCH v2 1/5] mtd: nand: Create a BBT flag to access bad block markers in raw mode Date: Fri, 24 Jul 2015 14:01:06 -0500 Message-ID: <20150724190106.GD24646@qualcomm.com> References: <1421419702-17812-1-git-send-email-architt@codeaurora.org> <1437474886-6209-1-git-send-email-architt@codeaurora.org> <1437474886-6209-2-git-send-email-architt@codeaurora.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <1437474886-6209-2-git-send-email-architt@codeaurora.org> Sender: linux-kernel-owner@vger.kernel.org To: Archit Taneja Cc: linux-mtd@lists.infradead.org, dehrenberg@google.com, cernekee@gmail.com, computersforpeace@gmail.com, linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org List-Id: linux-arm-msm@vger.kernel.org On Tue, Jul 21, 2015 at 04:04:42PM +0530, Archit Taneja wrote: > Some controllers can access the factory bad block marker from OOB only > when they read it in raw mode. When ECC is enabled, these controllers > discard reading/writing bad block markers, preventing access to them > altogether. > > The bbt driver assumes MTD_OPS_PLACE_OOB when scanning for bad blocks. > This results in the nand driver's ecc->read_oob() op to be called, which > works with ECC enabled. > > Create a new BBT option flag that tells nand_bbt to force the mode to > MTD_OPS_RAW. This would result in the correct op being called for the > underlying nand controller driver. > > Signed-off-by: Archit Taneja > --- Reviewed-by: Andy Gross -- Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project