Re: [U-Boot] [PATCH v2] mtd: nand: fsl-ifc: fix support of multiple NAND devices

2017-11-17 Thread York Sun
On 10/30/2017 02:58 PM, Scott Wood wrote: > On Mon, 2017-10-30 at 18:50 +, York Sun wrote: >> On 10/20/2017 03:43 AM, Kurt Kanzenbach wrote: >>> Currently the chipselect used to identify the corresponding NAND chip is >>> stored >>> at the controller and only set during fsl_ifc_chip_init().

Re: [U-Boot] [PATCH v2] mtd: nand: fsl-ifc: fix support of multiple NAND devices

2017-10-30 Thread Scott Wood
On Mon, 2017-10-30 at 18:50 +, York Sun wrote: > On 10/20/2017 03:43 AM, Kurt Kanzenbach wrote: > > Currently the chipselect used to identify the corresponding NAND chip is > > stored > > at the controller and only set during fsl_ifc_chip_init(). This way, only > > the > > last NAND chip is

Re: [U-Boot] [PATCH v2] mtd: nand: fsl-ifc: fix support of multiple NAND devices

2017-10-30 Thread York Sun
On 10/20/2017 03:43 AM, Kurt Kanzenbach wrote: > Currently the chipselect used to identify the corresponding NAND chip is > stored > at the controller and only set during fsl_ifc_chip_init(). This way, only the > last NAND chip is working, as the previous value of cs_nand gets overwritten. > >

[U-Boot] [PATCH v2] mtd: nand: fsl-ifc: fix support of multiple NAND devices

2017-10-20 Thread Kurt Kanzenbach
Currently the chipselect used to identify the corresponding NAND chip is stored at the controller and only set during fsl_ifc_chip_init(). This way, only the last NAND chip is working, as the previous value of cs_nand gets overwritten. In order to solve this issue the chipselect is computed on