From: Fredrik Noring <noring@nocrew.org>
To: Robin Murphy <robin.murphy@arm.com>
Cc: laurentiu.tudor@nxp.com, hch@lst.de, stern@rowland.harvard.edu,
gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
marex@denx.de, JuergenUrban@gmx.de, leoyang.li@nxp.com,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v2 0/3] prerequisites for device reserved local mem rework
Date: Tue, 14 May 2019 20:29:31 +0200 [thread overview]
Message-ID: <20190514182931.GA2559@sx9> (raw)
In-Reply-To: <9d34015d-c219-179b-3141-4b0de3530ac3@arm.com>
Thanks Robin!
> > For HCs that have local memory, replace the current DMA API usage
> > with a genalloc generic allocator to manage the mappings for these
> > devices.
> > This is in preparation for dropping the existing "coherent" dma
> > mem declaration APIs. Current implementation was relying on a short
> > circuit in the DMA API that in the end, was acting as an allocator
> > for these type of devices.
> >
> > Only compiled tested, so any volunteers willing to test are most welcome.
>
> I recall an out-of-tree PlayStation 2 OHCI driver being another
> HCD_LOCAL_MEM user - if Fredrik and Juergen are still active on that,
> hopefully they might be able to comment on whether this approach can
> work for them too. Patchwork link just in case:
> https://patchwork.kernel.org/project/linux-usb/list/?series=117433
True. In fact I'm preparing a patch submission for this PS2 OHCI driver,
along with about a hundred other patches (unrelated to the USB subsystem).
Hopefully in a few weeks. My patches are currently on top of v5.0. What
branch/version is recommended to try this DMA update?
Here is the v5.0.11 PS2 OHCI driver, for reference:
https://github.com/frno7/linux/blob/ps2-v5.0.11/drivers/usb/host/ohci-ps2.c
Fredrik
next prev parent reply other threads:[~2019-05-14 18:39 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
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 [this message]
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=20190514182931.GA2559@sx9 \
--to=noring@nocrew.org \
--cc=JuergenUrban@gmx.de \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--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).