From: Christoph Hellwig <hch@infradead.org>
To: Loic PALLARDY <loic.pallardy@st.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Clement Leger <cleger@kalray.eu>,
Ohad Ben-Cohen <ohad@wizery.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
"linux-remoteproc@vger.kernel.org"
<linux-remoteproc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] remoteproc: copy parent dma_pfn_offset for vdev
Date: Thu, 18 Jul 2019 23:32:50 -0700 [thread overview]
Message-ID: <20190719063250.GA9545@infradead.org> (raw)
In-Reply-To: <20190708184546.GA20670@infradead.org>
On Mon, Jul 08, 2019 at 11:45:46AM -0700, Christoph Hellwig wrote:
> > But that's breaking legacy as all platforms will have to add a virtio device node in
> > their DT file...
> >
> > Is it aligned with your view ?
>
> Yes, that is how I'd assume it works. But given that until recently
> you did now have these subdevices for dma coherent purposes we can't
> really break anything older than that, so I might still be missing
> something.
Any chance we could expedite this? remoteproc is the only driver
inheriting dma ops to subdevices, and the only one using
dma_declare_coherent_memory. I'd really like to clean this mess up
rather sooner than later.
next prev parent reply other threads:[~2019-07-19 6:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 9:55 [PATCH] remoteproc: recopy parent dma_pfn_offset for vdev Clement Leger
2019-06-17 10:10 ` Loic PALLARDY
2019-06-29 18:59 ` Bjorn Andersson
2019-07-01 7:02 ` [PATCH v2] remoteproc: copy " Clement Leger
2019-07-02 6:27 ` Bjorn Andersson
2019-07-02 13:22 ` Christoph Hellwig
2019-07-02 15:36 ` Loic PALLARDY
2019-07-08 18:45 ` Christoph Hellwig
2019-07-19 6:32 ` Christoph Hellwig [this message]
2019-07-22 8:41 ` Loic PALLARDY
2019-07-22 9:24 ` Christoph Hellwig
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=20190719063250.GA9545@infradead.org \
--to=hch@infradead.org \
--cc=bjorn.andersson@linaro.org \
--cc=cleger@kalray.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=loic.pallardy@st.com \
--cc=ohad@wizery.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.