linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Shinji Watanabe" <watashin@mvision.co.jp>
To: <linuxppc-embedded@ozlabs.org>
Subject: How to access MPC8555 DMA register ?
Date: Thu, 15 Feb 2007 19:16:27 +0900	[thread overview]
Message-ID: <013b01c750ea$5e8544b0$1601a8c0@wata> (raw)

I don't know how to bind the driver.

I maked driver of pci device type for MPC8555 as Log.A.

/var/log/message log is Log.B.

When I called platform_get_resource,
I can't get validate value.

Why ?

please help me!

///////////////////////// log.A

#define VENDORID_MVPPC 0x1057
#define DEVICEID_MVPPC 0x000A

static struct pci_device_id ids[] = {
 { PCI_DEVICE(VENDORID_MVPPC, DEVICEID_MVPPC), },
 { 0, }
};

MODULE_DEVICE_TABLE(pci, ids);

static struct pci_driver pci_driver = {
 .name = PCI_DEVICE_NAME, 
 ...
 .id_table = ids,
 .probe = probe,
};


static int probe(struct pci_dev *dev, const struct pci_device_id *id)
{
 struct resource *res;
 ...
 ...
 struct platform_device *pdev = to_platform_device(&dev->dev);
 ..
 ..
 pci_enable_device(dev);
 ..
 ..
 res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
  dprintk("res0 %p\n", 
   res
   );
 res = platform_get_resource(pdev, IORESOURCE_MEM, 1);
 dprintk("res1 %p\n", 
   res
   );
 res = platform_get_resource(pdev, IORESOURCE_MEM, 2);
 dprintk("res2 %p\n", 
   res
   );
 ...
 ...
}


///////////////////////// log.b
Feb 10 11:34:23 mpc8555cds user.debug kernel: res0 00000000
Feb 10 11:34:23 mpc8555cds user.debug kernel: res1 00000000
Feb 10 11:34:23 mpc8555cds user.debug kernel: res2 00000000


Regars,

shinji

             reply	other threads:[~2007-02-15 10:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-15 10:16 Shinji Watanabe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-02-06  8:44 How to access MPC8555 DMA register ? Shinji Watanabe
2007-02-06 16:36 ` Kumar Gala

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='013b01c750ea$5e8544b0$1601a8c0@wata' \
    --to=watashin@mvision.co.jp \
    --cc=linuxppc-embedded@ozlabs.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).