From: Vinod Koul <vinod.koul-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Dmitry Osipenko <digetx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Thierry Reding
<thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Jonathan Hunter
<jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
Laxman Dewangan
<ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
dmaengine-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2] dmaengine: tegra-apb: Support non-flow controlled slave configuration
Date: Wed, 15 Nov 2017 21:24:22 +0530 [thread overview]
Message-ID: <20171115155422.GN3187@localhost> (raw)
In-Reply-To: <57ef35f0-d8fa-5238-901e-11cd9d001e02-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On Tue, Nov 14, 2017 at 02:23:07PM +0300, Dmitry Osipenko wrote:
> On 20.10.2017 01:13, Dmitry Osipenko wrote:
> > This allows DMA client to issue a non-flow controlled TX. In particular
> > it is needed for the fuse driver that reads fuse registers using APBDMA
> > to workaround a HW bug that results in hang when CPU and DMA perform
> > simultaneous access to fuse peripheral.
> >
> > Signed-off-by: Dmitry Osipenko <digetx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> > Reviewed-by: Jon Hunter <jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
>
> Vinod, are you going to apply this patch for 4.15?
Sorry I dont seem to have this one in my queue and dont see it applied, not
sure why. Can you guys resend please
--
~Vinod
next prev parent reply other threads:[~2017-11-15 15:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 22:13 [PATCH v2] dmaengine: tegra-apb: Support non-flow controlled slave configuration Dmitry Osipenko
[not found] ` <20171019221308.18707-1-digetx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-11-14 11:23 ` Dmitry Osipenko
[not found] ` <57ef35f0-d8fa-5238-901e-11cd9d001e02-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-11-15 15:54 ` Vinod Koul [this message]
2017-11-16 17:16 ` Dmitry Osipenko
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=20171115155422.GN3187@localhost \
--to=vinod.koul-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=digetx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=dmaengine-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/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;
as well as URLs for NNTP newsgroup(s).