From: Gabriel Paubert <paubert@iram.es>
To: Nicolas Lavocat <nicolas.lavocat@fr.thalesgroup.com>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: freeze when reading a PCI bridge register
Date: Wed, 22 Apr 2009 13:03:27 +0200 [thread overview]
Message-ID: <20090422110327.GA9997@iram.es> (raw)
In-Reply-To: <49EECF8D.9000808@fr.thalesgroup.com>
On Wed, Apr 22, 2009 at 10:04:29AM +0200, Nicolas Lavocat wrote:
> Hi everybody!
>
> I' am trying to configure a PCI bridge on a private board, with a
> powerpc . In a first time, I tried to get informations about PCI
> devices, in order to be sure that my read and write methods work (
> using 2 configuration registers, like on an x86 architecture.) . 2
> configuration registers are used, for example we write an encoded
> address (it is a request to a PCI device) in the first and the answer of
> the PCI device can be read in the second register (it is a configuration
> cycle)
> Firstly, I did it by JTAG: it works. Then, under uboot, it is ok.
JTAG is probably a completely different hardware path, so it
does not really count. uboot testing is ok.
>
> For example, the code used under u-boot:
>
> volatile u32* addr;
> u32 vendor_device_ID;
>
> puts("PCI1 reading PCI VENDOR and DEVICE ID\n");
> addr=CFG_ADDR_PCI1;
> *addr=0x80007800;
>
> addr= CFG_DATA_PCI1;
> vendor_device_ID= *addr;
> printf("PCI1: PCI1_VENDOR_DEVICE_ID= %08x \n" ,vendor_device_ID);
2 possibilities:
- your I/O is not marked uncacheable (should be with ioremap)
- the PPC is reordering and issuing the read before the write,
you should use accessors. A simple test is inserting
an asm volatile("eieio") before the read.
About your other mails, please avoid HTML mail.
Gabriel
next prev parent reply other threads:[~2009-04-22 11:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 8:04 freeze when reading a PCI bridge register Nicolas Lavocat
2009-04-22 8:30 ` Liu Dave-R63238
2009-04-22 8:31 ` Nicolas Lavocat
2009-04-22 8:33 ` Liu Dave-R63238
2009-04-22 9:10 ` Nicolas Lavocat
2009-04-22 9:21 ` tiejun.chen
2009-04-22 9:26 ` Nicolas Lavocat
2009-04-22 9:45 ` tiejun.chen
2009-04-22 11:03 ` Gabriel Paubert [this message]
2009-04-22 12:28 ` Nicolas Lavocat
2009-04-22 14:56 ` Nicolas Lavocat
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=20090422110327.GA9997@iram.es \
--to=paubert@iram.es \
--cc=linuxppc-dev@ozlabs.org \
--cc=nicolas.lavocat@fr.thalesgroup.com \
/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).