From: Johnny Hung <johnny.hacking@gmail.com>
To: linux-embedded@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
kernelnewbies@nl.linux.org, scottwood@freescale.com
Subject: PCI device support in Open Firmware (device tree syntax)
Date: Mon, 29 Jun 2009 23:58:22 +0800 [thread overview]
Message-ID: <cb9ecdfa0906290858x125b8149na037f33258c21426@mail.gmail.com> (raw)
Hi all,
I am working in customized Freescale MPC8313 board. There are two
PCI devices (Broadcom Switch) in PCI bus.
Each PCI device has its configuration space. It contains
vendor/product ID (RO)..., and important information, likes BARs
(Base Address), INT line and IRQ(RW). These resources (BAR, INT, IRQ)
is assigned from BIOS in x86 arch.
My problem is how to assign PCI device resources in device tree. I
can't find exist dts file as an example. I have read the
http://www.power.org/resources/downloads/Power_ePAPR_APPROVED_v1.0.pdf
file. It's described detailed about device tree
except PCI device. So, anyone give me a hint or sany tuff is appreciated.
I think Linux Kernel parses device tree and get the PCI device
resources information then write into PCI configuration space.
So PCI device driver do pci_register_driver (get resource) and do
itself probe for PCI device. Is it right? CMIIAW
BRs, H. Johnny
next reply other threads:[~2009-06-29 15:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 15:58 Johnny Hung [this message]
2009-06-29 16:51 ` PCI device support in Open Firmware (device tree syntax) Scott Wood
2009-06-30 1:36 ` Johnny Hung
[not found] ` <2ea1731b0906292329t30cdc9a6q1fc36dc2273a2931@mail.gmail.com>
2009-06-30 7:33 ` Johnny Hung
2009-07-01 22:15 ` Benjamin Herrenschmidt
2009-06-30 15:32 ` Scott Wood
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=cb9ecdfa0906290858x125b8149na037f33258c21426@mail.gmail.com \
--to=johnny.hacking@gmail.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=scottwood@freescale.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).