[PATCH -next] mtd: nand: Add support for Toshiba BENAND (Built-in ECC NAND)

[Jean-Louis Thekekara]

Hi Kobayashi, Boris,

I'm using a Toshiba BENAND for our next product and had to adapt the 
original patch for our custom kernel (4.9). I was about to propose a 
patch for linux-next until I see this update proposed by Kobayashi.

I have a few comments on it.

On 26/05/2017 18:22, boris.brezillon at free-electrons.com (Boris
>> +config MTD_NAND_BENAND
>> +	bool "Support for Toshiba BENAND (Built-in ECC NAND)"
>> +	default n
>> +	help
>> +	  This enables support for Toshiba BENAND.
>> +	  Toshiba BENAND is a SLC NAND solution that automatically
>> +	  generates ECC inside NAND chip.
>> +
>> +config MTD_NAND_BENAND_ECC_STATUS
>> +	bool "Enable ECC Status Read Command(0x7A)"
>> +	depends on MTD_NAND_BENAND
>> +	default n
>> +	help
>> +	  This enables support for ECC Status Read Command(0x7A) of BENAND.
>> +	  When this enables, report the real number of bitflips.
>> +	  In other cases, report the assumud number.
>> +
> 
> Please drop the Kconfig options. The amount of code added here is quite
> small, and I don't think we need to compile it out. If the vendor code
> continues to grow we'll see how we want to deal with that, but we're
> not there yet.
> 
I'm interested into keeping MTD_NAND_BENAND_ECC_STATUS config for two 
reasons:

* if disabled, this can save some extra cycles. One can decide to report 
an arbitrary number of bitflips (= mtd->bitflip_threshold), it's fine.
* some NAND controller/driver might not support this command, as you 
stated later.

>>   static void toshiba_nand_decode_id(struct nand_chip *chip)
>>   {
>>   	struct mtd_info *mtd = nand_to_mtd(chip);
>> @@ -33,15 +124,32 @@ static void toshiba_nand_decode_id(struct nand_chip *chip)
>>   	 */
>>   	if (chip->id.len >= 6 && nand_is_slc(chip) &&
>>   	    (chip->id.data[5] & 0x7) == 0x6 /* 24nm */ &&
>> -	    !(chip->id.data[4] & 0x80) /* !BENAND */)
>> -		mtd->oobsize = 32 * mtd->writesize >> 9;
>> +	    (chip->id.data[4] & 0x80) /* BENAND */) {
>> +		if (IS_ENABLED(CONFIG_MTD_NAND_BENAND))
>> +			chip->ecc.mode = NAND_ECC_BENAND;
> 
> No, you should not set that explicitly. This choice should be left to
> the user. Now, since the internal ECC engine cannot be disabled here,
> you should fail in toshiba_nand_init() if you are dealing with a BENAND
> and chip->ecc.mode != NAND_ECC_ON_DIE.
> 
> 
>> +	} else {
>> +		mtd->oobsize = 32 * mtd->writesize >> 9;	/* !BENAND */
>> +	}
> 
> You're changing the ID decoding logic here.
> 
> It should be:
> 
> 	if (chip->id.len >= 6 && nand_is_slc(chip) &&
>    	    (chip->id.data[5] & 0x7) == 0x6 /* 24nm */) {
> 		if (chip->id.data[4] & 0x80)
> 			chip->ecc.mode = NAND_ECC_BENAND;
> 		else
> 			mtd->oobsize = 32 * mtd->writesize >> 9;
> 	}
>>   }
>>

I have a BENAND in my hands which, according to the datasheet reports 
only 5 bytes, so we can't depend on chip->id.len >= 6 for selecting 
NAND_ECC_BENAND. Another reason: some NAND controller don't report more 
than 5 bytes (which is, by the way, our case).

It could be something like:

>  if (chip->id.len >=5) {
>     if(chip->id.data[4] & 0x80) {
>       chip->ecc.mode = NAND_ECC_BENAND;
>     }
>     /*
>      * Toshiba 24nm raw SLC (i.e., not BENAND) have 32B OOB per
>      * 512B page. For Toshiba SLC, we decode the 5th/6th byte as
>      * follows:
>      * - ID byte 6, bits[2:0]: 100b -> 43nm, 101b -> 32nm,
>      *                         110b -> 24nm
>      * - ID byte 5, bit[7]:    1 -> BENAND, 0 -> raw SLC
>      */
>     else if (chip->id.len >= 6 && nand_is_slc(chip) &&
>              (chip->id.data[5] & 0x7) == 0x6 /* 24nm */) {
>       mtd->oobsize = 32 * mtd->writesize >> 9;
>     }
>   }
    Regards,
Jean-Louis Thekekara.