linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Verberk, Bep" <verberk@nortelnetworks.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: mtdcr and mfdcr macros
Date: Wed, 3 Dec 2003 10:25:18 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0312030959380.3107-100000@localhost.localdomain> (raw)


I'd like a sanity check on a change I am considering to
these macros....

I had some difficulty executing these macros
(found in include/asm/processor.h) in a loop, eg:

#define DMA0_BANKS 	4
#define DCRN_DMA0_BASE	0x100
#define DCRN_DMA0_CR(bank)  (DCRN_DMA0_BASE + (8 * (bank)))

		for(i=0;i<DMA0_BANKS;i++){
			dma0_cr = mfdcr(DCRN_DMA0_CR(i));
			CLEARBITS(dma0_cr, DMA0_CR_PCE);
			mtdcr(DCRN_DMA0_CR(i), dma0_cr);
		};


compiling results in the assembler error
/tmp/cca8HPJ4.s:282: Error: undefined symbol `i' in operation

Compiling with the -E to see what the pre-processor is generating
--
for(i=0;i< 4 ;i++) {
     	dma0_cr = ({unsigned int rval;
	asm volatile("mfdcr %0," "(0x100 + (8 * (i)))"
		  : "=r" (rval)); rval;}) ;
        ( dma0_cr  =  dma0_cr  |   0x00000008  ) ;
        asm volatile("mtdcr " "(0x100 + (8 * (i)))" ",%0"
		: : "r" (  dma0_cr )) ;
};

Looking at the definition of mtdcr and mfdcr in processor.h
--
#define mfdcr(rn)       ({unsigned int rval; \
                        asm volatile("mfdcr %0," __stringify(rn) \
                                     : "=r" (rval)); rval;})
#define mtdcr(rn, v)    asm volatile("mtdcr " __stringify(rn) ",%0" \
				: : "r" (v))

I was suspicious that the use of __stringify was buggering up my
index parameter. I made a slight tweak to these macros to take
(rn) as a numeric input param.

#define mfdcr(rn)       ({unsigned int rval; \
                        asm volatile("mfdcr %0, %1" \
                                     : "=r" (rval) \
				     : "n" (rn));  \
				rval;})

#define mtdcr(rn, v)    asm volatile("mtdcr %1 ,%0" \
				: : "r" (v), "n" (rn));


Testing this morning so far seems to indicate the new version is
working for me, but my usage is fairly limited. Am I missing
anything ??

Cheers,

--
Bep Verberk
verberk@nortelnetworks.com

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2003-12-03 15:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-03 15:25 Verberk, Bep [this message]
2003-12-03 17:56 ` mtdcr and mfdcr macros Verberk, Bep
2003-12-03 20:02 ` Eugene Surovegin
2003-12-04 14:03   ` Verberk, Bep

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=Pine.LNX.4.44.0312030959380.3107-100000@localhost.localdomain \
    --to=verberk@nortelnetworks.com \
    --cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).