Re: [PATCH v2] drivers:mtd:spi-nor:checkup FSR error bits

2017-12-05 Thread Cyrille Pitchen
Le 04/12/2017 à 14:27, Bean Huo (beanhuo) a écrit : > Hi, Cyrille > >> Hi Bean, >> >> Le 04/12/2017 à 13:34, Bean Huo (beanhuo) a écrit : >>> For Micron spi nor device, when erase/program operation fails, >>> especially the failure results from intending to modify protected >>> space, spi-nor uppe

RE: [PATCH v2] drivers:mtd:spi-nor:checkup FSR error bits

2017-12-04 Thread Bean Huo (beanhuo)
Hi, Cyrille >Hi Bean, > >Le 04/12/2017 à 13:34, Bean Huo (beanhuo) a écrit : >> For Micron spi nor device, when erase/program operation fails, >> especially the failure results from intending to modify protected >> space, spi-nor upper layers still get the return which shows the >> operation succe

Re: [PATCH v2] drivers:mtd:spi-nor:checkup FSR error bits

2017-12-04 Thread Cyrille Pitchen
Hi Bean, Le 04/12/2017 à 13:34, Bean Huo (beanhuo) a écrit : > For Micron spi nor device, when erase/program operation > fails, especially the failure results from intending to > modify protected space, spi-nor upper layers still get > the return which shows the operation succeeds. This is > becau

[PATCH v2] drivers:mtd:spi-nor:checkup FSR error bits

2017-12-04 Thread Bean Huo (beanhuo)
For Micron spi nor device, when erase/program operation fails, especially the failure results from intending to modify protected space, spi-nor upper layers still get the return which shows the operation succeeds. This is because current spi_nor_fsr_ready() only uses FSR bit.7 (flag status register