From: Marc Zyngier <maz@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>, Christoph Hellwig <hch@lst.de>
Cc: Russell King <linux@armlinux.org.uk>,
Arnd Bergmann <arnd@kernel.org>,
Andre Przywara <andre.przywara@arm.com>,
Andrew Lunn <andrew@lunn.ch>,
Gregory Clement <gregory.clement@bootlin.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Alan Stern <stern@rowland.harvard.edu>,
Laurentiu Tudor <laurentiu.tudor@nxp.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Robin Murphy <robin.murphy@arm.com>,
iommu@lists.linux-foundation.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: fully convert arm to use dma-direct
Date: Sat, 23 Apr 2022 11:27:13 +0100 [thread overview]
Message-ID: <e3ff279d8f00fb38ee4e9ecda0e56038@kernel.org> (raw)
In-Reply-To: <CACRpkdbdKBfmXGdyTm3T-MFAK30N-z4KH0k8eD8F7xaYUbDDhA@mail.gmail.com>
On 2022-04-22 22:17, Linus Walleij wrote:
> On Thu, Apr 21, 2022 at 9:42 AM Christoph Hellwig <hch@lst.de> wrote:
>
>> arm is the last platform not using the dma-direct code for directly
>> mapped DMA. With the dmaboune removal from Arnd we can easily switch
>> arm to always use dma-direct now (it already does for LPAE configs
>> and nommu). I'd love to merge this series through the dma-mapping
>> tree
>> as it gives us the opportunity for additional core dma-mapping
>> improvements.
> (...)
>
>> b/arch/arm/mach-footbridge/Kconfig | 1
>> b/arch/arm/mach-footbridge/common.c | 19
>> b/arch/arm/mach-footbridge/include/mach/dma-direct.h | 8
>> b/arch/arm/mach-footbridge/include/mach/memory.h | 4
>
> I think Marc Z has a Netwinder that he can test this on. Marc?
> I have one too, just not much in my office because of parental leave.
I'm about to travel for a week. Can this wait until I'm back?
This is one of the few boxes that isn't hooked up to the PDU,
so I can't operate it remotely.
M.
--
Jazz is not dead. It just smells funny...
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-04-23 10:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 7:41 fully convert arm to use dma-direct Christoph Hellwig
2022-04-21 7:41 ` [PATCH 1/7] ARM: sa1100/assabet: move dmabounce hack to ohci driver Christoph Hellwig
2022-04-21 7:41 ` [PATCH 2/7] ARM: remove dmabounce Christoph Hellwig
2022-04-21 7:48 ` Arnd Bergmann
2022-04-21 7:42 ` [PATCH 3/7] ARM: mark various dma-mapping routines static in dma-mapping.c Christoph Hellwig
2022-04-21 7:49 ` Arnd Bergmann
2022-04-21 7:42 ` [PATCH 4/7] ARM: remove the unused virt_to_dma helper Christoph Hellwig
2022-04-21 8:00 ` Arnd Bergmann
2022-04-21 14:11 ` Christoph Hellwig
2022-04-21 7:42 ` [PATCH 5/7] ARM: use dma_to_phys/phys_to_dma in the dma-mapping code Christoph Hellwig
2022-04-21 8:02 ` Arnd Bergmann
2022-04-21 7:42 ` [PATCH 6/7] ARM: use the common dma_to_phys/phys_to_dma implementation where possible Christoph Hellwig
2022-04-21 8:05 ` Arnd Bergmann
2022-04-21 14:12 ` Christoph Hellwig
2022-04-21 7:42 ` [PATCH 7/7] ARM: use dma-direct unconditionally Christoph Hellwig
2022-04-21 8:09 ` Arnd Bergmann
2022-04-21 8:14 ` fully convert arm to use dma-direct Arnd Bergmann
2022-04-21 10:41 ` Andre Przywara
2022-04-22 21:17 ` Linus Walleij
2022-04-23 10:27 ` Marc Zyngier [this message]
2022-04-23 16:43 ` Christoph Hellwig
2022-05-06 12:06 ` Marc Zyngier
2022-05-09 6:16 ` Christoph Hellwig
2022-05-09 15:44 ` Russell King (Oracle)
2022-05-09 21:51 ` Linus Walleij
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=e3ff279d8f00fb38ee4e9ecda0e56038@kernel.org \
--to=maz@kernel.org \
--cc=andre.przywara@arm.com \
--cc=andrew@lunn.ch \
--cc=arnd@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=gregory.clement@bootlin.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=laurentiu.tudor@nxp.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=m.szyprowski@samsung.com \
--cc=robin.murphy@arm.com \
--cc=sebastian.hesselbarth@gmail.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).