From: Christoph Hellwig <hch@lst.de>
To: Laurentiu Tudor <laurentiu.tudor@nxp.com>
Cc: Christoph Hellwig <hch@lst.de>,
"stern@rowland.harvard.edu" <stern@rowland.harvard.edu>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"marex@denx.de" <marex@denx.de>, Leo Li <leoyang.li@nxp.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"robin.murphy@arm.com" <robin.murphy@arm.com>
Subject: Re: [RFC PATCH v2 1/3] USB: use genalloc for USB HCs with local memory
Date: Wed, 15 May 2019 14:42:50 +0200 [thread overview]
Message-ID: <20190515124250.GA13754@lst.de> (raw)
In-Reply-To: <f4fc0151-5e49-77fd-7736-37cdfe57c268@nxp.com>
On Wed, May 15, 2019 at 09:57:12AM +0000, Laurentiu Tudor wrote:
> Glad I could help. On the remoteproc_virtio.c case, I had a cursory look
> and found out that the dma_declare_coherent_memory() usage was
> introduced quite recently, by this patch:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=086d08725d34c6b3333db710344ae9c4fdafb2d5
Yes. I took a look at it to, and while it isn't exactly a clean
usage of the API it at least declares system memory and not a resource.
So it doesn't really affect our plan.
next prev parent reply other threads:[~2019-05-15 12:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 14:38 [RFC PATCH v2 0/3] prerequisites for device reserved local mem rework laurentiu.tudor
2019-05-14 14:38 ` [RFC PATCH v2 1/3] USB: use genalloc for USB HCs with local memory laurentiu.tudor
2019-05-14 14:42 ` Christoph Hellwig
2019-05-15 9:57 ` Laurentiu Tudor
2019-05-15 12:42 ` Christoph Hellwig [this message]
2019-05-14 14:38 ` [RFC PATCH v2 2/3] usb: host: ohci-sm501: init genalloc for " laurentiu.tudor
2019-05-14 14:38 ` [RFC PATCH v2 3/3] usb: host: ohci-tmio: " laurentiu.tudor
2019-05-14 15:17 ` [RFC PATCH v2 0/3] prerequisites for device reserved local mem rework Robin Murphy
2019-05-14 18:29 ` Fredrik Noring
2019-05-15 10:37 ` Laurentiu Tudor
2019-05-15 16:28 ` Fredrik Noring
2019-05-16 9:35 ` Laurentiu Tudor
2019-05-16 13:47 ` Fredrik Noring
2019-05-16 11:49 ` Laurentiu Tudor
2019-05-16 15:15 ` Fredrik Noring
2019-05-17 10:52 ` Laurentiu Tudor
2019-05-17 17:41 ` Fredrik Noring
2019-05-20 11:34 ` Laurentiu Tudor
2019-05-20 15:41 ` Fredrik Noring
2019-05-21 10:32 ` hch
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=20190515124250.GA13754@lst.de \
--to=hch@lst.de \
--cc=gregkh@linuxfoundation.org \
--cc=laurentiu.tudor@nxp.com \
--cc=leoyang.li@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=marex@denx.de \
--cc=robin.murphy@arm.com \
--cc=stern@rowland.harvard.edu \
/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).