From: Alexander Kochetkov <al.kochet@gmail.com>
To: Maxime Ripard <maxime@cerno.tech>
Cc: Mark Brown <broonie@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
linux-spi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] spi: spi-sun6i: implement DMA-based transfer mode
Date: Mon, 19 Oct 2020 16:17:18 +0300 [thread overview]
Message-ID: <4B0B0459-DFCF-4307-8CAE-A2B579B0AF5E@gmail.com> (raw)
In-Reply-To: <20201019082129.myxpxla5xwoqwldo@gilmour.lan>
Hi, Maxime! Thanks for reviewing patches!
>>
>> +static int sun6i_spi_prepare_dma(struct sun6i_spi *sspi,
>> + struct spi_transfer *tfr)
>> +{
>> + struct dma_async_tx_descriptor *rxdesc, *txdesc;
>> + struct spi_master *master = sspi->master;
>> +
>> + rxdesc = NULL;
>> + if (tfr->rx_buf) {
>> + struct dma_slave_config rxconf = {
>> + .direction = DMA_DEV_TO_MEM,
>> + .src_addr = sspi->dma_addr_rx,
>> + .src_addr_width = 1,
>> + .src_maxburst = 1,
>> + };
>
> That doesn't really look optimal, the controller seems to be able to
> read / write 32 bits at a time from its FIFO and we probably can
> increase the burst length too?
I had doubts if it would work. I didn’t know will DMA work for transfers with lengths not
aligned to 32 bits. For example, if we init DMA with src_addr_width = 1 and
.src_maxburst = 8 will DMA work for transfer with length 11? I expect that DMA fill FIFO
with 16 bytes and SPI transfer only 11 bytes and 5 bytes will leave in TX fifo. I did the test
and there is no additional data left in the fifo buffer. Also at reception the is no memory
overwrites.
I made test with src_addr_width = 4, src_maxburst = 1 and transfer length 3. Looks
like in that case DMA doesn’t issue 4 bytes transfer.
For test with src_addr_width = 4, src_maxburst = 8 I had to adjust RF_RDY_TRIG_LEVEL_BITS
and TF_ERQ_TRIG_LEVEL_BITS of FIFO_CTL_REG to half of FIFO (32 bytes). With the config
DMA will transfer burst of half of FIFO length during transfer and remaining bytes at the end of
transfer.
>>
>> @@ -343,7 +436,8 @@ static irqreturn_t sun6i_spi_handler(int irq, void *dev_id)
>> /* Transfer complete */
>> if (status & SUN6I_INT_CTL_TC) {
>> sun6i_spi_write(sspi, SUN6I_INT_STA_REG, SUN6I_INT_CTL_TC);
>> - sun6i_spi_drain_fifo(sspi);
>> + if (!sspi->use_dma)
>> + sun6i_spi_drain_fifo(sspi);
>
> Is it causing any issue? The FIFO will be drained only if there's
> something remaining in the FIFO, which shouldn't happen with DMA?
>
No. It’s for make code patch explicit.
Remove the change?
Alexander.
next prev parent reply other threads:[~2020-10-19 13:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 15:47 Alexander Kochetkov
2020-10-19 8:21 ` Maxime Ripard
2020-10-19 13:17 ` Alexander Kochetkov [this message]
2020-10-21 16:39 ` Maxime Ripard
2020-10-19 17:43 ` Alexander Kochetkov
2020-10-20 3:52 ` Chen-Yu Tsai
2020-10-21 15:03 ` Maxime Ripard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B0B0459-DFCF-4307-8CAE-A2B579B0AF5E@gmail.com \
--to=al.kochet@gmail.com \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=maxime@cerno.tech \
--cc=wens@csie.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®