All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: vinod.koul@intel.com, linux-renesas-soc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, dmaengine@vger.kernel.org,
	iommu@lists.linux-foundation.org, hch@infradead.org,
	linux-arch@vger.kernel.org, geert+renesas@glider.be,
	arnd@arndb.de, linus.walleij@linaro.org,
	laurent.pinchart@ideasonboard.com, dan.j.williams@intel.com
Subject: Re: [PATCHv6 3/8] dma-mapping: add dma_{map,unmap}_resource
Date: Thu, 19 May 2016 10:22:48 -0400	[thread overview]
Message-ID: <20160519142248.GB21691@localhost.localdomain> (raw)
In-Reply-To: <20160519112926.GO29375@bigcity.dyn.berto.se>

On Thu, May 19, 2016 at 01:29:26PM +0200, Niklas Söderlund wrote:
> Hi Konrad,
> 
> Thanks for your feedback.
> 
> On 2016-05-17 10:54:45 -0400, Konrad Rzeszutek Wilk wrote:
> > >  
> > > -In some circumstances dma_map_single() and dma_map_page() will fail to create
> > > -a mapping. A driver can check for these errors by testing the returned
> > > -DMA address with dma_mapping_error(). A non-zero return value means the mapping
> > > -could not be created and the driver should take appropriate action (e.g.
> > > -reduce current DMA mapping usage or delay and try again later).
> > > +In some circumstances dma_map_single(), dma_map_page() and dma_map_resource()
> > > +will fail to create a mapping. A driver can check for these errors by testing
> > > +the returned DMA address with dma_mapping_error(). A non-zero return value
> > > +means the mapping could not be created and the driver should take appropriate
> > > +action (e.g. reduce current DMA mapping usage or delay and try again later).
> > 
> > This looks like it belongs to another patch?
> 
> No it is correct (at least intended to be in this patch). All it really 
> do is inject dma_map_resource() (which is added in this patch) as one of 
> the calls which return dma_addr_t should be checked for error using 
> dma_mapping_error().  But yes the change effect all lines in the 
> paragraph due to line wrapping.
> 
> Hum or maybe I'm misunderstanding your question.

I totally missed the 'dma_map_resource' in there and just read
'dma_mapping_error'!

<sigh> Thanks.
> 
> -- 
> Regards,
> Niklas Söderlund

WARNING: multiple messages have this Message-ID (diff)
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: vinod.koul@intel.com, linux-renesas-soc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, dmaengine@vger.kernel.org,
	iommu@lists.linux-foundation.org, hch@infradead.org,
	linux-arch@vger.kernel.org, geert+renesas@glider.be,
	arnd@arndb.de, linus.walleij@linaro.org,
	laurent.pinchart@ideasonboard.com, dan.j.williams@intel.com
Subject: Re: [PATCHv6 3/8] dma-mapping: add dma_{map,unmap}_resource
Date: Thu, 19 May 2016 10:22:48 -0400	[thread overview]
Message-ID: <20160519142248.GB21691@localhost.localdomain> (raw)
In-Reply-To: <20160519112926.GO29375@bigcity.dyn.berto.se>

On Thu, May 19, 2016 at 01:29:26PM +0200, Niklas S�derlund wrote:
> Hi Konrad,
> 
> Thanks for your feedback.
> 
> On 2016-05-17 10:54:45 -0400, Konrad Rzeszutek Wilk wrote:
> > >  
> > > -In some circumstances dma_map_single() and dma_map_page() will fail to create
> > > -a mapping. A driver can check for these errors by testing the returned
> > > -DMA address with dma_mapping_error(). A non-zero return value means the mapping
> > > -could not be created and the driver should take appropriate action (e.g.
> > > -reduce current DMA mapping usage or delay and try again later).
> > > +In some circumstances dma_map_single(), dma_map_page() and dma_map_resource()
> > > +will fail to create a mapping. A driver can check for these errors by testing
> > > +the returned DMA address with dma_mapping_error(). A non-zero return value
> > > +means the mapping could not be created and the driver should take appropriate
> > > +action (e.g. reduce current DMA mapping usage or delay and try again later).
> > 
> > This looks like it belongs to another patch?
> 
> No it is correct (at least intended to be in this patch). All it really 
> do is inject dma_map_resource() (which is added in this patch) as one of 
> the calls which return dma_addr_t should be checked for error using 
> dma_mapping_error().  But yes the change effect all lines in the 
> paragraph due to line wrapping.
> 
> Hum or maybe I'm misunderstanding your question.

I totally missed the 'dma_map_resource' in there and just read
'dma_mapping_error'!

<sigh> Thanks.
> 
> -- 
> Regards,
> Niklas S�derlund

WARNING: multiple messages have this Message-ID (diff)
From: konrad.wilk@oracle.com (Konrad Rzeszutek Wilk)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv6 3/8] dma-mapping: add dma_{map,unmap}_resource
Date: Thu, 19 May 2016 10:22:48 -0400	[thread overview]
Message-ID: <20160519142248.GB21691@localhost.localdomain> (raw)
In-Reply-To: <20160519112926.GO29375@bigcity.dyn.berto.se>

