iommu.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: iommu@lists.linux-foundation.org
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Robin Murphy <robin.murphy@arm.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: dma_get_required_mask tidyups
Date: Wed, 19 Sep 2018 17:01:48 +0200	[thread overview]
Message-ID: <20180919150148.GA29588@lst.de> (raw)
In-Reply-To: <20180910061332.28187-1-hch@lst.de>

Any comments?  I have a a few things piled up that base on this, so
some forward progress would be great.

On Mon, Sep 10, 2018 at 08:13:29AM +0200, Christoph Hellwig wrote:
> Hi all,
> 
> the dma_get_required_mask dma API implementation has always been a little
> odd, in that we by default don't wire it up struct dma_map_ops, but
> instead hard code a default implementation.  powerpc and ia64 override
> this default and either call a method or otherwise duplicate the default.
> 
> This series always enabled the method and just falls back to the previous
> default implementation when it is not available, as well as fixing up
> a few bits in the default implementations.  This already allows removing
> the ia64 override of the implementation, and will also allow to remove
> the powerpc one together with a few additional cleanups in the powerpc
> code, but those will be sent separately with other powerpc DMA API
> patches.  Last but not least the method will allow us to return a more
> sensible value for typical iommu dma_ops eventually, but that is left
> to another series as well.
> _______________________________________________
> iommu mailing list
> iommu@lists.linux-foundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/iommu
---end quoted text---

      parent reply	other threads:[~2018-09-19 15:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-10  6:13 dma_get_required_mask tidyups Christoph Hellwig
2018-09-10  6:13 ` [PATCH 1/3] dma-mapping: make the get_required_mask method available unconditionally Christoph Hellwig
     [not found] ` <20180910061332.28187-1-hch-jcswGhMUV9g@public.gmane.org>
2018-09-10  6:13   ` [PATCH 2/3] dma-mapping: simplify dma_direct get_required_mask Christoph Hellwig
2018-09-10  6:13 ` [PATCH 3/3] dma-mapping: use phys_to_dma in dma_direct_get_required Christoph Hellwig
2018-09-19 15:01 ` 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=20180919150148.GA29588@lst.de \
    --to=hch@lst.de \
    --cc=benh@kernel.crashing.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 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).