From: Daniel Hellstrom <daniel@gaisler.com>
To: sparclinux@vger.kernel.org
Subject: [PATCH 0/2] sparc32,leon: PCI patches
Date: Tue, 26 Apr 2011 08:54:16 +0000 [thread overview]
Message-ID: <4DB68838.1020304@gaisler.com> (raw)
Hello Dave,
The patches in this series must be applied ontop of the genriq patches
sent previously.
The patches implement PCI for the LEON architecture. The LEON supports
different PCI Host controllers, I have tried to collect common parts in
leon_pci.c and host drivers will be named leon_pci_*.c.
There is no BIOS or bootloader initializing PCI for use in comparison to
the PCIC-SPARC32 code. LEON rely on the Linux generic resource & IRQ
code to probe and setup the bus for us, drivers/pci/Makefile is
dependent on CONFIG_SPARC_LEON in order not to brake PCIC. PCIC can not
be defined at the same time as the LEON PCI layer, so the CONFIG_PCI
ifdeffs has been replaced with CONFIG_PCI && !CONFIG_SPARC_LEON.
Thanks,
Daniel
arch/sparc/Kconfig | 7 +
arch/sparc/include/asm/leon.h | 3 +
arch/sparc/include/asm/pci_32.h | 5 +
arch/sparc/include/asm/pci_leon.h | 36 ++
arch/sparc/include/asm/pcic.h | 2 +-
arch/sparc/kernel/Makefile | 5 +
arch/sparc/kernel/entry.S | 2 +-
arch/sparc/kernel/leon_kernel.c | 15 +
arch/sparc/kernel/leon_pci.c | 237 +++++++++
arch/sparc/kernel/leon_pci_grpci2.c | 905
+++++++++++++++++++++++++++++++++++
drivers/pci/Makefile | 1 +
11 files changed, 1216 insertions(+), 2 deletions(-)
next reply other threads:[~2011-04-26 8:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 8:54 Daniel Hellstrom [this message]
2011-05-16 20:01 ` [PATCH 0/2] sparc32,leon: PCI patches David Miller
2011-05-19 13:13 ` Daniel Hellstrom
2011-05-19 19:01 ` David Miller
2011-05-20 8:01 ` Daniel Hellstrom
2011-05-20 8:08 ` David Miller
2011-05-20 14:22 ` Daniel Hellstrom
2011-05-20 18:24 ` David Miller
2011-05-23 8:49 ` Daniel Hellstrom
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=4DB68838.1020304@gaisler.com \
--to=daniel@gaisler.com \
--cc=sparclinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.