From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: "Geert Uytterhoeven" <geert@linux-m68k.org>,
"Dan Williams" <dan.j.williams@intel.com>,
"Vinod Koul" <vinod.koul@intel.com>,
"Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>,
dmaengine@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Hiroyuki Yokoyama" <hiroyuki.yokoyama.vx@renesas.com>
Subject: Re: [PATCH] dmaengine: rcar-dmac: use DMATCRB when xxx_TO_MEM direction
Date: Tue, 17 Oct 2017 14:55:06 +0300 [thread overview]
Message-ID: <20662392.QIFALme4hY@avalon> (raw)
In-Reply-To: <87r2u27hx9.wl%kuninori.morimoto.gx@renesas.com>
Hi Morimoto-san,
On Tuesday, 17 October 2017 03:18:49 EEST Kuninori Morimoto wrote:
> Hi
>
> > Thank you for your explanation.
> > My 1st patch focused to "transfer completed" count (= TCRB) for all case.
> > In any case, "completed" information should be used.
> > But in MEM_TO_DEV case, I thought if is OK if data was read from MEM
> > (= the data will be send to DEV automatically, I didn't care about
> > interruption) But yes, your opinion is correct I think.
> >
> > I think MEM_TO_MEM should use TCRB.
> > I think logic is same as your MEM_TO_DEV explanation ?
TCRB is better for MEM_TO_MEM too in my opinion. When reporting residue
information we should indicate how much data has been transferred, and that
includes both read from source and written to destination.
> > Anyway, in all case I can use TCRB in v3 patch,
> > and it needs abouve explanation.
>
> If so, I think v1 is enough... ?
> "transfer completed count is important for all case" is no doubt... ?
That's correct, but I don't think the explanation was detailed and clear
enough. If it was Geert wouldn't have asked for a v2, and you wouldn't have
agreed to his request :-)
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2017-10-17 11:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 7:28 [PATCH] dmaengine: rcar-dmac: use DMATCRB when xxx_TO_MEM direction Kuninori Morimoto
2017-10-16 8:49 ` Laurent Pinchart
2017-10-17 0:12 ` Kuninori Morimoto
2017-10-17 0:18 ` Kuninori Morimoto
2017-10-17 11:55 ` Laurent Pinchart [this message]
2017-10-18 0:01 ` Kuninori Morimoto
2017-10-18 13:46 ` Laurent Pinchart
2017-10-18 13:47 ` Geert Uytterhoeven
2017-10-19 0:49 ` Kuninori Morimoto
2017-10-20 6:12 ` Vinod Koul
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=20662392.QIFALme4hY@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=hiroyuki.yokoyama.vx@renesas.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
--cc=vinod.koul@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