public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alessandro Rubini <rubini@gnudd.com>
To: linux-kernel@vger.kernel.org
Cc: Giancarlo Asnaghi <giancarlo.asnaghi@st.com>,
	Alan Cox <alan@linux.intel.com>,
	tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
	x86@kernel.org, Jesse Barnes <jbarnes@virtuousgeek.org>,
	Ingo Molnar <mingo@elte.hu>
Subject: [PATCH V5 0/3] STA2X11: patches for pci bridge support
Date: Wed, 4 Apr 2012 19:39:45 +0200	[thread overview]
Message-ID: <cover.1333560789.git.rubini@gnudd.com> (raw)

This is a repost of the patch set I sent on Mar 13th.
Patch 3 is modified to accound for a change in prototype for
the swiotlb alloc method.

Patch 3 is dependent on patch 1 and 2, which are unordered. The
big patch was picked up from V2 but without its dependencies.
It seems like the set can be accepted but was probably forgotten.

Other patches (for the sub-devices in this chip) are being worked on,
but they all depend on CONFIG_STA2X11, so I'd like these to be merged.
No problems have been reported on V4 and I actually expected Ingo to
pull them.

thanks
/alessandro


Summary:

Patch 1: no functional effect (it uses an existing "#ifdef CONFIG_X86_64"
in the 32-bit world, so it's not CONFIG_X86_64 but a new name)

Patch 2: no functional effect (it allows some inline functions to not be
inline where needed, with a new config symbol).

Patch 3: it's the real content.


History:

V5: rebased on next-20120403, fixed swiotlb change.

V4: rebased on next-20120309, no changes.

V3: rebased on next-20120221. Fixed patch 3 to match new DMA
prototypes. Renamed patch 3 as Ingo and Jesse merged it. Added both of
them to explicit Cc: list in the email set.

V2: rebased, minor and less-minor changes in patch 3/3.




Alessandro Rubini (3):
  x86: introduce CONFIG_X86_DEV_DMA_OPS
  x86: introduce CONFIG_X86_DMA_REMAP
  x86/PCI: initial support for sta2x11 I/O hub

 arch/x86/Kconfig                   |   34 +++-
 arch/x86/include/asm/device.h      |    4 +-
 arch/x86/include/asm/dma-mapping.h |    9 +-
 arch/x86/pci/Makefile              |    2 +
 arch/x86/pci/sta2x11-fixup.c       |  366 ++++++++++++++++++++++++++++++++++++
 5 files changed, 408 insertions(+), 7 deletions(-)
 create mode 100644 arch/x86/pci/sta2x11-fixup.c

-- 
1.7.7.2

             reply	other threads:[~2012-04-04 17:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-04 17:39 Alessandro Rubini [this message]
2012-04-04 17:39 ` [PATCH V5 1/3] x86: introduce CONFIG_X86_DEV_DMA_OPS Alessandro Rubini
2012-04-12 19:41   ` [tip:x86/platform] x86-32: Introduce CONFIG_X86_DEV_DMA_OPS tip-bot for Alessandro Rubini
2012-04-04 17:40 ` [PATCH V5 2/3] x86: introduce CONFIG_X86_DMA_REMAP Alessandro Rubini
2012-04-12 19:41   ` [tip:x86/platform] x86: Introduce CONFIG_X86_DMA_REMAP tip-bot for Alessandro Rubini
2012-04-04 17:40 ` [PATCH V5 3/3] x86/PCI: initial support for sta2x11 I/O hub Alessandro Rubini
2012-04-12 19:43   ` [tip:x86/platform] x86, platform: Initial support for sta2x11 I/ O hub tip-bot for Alessandro Rubini

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=cover.1333560789.git.rubini@gnudd.com \
    --to=rubini@gnudd.com \
    --cc=alan@linux.intel.com \
    --cc=giancarlo.asnaghi@st.com \
    --cc=hpa@zytor.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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