Hi Jin
On 3/8/19 9:28 AM, Xiao, Jin wrote:
Yes, the spi core has de-asserted the CS before the
pxa2xx_spi_unprepare_transfer(). The problem on my side is that the new
transfer will restart the SSP in pxa2xx_spi_transfer_one(). The spi core
has asserted the CS again before restart the SSP.
Hi
On 3/8/2019 12:09 AM, Mark Brown wrote:
On Thu, Mar 07, 2019 at 05:26:53PM +0200, Jarkko Nikula wrote:
On 3/7/19 9:24 AM, xiao jin wrote:
The patch is to do cs again if spi-pxa2xx restar the SSP during
pxa2xx_spi_transfer_one()
Hmm.. please correct me if I'm wrong but
On Thu, Mar 07, 2019 at 05:26:53PM +0200, Jarkko Nikula wrote:
> On 3/7/19 9:24 AM, xiao jin wrote:
> > The patch is to do cs again if spi-pxa2xx restar the SSP during
> > pxa2xx_spi_transfer_one()
> Hmm.. please correct me if I'm wrong but pxa2xx_spi_unprepare_transfer() is
> called always when
Hi
Is this also related to the regression with d5898e19c0d7 ("spi: pxa2xx:
Use core message processing loop") you have found or another issue?
Comments below.
On 3/7/19 9:24 AM, xiao jin wrote:
The spi-pxa2xx can't read and write data correctly on our board.
The pxa_ssp_type is LPSS_BXT_SSP
The spi-pxa2xx can't read and write data correctly on our board.
The pxa_ssp_type is LPSS_BXT_SSP in our case.
With more debug we find that it's related to restart the SPP
during pxa2xx_spi_transfer_one().
In the normal case the spi_transfer_one_message() calls spi-pxa2xx
cs_assert before
5 matches
Mail list logo
