[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190501131327.GX3845@vkoul-mobl.Dlink>
Date: Wed, 1 May 2019 18:43:27 +0530
From: Vinod Koul <vkoul@...nel.org>
To: Jon Hunter <jonathanh@...dia.com>
Cc: Ben Dooks <ben.dooks@...ethink.co.uk>,
linux-kernel@...ts.codethink.co.uk,
Dmitry Osipenko <digetx@...il.com>,
Laxman Dewangan <ldewangan@...dia.com>,
Dan Williams <dan.j.williams@...el.com>,
Thierry Reding <thierry.reding@...il.com>,
dmaengine@...r.kernel.org, linux-tegra@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] dma: tegra: add accurate reporting of dma state
On 01-05-19, 09:33, Jon Hunter wrote:
> > @@ -1444,12 +1529,7 @@ static int tegra_dma_probe(struct platform_device *pdev)
> > BIT(DMA_SLAVE_BUSWIDTH_4_BYTES) |
> > BIT(DMA_SLAVE_BUSWIDTH_8_BYTES);
> > tdma->dma_dev.directions = BIT(DMA_DEV_TO_MEM) | BIT(DMA_MEM_TO_DEV);
> > - /*
> > - * XXX The hardware appears to support
> > - * DMA_RESIDUE_GRANULARITY_BURST-level reporting, but it's
> > - * only used by this driver during tegra_dma_terminate_all()
> > - */
> > - tdma->dma_dev.residue_granularity = DMA_RESIDUE_GRANULARITY_SEGMENT;
> > + tdma->dma_dev.residue_granularity = DMA_RESIDUE_GRANULARITY_BURST;
> > tdma->dma_dev.device_config = tegra_dma_slave_config;
> > tdma->dma_dev.device_terminate_all = tegra_dma_terminate_all;
> > tdma->dma_dev.device_tx_status = tegra_dma_tx_status;
>
> In addition to Dmitry's comments, can you please make sure you run this
> through checkpatch.pl?
And use correct subsystem name !
--
~Vinod
Powered by blists - more mailing lists