Re: [PATCH] spi: disable chipselect after complete transfer
From: Mark Brown
Date: Thu Feb 10 2022 - 06:19:12 EST
On Thu, Feb 10, 2022 at 10:03:16AM +0800, Yun Zhou wrote:
> if the last xfer->cs_change is true, keep_cs will be true, and it will not
> call spi_set_cs() to set CS to false. Do you mean to keep CS enabled in this
> case?
Yes, that's exactly what is supposed to happen in that case.
> I do not think it will break cs_change support. In my understanding,
> cs_change indicates whether or not change CS after an xfer completed. But at
> present if the last xfer->cs_change is true, we will not change CS to
> disabled state. Is this the result we want? I'm confused.
Yes, it behaves differently on the last transfer.
Attachment:
signature.asc
Description: PGP signature