From: Dmitry Osipenko <digetx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Thierry Reding
<thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Jonathan Hunter
<jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH v3 0/2] Correct Tegra20 FUSE driver DMA usage
Date: Fri, 20 Oct 2017 01:08:02 +0300 [thread overview]
Message-ID: <cover.1508450681.git.digetx@gmail.com> (raw)
Change log:
v3:
- Addressed v2 review comments: added 'config.device_fc = false'
and utilize of_device_is_compatible() for dma-filter
v2:
- Dropped DT patch as turned out it was incorrect and made things
work by luck.
- Now FUSE driver requests DMA channel from the APB DMA driver
utilizing DMA channel filter.
- This patchset now depends on the APB DMA driver patch that allows
DMA client to issue a non-flow controlled transfers. I haven't
included that patch to this patchset since DMA usage is broken
anyway right now. It will work once this patchset and APBDMA
patch get applied.
Dmitry Osipenko (2):
soc/tegra: fuse: Fix reading registers using DMA on Tegra20
soc/tegra: fuse: Explicitly request DMA channel from APB DMA driver
drivers/soc/tegra/fuse/fuse-tegra.c | 1 +
drivers/soc/tegra/fuse/fuse-tegra20.c | 13 +++++++++++--
2 files changed, 12 insertions(+), 2 deletions(-)
--
2.14.2
next reply other threads:[~2017-10-19 22:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 22:08 Dmitry Osipenko [this message]
[not found] ` <cover.1508450681.git.digetx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-10-19 22:08 ` [PATCH v3 1/2] soc/tegra: fuse: Fix reading registers using DMA on Tegra20 Dmitry Osipenko
2017-10-19 22:08 ` [PATCH v3 2/2] soc/tegra: fuse: Explicitly request DMA channel from APB DMA driver Dmitry Osipenko
[not found] ` <059ca713c7416aedeb0080ab4b8a49da430a30b9.1508450681.git.digetx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-10-20 11:00 ` Jon Hunter
2017-11-14 11:25 ` [PATCH v3 0/2] Correct Tegra20 FUSE driver DMA usage Dmitry Osipenko
[not found] ` <a149fdb0-64ff-fa99-734e-9335605191ce-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-11-14 15:01 ` Thierry Reding
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=cover.1508450681.git.digetx@gmail.com \
--to=digetx-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=jonathanh-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).