From: Vinod Koul <vkoul@kernel.org>
To: aman.kumar@intel.com
Cc: dmaengine@vger.kernel.org, andriy.shevchenko@linux.intel.com,
srikanth.thokala@intel.com,
mallikarjunappa.sangannavar@intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/1] dmaengine: idma64: Update bytes_transferred field
Date: Fri, 10 Feb 2023 14:32:58 +0530 [thread overview]
Message-ID: <Y+YIQkrlJvGOh1bn@matsya> (raw)
In-Reply-To: <20230203121702.15725-1-aman.kumar@intel.com>
On 03-02-23, 17:47, aman.kumar@intel.com wrote:
> From: Aman Kumar <aman.kumar@intel.com>
>
> 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.
Applied, thanks
--
~Vinod
prev parent reply other threads:[~2023-02-10 9:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 12:17 [PATCH v1 1/1] dmaengine: idma64: Update bytes_transferred field aman.kumar
2023-02-10 9:02 ` Vinod Koul [this message]
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=Y+YIQkrlJvGOh1bn@matsya \
--to=vkoul@kernel.org \
--cc=aman.kumar@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mallikarjunappa.sangannavar@intel.com \
--cc=srikanth.thokala@intel.com \
/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