LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Zhang Wei" <Wei.Zhang@freescale.com>
To: "Olof Johansson" <olof@lixom.net>
Cc: <dan.j.williams@intel.com>, <sfr@canb.auug.org.au>,
	<linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] Fix fsldma.c warning messages when it's compiled underPPC64.
Date: Wed, 12 Mar 2008 10:10:46 +0800	[thread overview]
Message-ID: <ABF87B0B6A38C0458E319AC973ED68AECE526A@zch01exm26.fsl.freescale.net> (raw)
In-Reply-To: <20080311142247.GA18915@lixom.net>

Hi, 

> -----Original Message-----
> From: Olof Johansson [mailto:olof@lixom.net] 
> 
> On Mon, Mar 10, 2008 at 06:47:25PM +0800, Zhang Wei wrote:
> > There are warning messages reported by Stephen Rothwell with
> > ARCH=powerpc allmodconfig build:
> > 
> > drivers/dma/fsldma.c: In function 'fsl_dma_prep_memcpy':
> > drivers/dma/fsldma.c:439: warning: comparison of distinct 
> pointer types
> > lacks a cast
> > drivers/dma/fsldma.c: In function 'fsl_chan_xfer_ld_queue':
> > drivers/dma/fsldma.c:584: warning: format '%016llx' expects 
> type 'long long
> > unsigned int', but argument 4 has type 'dma_addr_t'
> > drivers/dma/fsldma.c: In function 'fsl_dma_chan_do_interrupt':
> > drivers/dma/fsldma.c:668: warning: format '%x' expects type 
> 'unsigned int',
> > but argument 5 has type 'dma_addr_t'
> > drivers/dma/fsldma.c:684: warning: format '%016llx' expects 
> type 'long long
> > unsigned int', but argument 4 has type 'dma_addr_t'
> > drivers/dma/fsldma.c:684: warning: format '%016llx' expects 
> type 'long long
> > unsigned int', but argument 5 has type 'dma_addr_t'
> > drivers/dma/fsldma.c:701: warning: format '%02x' expects 
> type 'unsigned
> > int', but argument 4 has type 'dma_addr_t'
> > drivers/dma/fsldma.c: In function 'fsl_dma_self_test':
> > drivers/dma/fsldma.c:840: warning: format '%d' expects type 
> 'int', but
> > argument 5 has type 'size_t'
> > drivers/dma/fsldma.c: In function 'of_fsl_dma_probe':
> > drivers/dma/fsldma.c:1010: warning: format '%08x' expects 
> type 'unsigned
> > int', but argument 5 has type 'resource_size_t'
> > 
> > This patch fixed the above warning messages.
> > 
> > Signed-off-by: Zhang Wei <wei.zhang@freescale.com>
> > ---
> >  drivers/dma/fsldma.c |   29 ++++++++++++++++-------------
> >  1 files changed, 16 insertions(+), 13 deletions(-)
> > 
> > diff --git a/drivers/dma/fsldma.c b/drivers/dma/fsldma.c
> > index cc9a681..5dfedf3 100644
> > --- a/drivers/dma/fsldma.c
> > +++ b/drivers/dma/fsldma.c
> > @@ -57,12 +57,12 @@ static void dma_init(struct 
> fsl_dma_chan *fsl_chan)
> >  
> >  }
> >  
> > -static void set_sr(struct fsl_dma_chan *fsl_chan, dma_addr_t val)
> > +static void set_sr(struct fsl_dma_chan *fsl_chan, u32 val)
> 
> Why? dma_addr_t is the right type to use here.

The reason is the val will be assigned to SR register, and SR register
 is a 32-bit only register.

> > @@ -581,8 +581,8 @@ static void 
> fsl_chan_xfer_ld_queue(struct fsl_dma_chan *fsl_chan)
> >  	if (ld_node != &fsl_chan->ld_queue) {
> >  		/* Get the ld start address from ld_queue */
> >  		next_dest_addr = to_fsl_desc(ld_node)->async_tx.phys;
> > -		dev_dbg(fsl_chan->dev, "xfer LDs staring from 
> 0x%016llx\n",
> > -				(u64)next_dest_addr);
> > +		dev_dbg(fsl_chan->dev, "xfer LDs staring from %p\n",
> > +				(void *)next_dest_addr);
> 
> If anything you should cast to unsigned long and print as %lx.
> next_dest_addr is not a pointer, it's a bus/dma address.
> 
> Same for all the other changes in this file (dma_addr_t -> u32 doesn't
> seem right, same for the %llx -> %p changes).
> 

Here's cast is only for print out message. The type point can
 adapt the address width automatically in 32-bit and 64-bit kernel.

Thanks!
Wei.

  reply	other threads:[~2008-03-12  2:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-10 10:47 [PATCH] Fix fsldma.c warning messages when it's compiled under PPC64 Zhang Wei
2008-03-10 19:09 ` Dan Williams
2008-03-11 14:22 ` Olof Johansson
2008-03-12  2:10   ` Zhang Wei [this message]
2008-03-12 16:29     ` [PATCH] Fix fsldma.c warning messages when it's compiled underPPC64 Dan Williams
2008-03-13  6:52       ` Zhang Wei
2008-03-18 18:23         ` Scott Wood
2008-03-19  1:52           ` Zhang Wei

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=ABF87B0B6A38C0458E319AC973ED68AECE526A@zch01exm26.fsl.freescale.net \
    --to=wei.zhang@freescale.com \
    --cc=dan.j.williams@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=sfr@canb.auug.org.au \
    --subject='RE: [PATCH] Fix fsldma.c warning messages when it'\''s compiled underPPC64.' \
    /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

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).