linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: david.hagood@gmail.com
To: linuxppc-dev@ozlabs.org
Subject: MPC8641D PEX: programming OWBAR in Endpoint mode?
Date: Wed, 22 Sep 2010 10:55:38 -0500	[thread overview]
Message-ID: <08f8439b89ad5771221aaba1cee86fc4.squirrel@localhost> (raw)

I am trying to get the PCIe interfaces of a Freescale MPC8641D working in
endpoint mode (i.e. as a PCI device rather than a PCI root complex host).

I can get the device to show up on the host's PCI bus, I can program the
inbound ATMUs such that the BARS are updated when the host (re-)scans
them, but I cannot for the life of me get the PPC's Outbound ATMUS to
work.

When I attempt to program them, I can program ALL the registers EXCEPT the
OWBAR - which steadfastly remains 0 no matter what I write to it.

As a result, when I attempt to bus master out from the PPC to the PCIe
address spaces via the outbound ATMUs, I get a bus fault on the PPC as
there is no device at the address I am accessing.

I've double-checked the LAWs to make sure the PEX is mapped into local
space, I've put the OWBAR in that address space, I've tried different
outbound ATMUs, and NOTHING works. Not ATMU0, not ATMU1, etc.

I've been trying to work with our Freescale rep, but I am getting nowhere
on that front.

Does anybody have any suggestions on what I might be doing wrong? I mean,
it looks like it should be a simple out_be32(addr_of_OWBAR,value), just
like all the other accesses to the ATMU registers that seem to be working
(as in, I read back what I wrote).

             reply	other threads:[~2010-09-22 15:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-22 15:55 david.hagood [this message]
2010-09-23  3:21 ` MPC8641D PEX: programming OWBAR in Endpoint mode? Chen, Tiejun
2010-09-23 11:11   ` David Hagood
2010-09-23 14:10     ` Chen, Tiejun
2010-09-23 14:44       ` david.hagood
2010-09-24  5:09         ` Chen, Tiejun
2010-09-24 10:50           ` David Hagood
2010-09-25  9:46             ` tiejun.chen
2010-09-25 11:51               ` David Hagood
2010-09-26 10:14                 ` tiejun.chen

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=08f8439b89ad5771221aaba1cee86fc4.squirrel@localhost \
    --to=david.hagood@gmail.com \
    --cc=linuxppc-dev@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).