RE: [RFC] spi-nor: fix cross die reads on Micron multi-die devices

2016-01-21 Thread beanhuo
> Hi Bean, > > On Thu, 21 Jan 2016 01:06:48 + > Bean Huo 霍斌斌 (beanhuo) wrote: > > > Hi, Adam and Boris > > > > For Micron MT25Q ,MT25T and MT35Q, they does not exist this action > > even they are Multi-die devices. So when the last byte of the die > > selected is read, the next byte output

Re: [RFC] spi-nor: fix cross die reads on Micron multi-die devices

2016-01-21 Thread Boris Brezillon
Hi Bean, On Thu, 21 Jan 2016 01:06:48 + Bean Huo 霍斌斌 (beanhuo) wrote: > Hi, Adam and Boris > > For Micron MT25Q ,MT25T and MT35Q, they does not exist this action even they > are > Multi-die devices. So when the last byte of the die selected is read, the > next byte output > is the first

Re: [RFC] spi-nor: fix cross die reads on Micron multi-die devices

2016-01-21 Thread Boris Brezillon
Hi Bean, On Thu, 21 Jan 2016 01:06:48 + Bean Huo 霍斌斌 (beanhuo) wrote: > Hi, Adam and Boris > > For Micron MT25Q ,MT25T and MT35Q, they does not exist this action even they > are > Multi-die devices. So when the last byte of the die selected is read, the > next byte

RE: [RFC] spi-nor: fix cross die reads on Micron multi-die devices

2016-01-21 Thread beanhuo
> Hi Bean, > > On Thu, 21 Jan 2016 01:06:48 + > Bean Huo 霍斌斌 (beanhuo) wrote: > > > Hi, Adam and Boris > > > > For Micron MT25Q ,MT25T and MT35Q, they does not exist this action > > even they are Multi-die devices. So when the last byte of the die > > selected is read,

RE: [RFC] spi-nor: fix cross die reads on Micron multi-die devices

2016-01-20 Thread beanhuo
Hi, Adam and Boris For Micron MT25Q ,MT25T and MT35Q, they does not exist this action even they are Multi-die devices. So when the last byte of the die selected is read, the next byte output is the first byte of next die(not the same die). You can check this by extended address register

RE: [RFC] spi-nor: fix cross die reads on Micron multi-die devices

2016-01-20 Thread beanhuo
Hi, Adam and Boris For Micron MT25Q ,MT25T and MT35Q, they does not exist this action even they are Multi-die devices. So when the last byte of the die selected is read, the next byte output is the first byte of next die(not the same die). You can check this by extended address register