From: Neil Armstrong <narmstrong@baylibre.com>
To: Arnd Bergmann <arnd@arndb.de>, Mark Brown <broonie@kernel.org>
Cc: linux-spi@vger.kernel.org, linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] spi: meson-spicc: add support for DMA
Date: Wed, 14 Sep 2022 14:35:36 +0200 [thread overview]
Message-ID: <499f0940-3d7f-0ed5-e469-5c0979e6f761@baylibre.com> (raw)
In-Reply-To: <667da463-1edc-4a99-9ac1-85303d9187c6@www.fastmail.com>
On 14/09/2022 13:19, Arnd Bergmann wrote:
> On Tue, Sep 13, 2022, at 4:03 PM, Neil Armstrong wrote:
>
>> +static void meson_spicc_setup_dma_burst(struct meson_spicc_device *spicc)
>> +{
> ...
>> + /* Setup burst length */
>> + writel_relaxed(ld_ctr1, spicc->base + SPICC_LD_CNTL1);
>> +
>> + writel_relaxed(SPICC_DMA_ENABLE | SPICC_DMA_URGENT |
>> + FIELD_PREP(SPICC_TXFIFO_THRESHOLD_MASK, txfifo_thres) |
>> + FIELD_PREP(SPICC_READ_BURST_MASK, read_req) |
>> + FIELD_PREP(SPICC_RXFIFO_THRESHOLD_MASK, rxfifo_thres) |
>> + FIELD_PREP(SPICC_WRITE_BURST_MASK, write_req),
>> + spicc->base + SPICC_DMAREG);
>> +}
>
> It looks like this last writel_relaxed() starts the DMA, but I don't
> see any barrier that serializes it against the memory access, which
> could still be in a store buffer.
You're right this one restarts a DMA, so yeah it should not have the relaxed accessor.
But the one starting the first DMA is in another place and aswell should not use relaxed.
>
>> + /* Sometimes, TC gets triggered while the RX fifo isn't fully flushed *
>> + if (spicc->using_dma) {
>> + unsigned int rxfifo_count = FIELD_GET(SPICC_RXCNT_MASK,
>> + readl_relaxed(spicc->base + SPICC_TESTREG));
>
> Same here in the interrupt controller, I don't see anything enforcing
> the DMA to actually complete before the readl_relaxed().
I don't see the relathionship between a register relaxed read and the DMA not finishing
writing the data in uncached memory, for me it's 2 unrelated things.
>
> At the very minimum, I think these two have to use non-relaxed
> accessors when adding DMA support, but an easier approach would
> be to use those consistently throughout the driver.
I'll do a check of those accessors for v2.
>
> Arnd
Thanks,
Neil
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2022-09-14 12:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 14:03 Neil Armstrong
2022-09-14 11:19 ` Arnd Bergmann
2022-09-14 12:35 ` Neil Armstrong [this message]
2022-09-14 13:17 ` Arnd Bergmann
2022-09-14 13:43 ` Neil Armstrong
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=499f0940-3d7f-0ed5-e469-5c0979e6f761@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.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®