From: "Steven Kaiser" <skaiser.uci@gmail.com>
To: "'Markus Klotzbücher'" <mk@creamnet.de>
Cc: linuxppc-embedded@ozlabs.org
Subject: RE: MPC5200b kernel module memory mapping
Date: Sat, 23 Sep 2006 13:46:36 -0700 [thread overview]
Message-ID: <000601c6df51$5d6edf10$6e4ec880@volt> (raw)
In-Reply-To: <87slilxf92.fsf@creamnet.de>
Markus:
> > sure I am setting up the LocalBus chip select registers ok.
>
> I would guess this is not the case. What kind of device is this?
It is a Freescale MPC5200b:
http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=MPC5200B
You are correct. I was so concerned about the linux driver stuff (
request_region(), ioremap(), etc ), that I was locked into endless studies
on that and see now I clearly overlooked some simple chip setting up. Doh!
Thanks for reorienting my focus--
int init_module(void) { ...
// reserve a page of memory for our hardware /proc/iomem
if ( check_region(MALab_MM_START,MALab_MM_SIZE) ) {
printk (KERN_ALERT "LED init_module: memory already in
use\n");
return -EBUSY;
}
request_region(MALab_MM_START,MALab_MM_SIZE,LED_DEVICE_NAME);
// enable LocalBus chip select CS2 to hit on our address range
*(volatile u32 *)MPC5xxx_MM_IPBI &= ~0x00040000;
*(volatile u16 *)(MPC5xxx_MM_CS2_START + 2) = MALab_MM_START >> 16;
*(volatile u16 *)(MPC5xxx_MM_CS2_STOP + 2) = MALab_MM_END >> 16;
*(volatile u32 *)MPC5xxx_MM_IPBI |= 0x00040000;
// LocalBus Chip Select 2,3 Configuration Register
*(volatile u32 *)(MPC5xxx_MBAR + 0x0308) = 0x03031110;
*(volatile u32 *)(MPC5xxx_MBAR + 0x030c) = 0x03031110;
// LocalBus Chip Select Control Register
*(volatile u32 *)(MPC5xxx_MBAR + 0x0318) |= 0x01000000;
// map our physical address into kernal virtual address space
ioaddr = ioremap(MALab_MM_START,MALab_MM_SIZE);
printk(KERN_ALERT "ioaddr: 0x%08x\n", (u32)ioaddr);
and later, any of these calls work:
next prev parent reply other threads:[~2006-09-23 20:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-21 0:09 MPC5200b kernel module memory mapping Steven Kaiser
2006-09-21 8:47 ` sudheer
2006-09-21 18:10 ` Markus Klotzbücher
2006-09-23 20:46 ` Steven Kaiser [this message]
2006-09-23 20:55 ` Steven Kaiser
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='000601c6df51$5d6edf10$6e4ec880@volt' \
--to=skaiser.uci@gmail.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=mk@creamnet.de \
/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).