Re: [U-Boot] [PATCH v2 1/3] spi: ti_qspi: Fix failure on multiple READ_ID cmd

2016-07-23 Thread Jagan Teki
On 22 July 2016 at 15:38, Mugunthan V N wrote: > On Friday 22 July 2016 10:55 AM, Vignesh R wrote: >> Populating QSPI_RD_SNGL bit(0x1) in priv->cmd means that value >> QSPI_INVAL (0x4) is not written to CMD field of QSPI_SPI_CMD_REG in >> ti_qspi_cs_deactivate(). Therefore CS is never deactivated

Re: [U-Boot] [PATCH v2 1/3] spi: ti_qspi: Fix failure on multiple READ_ID cmd

2016-07-22 Thread Mugunthan V N
On Friday 22 July 2016 10:55 AM, Vignesh R wrote: > Populating QSPI_RD_SNGL bit(0x1) in priv->cmd means that value > QSPI_INVAL (0x4) is not written to CMD field of QSPI_SPI_CMD_REG in > ti_qspi_cs_deactivate(). Therefore CS is never deactivated between > successive READ ID which results in sf prob

Re: [U-Boot] [PATCH v2 1/3] spi: ti_qspi: Fix failure on multiple READ_ID cmd

2016-07-22 Thread Jagan Teki
On 22 July 2016 at 10:55, Vignesh R wrote: > Populating QSPI_RD_SNGL bit(0x1) in priv->cmd means that value > QSPI_INVAL (0x4) is not written to CMD field of QSPI_SPI_CMD_REG in > ti_qspi_cs_deactivate(). Therefore CS is never deactivated between > successive READ ID which results in sf probe to f

[U-Boot] [PATCH v2 1/3] spi: ti_qspi: Fix failure on multiple READ_ID cmd

2016-07-21 Thread Vignesh R
Populating QSPI_RD_SNGL bit(0x1) in priv->cmd means that value QSPI_INVAL (0x4) is not written to CMD field of QSPI_SPI_CMD_REG in ti_qspi_cs_deactivate(). Therefore CS is never deactivated between successive READ ID which results in sf probe to fail. Fix this by not populating priv->cmd with QSPI_