Re: [PATCH v5 1/3] mtd: nand: don't select chip in nand_chip's block_bad op

2016-01-06 Thread Boris Brezillon
On Tue, 5 Jan 2016 10:54:59 +0530 Archit Taneja wrote: > One of the arguments passed to struct nand_chip's block_bad op is > 'getchip', which, if true, is supposed to get and select the nand device, > and later unselect and release the device. > > This op is intended to

Re: [PATCH v5 1/3] mtd: nand: don't select chip in nand_chip's block_bad op

2016-01-06 Thread Archit Taneja
On 01/06/2016 09:35 PM, Boris Brezillon wrote: On Tue, 5 Jan 2016 10:54:59 +0530 Archit Taneja wrote: One of the arguments passed to struct nand_chip's block_bad op is 'getchip', which, if true, is supposed to get and select the nand device, and later unselect and

[PATCH v5 1/3] mtd: nand: don't select chip in nand_chip's block_bad op

2016-01-04 Thread Archit Taneja
One of the arguments passed to struct nand_chip's block_bad op is 'getchip', which, if true, is supposed to get and select the nand device, and later unselect and release the device. This op is intended to be replaceable by drivers. The drivers shouldn't be responsible for selecting/unselecting