[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180526104900.139dd19b@xps13>
Date: Sat, 26 May 2018 10:58:38 +0200
From: Miquel Raynal <miquel.raynal@...tlin.com>
To: Abhishek Sahu <absahu@...eaurora.org>
Cc: Boris Brezillon <boris.brezillon@...tlin.com>,
David Woodhouse <dwmw2@...radead.org>,
Brian Norris <computersforpeace@...il.com>,
Marek Vasut <marek.vasut@...il.com>,
Richard Weinberger <richard@....at>,
Cyrille Pitchen <cyrille.pitchen@...ev4u.fr>,
linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mtd@...ts.infradead.org, Andy Gross <andy.gross@...aro.org>,
Archit Taneja <architt@...eaurora.org>
Subject: Re: [PATCH v3 13/16] mtd: rawnand: qcom: minor code reorganization
for bad block check
Hi Abhishek,
> @@ -2141,12 +2127,10 @@ static int qcom_nandc_block_bad(struct mtd_info *mtd, loff_t ofs)
> goto err;
> }
>
> - bbpos = mtd->writesize - host->cw_size * (ecc->steps - 1);
> -
> - bad = nandc->data_buffer[bbpos] != 0xff;
> + bad = bbm_bytes_buf[0] != 0xff;
BTW, as there are host->bbm_size bytes that can inform on the block
state, don't we need to check all of them?
>
> if (chip->options & NAND_BUSWIDTH_16)
> - bad = bad || (nandc->data_buffer[bbpos + 1] != 0xff);
> + bad = bad || (bbm_bytes_buf[1] != 0xff);
> err:
> return bad;
> }
Thanks,
Miquèl
Powered by blists - more mailing lists