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().
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
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.
>
>
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
4 matches
Mail list logo