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: Mon, 22 Jul 2019 02:24:29 -0700 [thread overview]
Message-ID: <20190722092429.GB12167@infradead.org> (raw)
In-Reply-To: <3c2c98e785704969a862715ab52ce2de@SFHDAG7NODE2.st.com>
On Mon, Jul 22, 2019 at 08:41:32AM +0000, Loic PALLARDY wrote:
> Ongoing...
> Two topics to clean up:
> - Sub device creation and DMA ops inheritance --> need to use platform_device or device tree
> - dma_declare_coherent_memory use --> it has been introduced to support internal memories declared via reg field.
> I propose to migrate existing drivers on reserved memory usage and so remove dma_declare_coherent call from remoteproc core.
I thought this was inter-related in that you needed the additional
field with the manual memory region for the subdevs, but I guess I
misunderstood. Anyway, thanks for doing the work.
prev parent reply other threads:[~2019-07-22 9:24 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
2019-07-22 8:41 ` Loic PALLARDY
2019-07-22 9:24 ` Christoph Hellwig [this message]
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=20190722092429.GB12167@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 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).