On Thu, May 19, 2016 at 01:29:26PM +0200, Niklas S?derlund wrote:
> Hi Konrad,
> 
> Thanks for your feedback.
> 
> On 2016-05-17 10:54:45 -0400, Konrad Rzeszutek Wilk wrote:
> > >  
> > > -In some circumstances dma_map_single() and dma_map_page() will fail to create
> > > -a mapping. A driver can check for these errors by testing the returned
> > > -DMA address with dma_mapping_error(). A non-zero return value means the mapping
> > > -could not be created and the driver should take appropriate action (e.g.
> > > -reduce current DMA mapping usage or delay and try again later).
> > > +In some circumstances dma_map_single(), dma_map_page() and dma_map_resource()
> > > +will fail to create a mapping. A driver can check for these errors by testing
> > > +the returned DMA address with dma_mapping_error(). A non-zero return value
> > > +means the mapping could not be created and the driver should take appropriate
> > > +action (e.g. reduce current DMA mapping usage or delay and try again later).
> > 
> > This looks like it belongs to another patch?
> 
> No it is correct (at least intended to be in this patch). All it really 
> do is inject dma_map_resource() (which is added in this patch) as one of 
> the calls which return dma_addr_t should be checked for error using 
> dma_mapping_error().  But yes the change effect all lines in the 
> paragraph due to line wrapping.
> 
> Hum or maybe I'm misunderstanding your question.

I totally missed the 'dma_map_resource' in there and just read
'dma_mapping_error'!

<sigh> Thanks.
> 
> -- 
> Regards,
> Niklas S?derlund

  reply	other threads:[~2016-05-19 14:24 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-09 16:43 [PATCHv6 0/8] dmaengine: rcar-dmac: add iommu support for slave transfers Niklas Söderlund
2016-05-09 16:43 ` Niklas Söderlund
2016-05-09 16:43 ` Niklas Söderlund
2016-05-09 16:44 ` [PATCHv6 1/8] dma-mapping: add {map,unmap}_resource to dma_map_ops Niklas Söderlund
2016-05-09 16:44   ` Niklas Söderlund
2016-05-09 16:44   ` Niklas Söderlund
2016-05-09 16:44 ` [PATCHv6 2/8] dma-debug: add support for resource mappings Niklas Söderlund
2016-05-09 16:44   ` Niklas Söderlund
2016-05-09 16:44   ` Niklas Söderlund
2016-05-17 14:50   ` Konrad Rzeszutek Wilk
2016-05-17 14:50     ` Konrad Rzeszutek Wilk
2016-05-17 14:50     ` Konrad Rzeszutek Wilk
2016-05-19 11:21     ` Niklas Söderlund
2016-05-19 11:21       ` Niklas Söderlund
2016-05-19 11:21       ` Niklas Söderlund
2016-05-19 11:42       ` Robin Murphy
2016-05-19 11:42         ` Robin Murphy
2016-05-19 11:42         ` Robin Murphy
2016-05-09 16:44 ` [PATCHv6 3/8] dma-mapping: add dma_{map,unmap}_resource Niklas Söderlund
2016-05-09 16:44   ` Niklas Söderlund
2016-05-17 14:54   ` Konrad Rzeszutek Wilk
2016-05-17 14:54     ` Konrad Rzeszutek Wilk
2016-05-17 14:54     ` Konrad Rzeszutek Wilk
2016-05-19 11:29     ` Niklas Söderlund
2016-05-19 11:29       ` Niklas Söderlund
2016-05-19 11:29       ` Niklas Söderlund
2016-05-19 14:22       ` Konrad Rzeszutek Wilk [this message]
2016-05-19 14:22         ` Konrad Rzeszutek Wilk
2016-05-19 14:22         ` Konrad Rzeszutek Wilk
2016-05-09 16:44 ` [PATCHv6 4/8] arm: dma-mapping: add {map,unmap}_resource for iommu ops Niklas Söderlund
2016-05-09 16:44   ` [PATCHv6 4/8] arm: dma-mapping: add {map, unmap}_resource " Niklas Söderlund
2016-05-09 16:44   ` Niklas Söderlund
2016-05-09 16:44 ` [PATCHv6 5/8] dmaengine: rcar-dmac: group slave configuration Niklas Söderlund
2016-05-09 16:44   ` Niklas Söderlund
2016-05-09 16:44   ` Niklas Söderlund
2016-05-09 16:44 ` [PATCHv6 6/8] dmaengine: rcar-dmac: add iommu support for slave transfers Niklas Söderlund
2016-05-09 16:44   ` Niklas Söderlund
2016-05-09 16:44   ` Niklas Söderlund
2016-05-09 16:44 ` [PATCHv6 7/8] ARM: dts: r8a7790: add iommus to dmac0 and dmac1 Niklas Söderlund
2016-05-09 16:44   ` Niklas Söderlund
2016-05-09 16:44   ` Niklas Söderlund
2016-05-09 16:44 ` [PATCHv6 8/8] ARM: dts: r8a7791: " Niklas Söderlund
2016-05-09 16:44   ` Niklas Söderlund
2016-05-09 16:44   ` Niklas Söderlund

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=20160519142248.GB21691@localhost.localdomain \
    --to=konrad.wilk@oracle.com \
    --cc=arnd@arndb.de \
    --cc=dan.j.williams@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=hch@infradead.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=vinod.koul@intel.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.