diff options
| author | Aman Kumar <[email protected]> | 2023-02-03 17:47:02 +0530 |
|---|---|---|
| committer | Vinod Koul <[email protected]> | 2023-02-16 18:45:48 +0530 |
| commit | e922bbf37564a4c67efca9dd6133eaadbffb65f5 (patch) | |
| tree | 13b74d35ca3063ba8c3332a9b0819bf78796eea3 | |
| parent | 8d1b7bd543833169a5f5f74c4753509ab406f381 (diff) | |
dmaengine: idma64: Update bytes_transferred field
Currently when 8250 data transfer is done, bytes_tranferred always returns
0 at /sys/devices/pci0000\:\:**.*/dma/dma*chan*/bytes_transferred.
In many cases it gives false impression that data is not being
trasferred via DMA.
So, updating the bytes_transferred field to count the bytes
whenever there is data transfer using idma64.
Co-developed-by: Srikanth Thokala <[email protected]>
Signed-off-by: Srikanth Thokala <[email protected]>
Signed-off-by: Aman Kumar <[email protected]>
Reviewed-by: Andy Shevchenko <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Vinod Koul <[email protected]>
| -rw-r--r-- | drivers/dma/idma64.c | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/drivers/dma/idma64.c b/drivers/dma/idma64.c index cd9622f6e59c..0ac634a51c5e 100644 --- a/drivers/dma/idma64.c +++ b/drivers/dma/idma64.c @@ -137,8 +137,11 @@ static void idma64_chan_irq(struct idma64 *idma64, unsigned short c, u32 status_err, u32 status_xfer) { struct idma64_chan *idma64c = &idma64->chan[c]; + struct dma_chan_percpu *stat; struct idma64_desc *desc; + stat = this_cpu_ptr(idma64c->vchan.chan.local); + spin_lock(&idma64c->vchan.lock); desc = idma64c->desc; if (desc) { @@ -149,6 +152,7 @@ static void idma64_chan_irq(struct idma64 *idma64, unsigned short c, dma_writel(idma64, CLEAR(XFER), idma64c->mask); desc->status = DMA_COMPLETE; vchan_cookie_complete(&desc->vdesc); + stat->bytes_transferred += desc->length; idma64_start_transfer(idma64c); } |