Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Vaishnav Achath <vaishnav.a@ti.com>
To:     <peter.ujfalusi@gmail.com>, <vkoul@kernel.org>,
        <broonie@kernel.org>, <dmaengine@vger.kernel.org>,
        <linux-kernel@vger.kernel.org>, <linux-spi@vger.kernel.org>
CC:     <vigneshr@ti.com>, <kishon@ti.com>, <vaishnav.a@ti.com>
Subject: [PATCH 0/2] spi: spi-omap2-mcspi: Use EOW interrupt for transfer completion
Date:   Mon, 22 Aug 2022 14:45:29 +0530
Message-ID: <20220822091531.27827-1-vaishnav.a@ti.com>
MIME-Version: 1.0
Content-Type: text/plain
Precedence: bulk

When using MCSPI with DMA enabled in Master/Slave mode, real-time 
performance issues were observed which were root caused to the 
uncertain delays in the  TX completion calculation mechanism in
k3-udma driver.

This series updates the omap2-mcspi driver to use End of Word(EOW)
interrupt to identify transaction completion and remove the usage
of DMA rx_completion and tx_completion for identifying transaction
completion.

Tested on J721E SK (for both Master and Slave Mode) for Full Duplex,
TX Only and RX Only mode transactions.Also tested with ILI9225 based
SPI TFT Display.

Vaishnav Achath (2):
  dmaengine: ti: k3-udma: Respond TX done if DMA_PREP_INTERRUPT is not
    requested
  spi: spi-omap2-mcspi: Use EOW interrupt for completion when DMA
    enabled

 drivers/dma/ti/k3-udma.c      |   5 +-
 drivers/spi/spi-omap2-mcspi.c | 141 +++++++++-------------------------
 2 files changed, 40 insertions(+), 106 deletions(-)

-- 
2.17.1