From: Christoph Hellwig <hch@lst.de>
To: Robin Murphy <robin.murphy@arm.com>
Cc: hch@lst.de, m.szyprowski@samsung.com,
iommu@lists.linux-foundation.org,
linux-arm-kernel@lists.infradead.org, linux-ia64@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [RFC PATCH 2/2] dma-mapping: Clean up dma_get_required_mask() hooks
Date: Thu, 05 Jul 2018 19:38:46 +0000 [thread overview]
Message-ID: <20180705193846.GC28905@lst.de> (raw)
In-Reply-To: <08256121f325ceed7f6b88c1a5d3cf949698787d.1530726467.git.robin.murphy@arm.com>
On Wed, Jul 04, 2018 at 06:50:12PM +0100, Robin Murphy wrote:
> As for the other mask-related hooks, standardise the arch override into
> a Kconfig option, and also pull the generic implementation into the DMA
> mapping code rather than having it hide away in the platform bus code.
Heh, I have a somewhat similar patch in my queue. I didn't want it out
because dma_get_required_mask is rather ill defined at the moment and
I wanted to clean that up first. But I guess I could apply this first
and clean up later.
I just fear you might be wanting to add an arm64 user, so I'd really like
to understand why and how.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
To: Robin Murphy <robin.murphy-5wv7dgnIgG8@public.gmane.org>
Cc: linux-ia64-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
hch-jcswGhMUV9g@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [RFC PATCH 2/2] dma-mapping: Clean up dma_get_required_mask() hooks
Date: Thu, 5 Jul 2018 21:38:46 +0200 [thread overview]
Message-ID: <20180705193846.GC28905@lst.de> (raw)
In-Reply-To: <08256121f325ceed7f6b88c1a5d3cf949698787d.1530726467.git.robin.murphy-5wv7dgnIgG8@public.gmane.org>
On Wed, Jul 04, 2018 at 06:50:12PM +0100, Robin Murphy wrote:
> As for the other mask-related hooks, standardise the arch override into
> a Kconfig option, and also pull the generic implementation into the DMA
> mapping code rather than having it hide away in the platform bus code.
Heh, I have a somewhat similar patch in my queue. I didn't want it out
because dma_get_required_mask is rather ill defined at the moment and
I wanted to clean that up first. But I guess I could apply this first
and clean up later.
I just fear you might be wanting to add an arm64 user, so I'd really like
to understand why and how.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Robin Murphy <robin.murphy@arm.com>
Cc: hch@lst.de, m.szyprowski@samsung.com,
iommu@lists.linux-foundation.org,
linux-arm-kernel@lists.infradead.org, linux-ia64@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [RFC PATCH 2/2] dma-mapping: Clean up dma_get_required_mask() hooks
Date: Thu, 5 Jul 2018 21:38:46 +0200 [thread overview]
Message-ID: <20180705193846.GC28905@lst.de> (raw)
In-Reply-To: <08256121f325ceed7f6b88c1a5d3cf949698787d.1530726467.git.robin.murphy@arm.com>
On Wed, Jul 04, 2018 at 06:50:12PM +0100, Robin Murphy wrote:
> As for the other mask-related hooks, standardise the arch override into
> a Kconfig option, and also pull the generic implementation into the DMA
> mapping code rather than having it hide away in the platform bus code.
Heh, I have a somewhat similar patch in my queue. I didn't want it out
because dma_get_required_mask is rather ill defined at the moment and
I wanted to clean that up first. But I guess I could apply this first
and clean up later.
I just fear you might be wanting to add an arm64 user, so I'd really like
to understand why and how.
WARNING: multiple messages have this Message-ID (diff)
From: hch@lst.de (Christoph Hellwig)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 2/2] dma-mapping: Clean up dma_get_required_mask() hooks
Date: Thu, 5 Jul 2018 21:38:46 +0200 [thread overview]
Message-ID: <20180705193846.GC28905@lst.de> (raw)
In-Reply-To: <08256121f325ceed7f6b88c1a5d3cf949698787d.1530726467.git.robin.murphy@arm.com>
On Wed, Jul 04, 2018 at 06:50:12PM +0100, Robin Murphy wrote:
> As for the other mask-related hooks, standardise the arch override into
> a Kconfig option, and also pull the generic implementation into the DMA
> mapping code rather than having it hide away in the platform bus code.
Heh, I have a somewhat similar patch in my queue. I didn't want it out
because dma_get_required_mask is rather ill defined at the moment and
I wanted to clean that up first. But I guess I could apply this first
and clean up later.
I just fear you might be wanting to add an arm64 user, so I'd really like
to understand why and how.
next prev parent reply other threads:[~2018-07-05 19:38 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 17:50 [RFC PATCH 1/2] dma-mapping: Clean up dma_set_*mask() hooks Robin Murphy
2018-07-04 17:50 ` Robin Murphy
2018-07-04 17:50 ` Robin Murphy
2018-07-04 17:50 ` Robin Murphy
2018-07-04 17:50 ` [RFC PATCH 2/2] dma-mapping: Clean up dma_get_required_mask() hooks Robin Murphy
2018-07-04 17:50 ` Robin Murphy
2018-07-04 17:50 ` Robin Murphy
2018-07-04 17:50 ` Robin Murphy
2018-07-05 19:38 ` Christoph Hellwig [this message]
2018-07-05 19:38 ` Christoph Hellwig
2018-07-05 19:38 ` Christoph Hellwig
2018-07-05 19:38 ` Christoph Hellwig
2018-07-06 14:22 ` Robin Murphy
2018-07-06 14:22 ` Robin Murphy
2018-07-06 14:22 ` Robin Murphy
2018-07-06 14:22 ` Robin Murphy
2018-07-10 11:39 ` Christoph Hellwig
2018-07-10 11:39 ` Christoph Hellwig
2018-07-10 11:39 ` Christoph Hellwig
2018-07-10 11:39 ` Christoph Hellwig
2018-07-10 12:29 ` Robin Murphy
2018-07-10 12:29 ` Robin Murphy
2018-07-10 12:29 ` Robin Murphy
2018-07-10 12:29 ` Robin Murphy
2018-07-10 15:08 ` Christoph Hellwig
2018-07-10 15:08 ` Christoph Hellwig
2018-07-10 15:08 ` Christoph Hellwig
2018-07-10 15:08 ` Christoph Hellwig
2018-07-05 19:37 ` [RFC PATCH 1/2] dma-mapping: Clean up dma_set_*mask() hooks Christoph Hellwig
2018-07-05 19:37 ` Christoph Hellwig
2018-07-05 19:37 ` Christoph Hellwig
2018-07-05 19:37 ` Christoph Hellwig
2018-07-06 14:20 ` Robin Murphy
2018-07-06 14:20 ` Robin Murphy
2018-07-06 14:20 ` Robin Murphy
2018-07-06 14:20 ` Robin Murphy
2018-07-08 15:07 ` Christoph Hellwig
2018-07-08 15:07 ` Christoph Hellwig
2018-07-08 15:07 ` Christoph Hellwig
2018-07-08 15:07 ` Christoph Hellwig
2018-07-09 14:53 ` Robin Murphy
2018-07-09 14:53 ` Robin Murphy
2018-07-09 14:53 ` Robin Murphy
2018-07-09 14:53 ` Robin Murphy
2018-07-10 11:44 ` Christoph Hellwig
2018-07-10 11:44 ` Christoph Hellwig
2018-07-10 11:44 ` Christoph Hellwig
2018-07-10 11:44 ` 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=20180705193846.GC28905@lst.de \
--to=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=m.szyprowski@samsung.com \
--cc=robin.murphy@arm.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.