From: "Shevchenko, Andriy" <andriy.shevchenko@intel.com>
To: "Koul, Vinod" <vinod.koul@intel.com>
Cc: "Williams, Dan J" <dan.j.williams@intel.com>,
Youquan Song <youquan.song@linux.jf.intel.com>,
Greg KH <gregkh@linuxfoundation.org>,
"Song, Youquan" <youquan.song@intel.com>,
"Westerberg, Mika" <mika.westerberg@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] dma: Add interface to calculate data transferred
Date: Wed, 16 Oct 2013 09:13:20 +0000 [thread overview]
Message-ID: <1381914782.29062.137.camel@smile> (raw)
In-Reply-To: <20131016075702.GW2954@intel.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1398 bytes --]
On Wed, 2013-10-16 at 13:27 +0530, Vinod Koul wrote:
> On Wed, Oct 16, 2013 at 02:06:30PM +0530, Shevchenko, Andriy wrote:
> > On Wed, 2013-10-16 at 11:08 +0530, Vinod Koul wrote:
[]
> > > Well am going to take it a bit further and ask you why do we need the
> > > /sys/class/dma? I have never used it for slave work.
> >
> > How user (who, f.e., would like to run dmatest) will know names of the
> > channels provided?
> Ok dmatest requires this, I overlooked that part
>
> > How could we see what channels of certain dma controller are requested /
> > busy from userspace?
> But do end user care or need to know about this?
The idea is to have some test cases. So, end user probably doesn't
really need this.
--
Andy Shevchenko <andriy.shevchenko@intel.com>
Intel Finland Oy
---------------------------------------------------------------------
Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki
Business Identity Code: 0357606 - 4
Domiciled in Helsinki
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next prev parent reply other threads:[~2013-10-16 9:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 21:42 DMA: Calculate how many data transferred by DMA Youquan Song
2013-10-11 21:42 ` [PATCH 1/2] dma: Add interface to calculate data transferred Youquan Song
2013-10-11 10:22 ` Shevchenko, Andriy
2013-10-11 13:33 ` Greg KH
2013-10-13 15:26 ` Vinod Koul
2013-10-15 18:31 ` Youquan Song
2013-10-15 15:30 ` Greg KH
2013-10-15 15:55 ` Dan Williams
2013-10-15 16:17 ` Greg KH
2013-10-16 5:38 ` Vinod Koul
2013-10-16 8:36 ` Shevchenko, Andriy
2013-10-16 7:57 ` Vinod Koul
2013-10-16 9:13 ` Shevchenko, Andriy [this message]
2013-10-16 14:12 ` Greg KH
2013-10-16 15:07 ` Vinod Koul
2013-10-16 18:17 ` Dan Williams
2013-10-11 21:42 ` [PATCH 2/2] dma: calculate the data tranferred by 8250 Youquan Song
2013-10-11 13:32 ` Greg KH
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=1381914782.29062.137.camel@smile \
--to=andriy.shevchenko@intel.com \
--cc=dan.j.williams@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@intel.com \
--cc=vinod.koul@intel.com \
--cc=youquan.song@intel.com \
--cc=youquan.song@linux.jf.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