Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: Alchemy DMA and GFP_DMA
Date: Sun, 26 Aug 2007 18:48:41 +0400	[thread overview]
Message-ID: <46D192C9.7070208@ru.mvista.com> (raw)
In-Reply-To: <20070816110501.GA5701@linux-mips.org>

Hello.

Ralf Baechle wrote:

> arch/mips/au1000/common/dbdma.c uses GFP_DMA in two places and I think
> both instances are uncessary.  Could some alchmist confirm that both are
> unnecessary?

> Thanks,

>   Ralf

> Signed-off-by: Ralf Baechle <ralf@linux-mips.org>

> diff --git a/arch/mips/au1000/common/dbdma.c b/arch/mips/au1000/common/dbdma.c
> index 626de44..708b83b 100644
> --- a/arch/mips/au1000/common/dbdma.c
> +++ b/arch/mips/au1000/common/dbdma.c
> @@ -397,7 +397,7 @@ au1xxx_dbdma_ring_alloc(u32 chanid, int entries)
>  	 * slabs of memory.
>  	 */
>  	desc_base = (u32)kmalloc(entries * sizeof(au1x_ddma_desc_t),
> -			GFP_KERNEL|GFP_DMA);
> +			GFP_KERNEL);
>  	if (desc_base == 0)
>  		return 0;
>  
> @@ -408,7 +408,7 @@ au1xxx_dbdma_ring_alloc(u32 chanid, int entries)
>  		kfree((const void *)desc_base);
>  		i = entries * sizeof(au1x_ddma_desc_t);
>  		i += (sizeof(au1x_ddma_desc_t) - 1);
> -		if ((desc_base = (u32)kmalloc(i, GFP_KERNEL|GFP_DMA)) == 0)
> +		if ((desc_base = (u32)kmalloc(i, GFP_KERNEL)) == 0)
>  			return 0;
>  
>  		desc_base = ALIGN_ADDR(desc_base, sizeof(au1x_ddma_desc_t));

     Those are probably still necessary because the DBDMA descriptors itselves 
(not the data they address) must have 32-bit addresses.

WBR, Sergei

  reply	other threads:[~2007-08-26 14:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-16 11:05 Alchemy DMA and GFP_DMA Ralf Baechle
2007-08-26 14:48 ` Sergei Shtylyov [this message]
2007-08-26 15:36   ` Ralf Baechle
  -- strict thread matches above, loose matches on Subject: below --
2007-08-17 15:29 bo y

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=46D192C9.7070208@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.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