From: <gerg@snapgear.com>
To: linux-m68k@vger.kernel.org
Subject: [PATCH v2 0/5] ColdFire PCI bus support
Date: Mon, 16 Jul 2012 22:27:21 +1000 [thread overview]
Message-ID: <1342441646-5645-1-git-send-email-gerg@snapgear.com> (raw)
This is version 2 of the ColdFire PCI bus support.
The following patch series adds support for the PCI bus on the ColdFire
M54[78]x family of parts.
Changes since the last version:
. change to drivers/pci/Makefile sent to linux-pci email list separately
. header file changes broken out into a separate patch (for easier review)
. IO barriers added within PCI config space access functions
---
arch/m68k/Kconfig.bus | 7
arch/m68k/include/asm/dma.h | 4
arch/m68k/include/asm/io_mm.h | 50 +++++
arch/m68k/include/asm/m54xxpci.h | 138 ++++++++++++++
arch/m68k/include/asm/m54xxsim.h | 3
arch/m68k/include/asm/pci.h | 6
arch/m68k/kernel/Makefile | 1
arch/m68k/kernel/pcibios.c | 109 +++++++++++
arch/m68k/platform/coldfire/Makefile | 2
arch/m68k/platform/coldfire/pci.c | 327 +++++++++++++++++++++++++++++++++++
10 files changed, 646 insertions(+), 1 deletion(-)
next reply other threads:[~2012-07-16 12:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-16 12:27 gerg [this message]
2012-07-16 12:27 ` [PATCH v2 1/5] m68k: common PCI support definitions and code gerg
2021-06-28 7:44 ` Geert Uytterhoeven
2021-06-28 13:23 ` Greg Ungerer
2021-06-28 13:29 ` Geert Uytterhoeven
2021-06-28 13:58 ` Greg Ungerer
2012-07-16 12:27 ` [PATCH v2 2/5] m68k: add PCI bus support definitions for the ColdFire M54xx SoC family gerg
2012-07-16 12:27 ` [PATCH v2 3/5] m68k: add IO access definitions to support PCI on ColdFire platforms gerg
2012-07-16 12:27 ` [PATCH v2 4/5] m68k: add PCI bus code support for the ColdFire M54xx SoC family gerg
2012-07-16 12:27 ` [PATCH v2 5/5] m68k: allow PCI bus to be enabled for ColdFire m54xx CPUs gerg
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=1342441646-5645-1-git-send-email-gerg@snapgear.com \
--to=gerg@snapgear.com \
--cc=linux-m68k@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 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).