mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hans-Christian Egtvedt <egtvedt@samfundet.no>
To: Akinobu Mita <akinobu.mita@gmail.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	Haavard Skinnemoen <hskinnemoen@gmail.com>,
	linux-arch@vger.kernel.org
Subject: Re: [PATCH v2 07/10] avr32: use for_each_sg()
Date: Mon, 4 May 2015 08:15:13 +0200	[thread overview]
Message-ID: <20150504061513.GA25444@samfundet.no> (raw)
In-Reply-To: <1430488603-11055-7-git-send-email-akinobu.mita@gmail.com>

Around Fri 01 May 2015 22:56:40 +0900 or thereabout, Akinobu Mita wrote:
> This replaces the plain loop over the sglist array with for_each_sg()
> macro which consists of sg_next() function calls.  Since avr32 doesn't
> select ARCH_HAS_SG_CHAIN, it is not necessary to use for_each_sg() in
> order to loop over each sg element.  But this can help find problems
> with drivers that do not properly initialize their sg tables when
> CONFIG_DEBUG_SG is enabled.

Nice

> Signed-off-by: Akinobu Mita <akinobu.mita@gmail.com>
> Cc: Haavard Skinnemoen <hskinnemoen@gmail.com>
> Cc: Hans-Christian Egtvedt <egtvedt@samfundet.no>
> Cc: linux-arch@vger.kernel.org

Acked-by: Hans-Christian Egtvedt <egtvedt@samfundet.no>

> ---
> * New patch from v2
> 
>  arch/avr32/include/asm/dma-mapping.h | 19 ++++++++++---------
>  1 file changed, 10 insertions(+), 9 deletions(-)
> 
> diff --git a/arch/avr32/include/asm/dma-mapping.h b/arch/avr32/include/asm/dma-mapping.h
> index b3d18f9..ae7ac92 100644
> --- a/arch/avr32/include/asm/dma-mapping.h
> +++ b/arch/avr32/include/asm/dma-mapping.h
> @@ -209,17 +209,18 @@ dma_unmap_page(struct device *dev, dma_addr_t dma_address, size_t size,
>   * the same here.
>   */
>  static inline int
> -dma_map_sg(struct device *dev, struct scatterlist *sg, int nents,
> +dma_map_sg(struct device *dev, struct scatterlist *sglist, int nents,
>  	   enum dma_data_direction direction)
>  {
>  	int i;
> +	struct scatterlist *sg;
>  
> -	for (i = 0; i < nents; i++) {
> +	for_each_sg(sglist, sg, nents, i) {
>  		char *virt;
>  
> -		sg[i].dma_address = page_to_bus(sg_page(&sg[i])) + sg[i].offset;
> -		virt = sg_virt(&sg[i]);
> -		dma_cache_sync(dev, virt, sg[i].length, direction);
> +		sg->dma_address = page_to_bus(sg_page(sg)) + sg->offset;
> +		virt = sg_virt(sg);
> +		dma_cache_sync(dev, virt, sg->length, direction);
>  	}
>  
>  	return nents;
> @@ -321,14 +322,14 @@ dma_sync_sg_for_cpu(struct device *dev, struct scatterlist *sg,
>  }
>  
>  static inline void
> -dma_sync_sg_for_device(struct device *dev, struct scatterlist *sg,
> +dma_sync_sg_for_device(struct device *dev, struct scatterlist *sglist,
>  		       int nents, enum dma_data_direction direction)
>  {
>  	int i;
> +	struct scatterlist *sg;
>  
> -	for (i = 0; i < nents; i++) {
> -		dma_cache_sync(dev, sg_virt(&sg[i]), sg[i].length, direction);
> -	}
> +	for_each_sg(sglist, sg, nents, i)
> +		dma_cache_sync(dev, sg_virt(sg), sg->length, direction);
>  }
>  
>  /* Now for the API extensions over the pci_ one */
-- 
mvh
Hans-Christian Egtvedt

  reply	other threads:[~2015-05-04  6:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-01 13:56 [PATCH v2 01/10] m68k: " Akinobu Mita
2015-05-01 13:56 ` [PATCH v2 02/10] arc: " Akinobu Mita
2015-05-01 13:56 ` [PATCH v2 03/10] metag: " Akinobu Mita
2015-05-01 13:56 ` [PATCH v2 04/10] xtensa: " Akinobu Mita
2015-05-01 13:56 ` [PATCH v2 05/10] mips: " Akinobu Mita
2015-05-01 13:56 ` [PATCH v2 06/10] frv: " Akinobu Mita
2015-05-01 13:56 ` [PATCH v2 07/10] avr32: " Akinobu Mita
2015-05-04  6:15   ` Hans-Christian Egtvedt [this message]
2015-05-01 13:56 ` [PATCH v2 08/10] powerpc: " Akinobu Mita
2015-05-01 13:56 ` [PATCH v2 09/10] sparc: " Akinobu Mita
2015-05-01 13:56 ` [PATCH v2 10/10] parisc: " Akinobu Mita
2015-05-04  9:04 ` [PATCH v2 01/10] m68k: " Geert Uytterhoeven

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=20150504061513.GA25444@samfundet.no \
    --to=egtvedt@samfundet.no \
    --cc=akinobu.mita@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=hskinnemoen@gmail.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®