Received-SPF: pass (google.com: domain of linux-kernel+bounces-123390-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
Precedence: bulk
MIME-Version: 1.0
References: <CGME20240327033501epcas2p2bbe21301da5584f7f3a073c51a363c00@epcas2p2.samsung.com>
 <20240327033041.83625-1-jaewon02.kim@samsung.com>
In-Reply-To: <20240327033041.83625-1-jaewon02.kim@samsung.com>
From: Sam Protsenko <semen.protsenko@linaro.org>
Date: Thu, 28 Mar 2024 12:58:07 -0500
Message-ID: <CAPLW+4k4qh4ZYBufZoGbUZN0yxSE2X8bOdkEQVw1Zg9YUVpbug@mail.gmail.com>
Subject: Re: [PATCH] spi: s3c64xx: Use DMA mode from fifo size
To: Jaewon Kim <jaewon02.kim@samsung.com>
Cc: Andi Shyti <andi.shyti@kernel.org>, Mark Brown <broonie@kernel.org>, 
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>, Alim Akhtar <alim.akhtar@samsung.com>, 
	linux-spi@vger.kernel.org, linux-samsung-soc@vger.kernel.org, 
	linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, Mar 26, 2024 at 10:35=E2=80=AFPM Jaewon Kim <jaewon02.kim@samsung.c=
om> wrote:
>
> The SPI data size is smaller than FIFO, it operates in PIO mode,

Spelling: "The" -> "If the"

> and if it is larger than FIFO mode, DMA mode is selected.
>
> If the data size is the same as the FIFO size, it operates in PIO mode
> and data is separated into two transfer. In order to prevent,

Nit: "transfer" -> "transfers", "prevent" -> "prevent it"

> DMA mode must be used from the case of FIFO and data size.
>

You probably mean this code (it occurs two times in the driver):

    xfer->len =3D fifo_len - 1;

Can you please elaborate on why it's done this way? Why can't we just
do "xfer->len =3D fifo_len" and use the whole FIFO for the transfer
instead? I don't understand the necessity to split the transfer into
two chunks if its size is of FIFO length -- wouldn't it fit into FIFO
in that case? (I'm pretty sure this change is correct, just want to
understand how exactly it works).

> Fixes: 1ee806718d5e ("spi: s3c64xx: support interrupt based pio mode")

Just wonder if that fixes some throughput regression, or something
worse (like failed transfers when the transfer size is the same as
FIFO size)?

> Signed-off-by: Jaewon Kim <jaewon02.kim@samsung.com>
> ---
>  drivers/spi/spi-s3c64xx.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/spi/spi-s3c64xx.c b/drivers/spi/spi-s3c64xx.c
> index 9fcbe040cb2f..81ed5fddf83e 100644
> --- a/drivers/spi/spi-s3c64xx.c
> +++ b/drivers/spi/spi-s3c64xx.c
> @@ -430,7 +430,7 @@ static bool s3c64xx_spi_can_dma(struct spi_controller=
 *host,
>         struct s3c64xx_spi_driver_data *sdd =3D spi_controller_get_devdat=
a(host);
>
>         if (sdd->rx_dma.ch && sdd->tx_dma.ch)
> -               return xfer->len > sdd->fifo_depth;
> +               return xfer->len >=3D sdd->fifo_depth;
>
>         return false;
>  }
> @@ -826,11 +826,11 @@ static int s3c64xx_spi_transfer_one(struct spi_cont=
roller *host,
>                         return status;
>         }
>
> -       if (!is_polling(sdd) && (xfer->len > fifo_len) &&
> +       if (!is_polling(sdd) && xfer->len >=3D fifo_len &&
>             sdd->rx_dma.ch && sdd->tx_dma.ch) {
>                 use_dma =3D 1;
>

Would be nice to remove this empty line, while at it.

> -       } else if (xfer->len >=3D fifo_len) {
> +       } else if (xfer->len > fifo_len) {

Below in the same function I can see similar code:

            if (target_len >=3D fifo_len)
                xfer->len =3D fifo_len - 1;

Shouldn't that 'if' condition be fixed too? Or it's ok as it is? (Just
noticed it by searching, not sure myself, hence asking).

>                 tx_buf =3D xfer->tx_buf;
>                 rx_buf =3D xfer->rx_buf;
>                 origin_len =3D xfer->len;
> --
> 2.43.2
>
>