1. 16 5月, 2012 1 次提交
  2. 14 5月, 2012 1 次提交
    • R
      ARM: PCI: get rid of pci_std_swizzle() · daeb4c0c
      Russell King 提交于
      Most PCI implementations use the standard PCI swizzle function, which
      handles the well defined behaviour of PCI-to-PCI bridges which can be
      found on cards (eg, four port ethernet cards.)
      
      Rather than having almost every platform specify the standard swizzle
      function, make this the default when no swizzle function is supplied.
      Therefore, a swizzle function only needs to be provided when there is
      something exceptional which needs to be handled.
      
      This gets rid of the swizzle initializer from 47 files, and leaves us
      with just two platforms specifying a swizzle function: ARM Integrator
      and Chalice CATS.
      Acked-by: NKrzysztof Hałasa <khc@pm.waw.pl>
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      daeb4c0c
  3. 09 5月, 2012 2 次提交
  4. 24 2月, 2012 1 次提交
  5. 07 1月, 2012 1 次提交
  6. 14 12月, 2011 2 次提交
  7. 22 7月, 2011 1 次提交
    • R
      PCI: Make the struct pci_dev * argument of pci_fixup_irqs const. · d5341942
      Ralf Baechle 提交于
      Aside of the usual motivation for constification,  this function has a
      history of being abused a hook for interrupt and other fixups so I turned
      this function const ages ago in the MIPS code but it should be done
      treewide.
      
      Due to function pointer passing in varous places a few other functions
      had to be constified as well.
      Signed-off-by: NRalf Baechle <ralf@linux-mips.org>
      To: Anton Vorontsov <avorontsov@mvista.com>
      To: Chris Metcalf <cmetcalf@tilera.com>
      To: Colin Cross <ccross@android.com>
      Acked-by: N"David S. Miller" <davem@davemloft.net>
      To: Eric Miao <eric.y.miao@gmail.com>
      To: Erik Gilling <konkers@android.com>
      Acked-by: NGuan Xuetao <gxt@mprc.pku.edu.cn>
      To: "H. Peter Anvin" <hpa@zytor.com>
      To: Imre Kaloz <kaloz@openwrt.org>
      To: Ingo Molnar <mingo@redhat.com>
      To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
      To: Jesse Barnes <jbarnes@virtuousgeek.org>
      To: Krzysztof Halasa <khc@pm.waw.pl>
      To: Lennert Buytenhek <kernel@wantstofly.org>
      To: Matt Turner <mattst88@gmail.com>
      To: Nicolas Pitre <nico@fluxnic.net>
      To: Olof Johansson <olof@lixom.net>
      Acked-by: NPaul Mundt <lethal@linux-sh.org>
      To: Richard Henderson <rth@twiddle.net>
      To: Russell King <linux@arm.linux.org.uk>
      To: Thomas Gleixner <tglx@linutronix.de>
      Cc: Andrew Morton <akpm@linux-foundation.org>
      Cc: linux-alpha@vger.kernel.org
      Cc: linux-arm-kernel@lists.infradead.org
      Cc: linux-kernel@vger.kernel.org
      Cc: linux-mips@linux-mips.org
      Cc: linux-pci@vger.kernel.org
      Cc: linux-sh@vger.kernel.org
      Cc: linux-tegra@vger.kernel.org
      Cc: sparclinux@vger.kernel.org
      Cc: x86@kernel.org
      Signed-off-by: NJesse Barnes <jbarnes@virtuousgeek.org>
      d5341942
  8. 13 7月, 2011 1 次提交
  9. 04 3月, 2011 1 次提交
  10. 20 9月, 2010 1 次提交
  11. 17 7月, 2010 2 次提交
  12. 30 3月, 2010 1 次提交
    • T
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking... · 5a0e3ad6
      Tejun Heo 提交于
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h
      
      percpu.h is included by sched.h and module.h and thus ends up being
      included when building most .c files.  percpu.h includes slab.h which
      in turn includes gfp.h making everything defined by the two files
      universally available and complicating inclusion dependencies.
      
      percpu.h -> slab.h dependency is about to be removed.  Prepare for
      this change by updating users of gfp and slab facilities include those
      headers directly instead of assuming availability.  As this conversion
      needs to touch large number of source files, the following script is
      used as the basis of conversion.
      
        http://userweb.kernel.org/~tj/misc/slabh-sweep.py
      
      The script does the followings.
      
      * Scan files for gfp and slab usages and update includes such that
        only the necessary includes are there.  ie. if only gfp is used,
        gfp.h, if slab is used, slab.h.
      
      * When the script inserts a new include, it looks at the include
        blocks and try to put the new include such that its order conforms
        to its surrounding.  It's put in the include block which contains
        core kernel includes, in the same order that the rest are ordered -
        alphabetical, Christmas tree, rev-Xmas-tree or at the end if there
        doesn't seem to be any matching order.
      
      * If the script can't find a place to put a new include (mostly
        because the file doesn't have fitting include block), it prints out
        an error message indicating which .h file needs to be added to the
        file.
      
      The conversion was done in the following steps.
      
      1. The initial automatic conversion of all .c files updated slightly
         over 4000 files, deleting around 700 includes and adding ~480 gfp.h
         and ~3000 slab.h inclusions.  The script emitted errors for ~400
         files.
      
      2. Each error was manually checked.  Some didn't need the inclusion,
         some needed manual addition while adding it to implementation .h or
         embedding .c file was more appropriate for others.  This step added
         inclusions to around 150 files.
      
      3. The script was run again and the output was compared to the edits
         from #2 to make sure no file was left behind.
      
      4. Several build tests were done and a couple of problems were fixed.
         e.g. lib/decompress_*.c used malloc/free() wrappers around slab
         APIs requiring slab.h to be added manually.
      
      5. The script was run on all .h files but without automatically
         editing them as sprinkling gfp.h and slab.h inclusions around .h
         files could easily lead to inclusion dependency hell.  Most gfp.h
         inclusion directives were ignored as stuff from gfp.h was usually
         wildly available and often used in preprocessor macros.  Each
         slab.h inclusion directive was examined and added manually as
         necessary.
      
      6. percpu.h was updated not to include slab.h.
      
      7. Build test were done on the following configurations and failures
         were fixed.  CONFIG_GCOV_KERNEL was turned off for all tests (as my
         distributed build env didn't work with gcov compiles) and a few
         more options had to be turned off depending on archs to make things
         build (like ipr on powerpc/64 which failed due to missing writeq).
      
         * x86 and x86_64 UP and SMP allmodconfig and a custom test config.
         * powerpc and powerpc64 SMP allmodconfig
         * sparc and sparc64 SMP allmodconfig
         * ia64 SMP allmodconfig
         * s390 SMP allmodconfig
         * alpha SMP allmodconfig
         * um on x86_64 SMP allmodconfig
      
      8. percpu.h modifications were reverted so that it could be applied as
         a separate patch and serve as bisection point.
      
      Given the fact that I had only a couple of failures from tests on step
      6, I'm fairly confident about the coverage of this conversion patch.
      If there is a breakage, it's likely to be something in one of the arch
      headers which should be easily discoverable easily on most builds of
      the specific arch.
      Signed-off-by: NTejun Heo <tj@kernel.org>
      Guess-its-ok-by: NChristoph Lameter <cl@linux-foundation.org>
      Cc: Ingo Molnar <mingo@redhat.com>
      Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
      5a0e3ad6
  13. 08 11月, 2009 2 次提交
    • L
    • L
      [ARM] kirkwood: fix PCI I/O port assignment · 35f029e2
      Lennert Buytenhek 提交于
      Instead of allocating PCI devices I/O port bus addresses from the
      000xxxxx I/O port range as intended, due to a bus versus physical
      address mixup, the Kirkwood PCIe handling code inadvertently
      allocated I/O port bus addresses from the f20xxxxx address range
      (which is the physical address range of the PCIe I/O mapping window),
      but then direct all I/O port accesses to bus addresses 000xxxxx,
      which would then not be decoded at all.
      
      Fix this by setting the base address of the PCIe I/O space struct
      resource to KIRKWOOD_PCIE_IO_BUS_BASE instead of the incorrect
      KIRKWOOD_PCIE_IO_PHYS_BASE, and fix up __io() to expect addresses
      offsetted by the former instead of the latter.
      
      (The suggested fix of directing I/O port accesses from the host to
      bus addresses f20xxxxx instead has the problem that assigning full
      32bit I/O port bus addresses (f20xxxxx) doesn't work on all PCI
      devices, as not all PCI devices implement full 32 bit BAR registers
      for I/O ports.  We should really try to allocate I/O port bus
      addresses that fit in 16 bits.)
      Signed-off-by: NLennert Buytenhek <buytenh@marvell.com>
      Signed-off-by: NNicolas Pitre <nico@marvell.com>
      35f029e2
  14. 06 11月, 2009 1 次提交
    • L
      [ARM] kirkwood: fix section mismatch · 6de95c19
      Li Jie 提交于
      kirkwood_timer_init() and kirkwood_pcie_setup() lack of __init which
      causes following warnings:
      
      WARNING: vmlinux.o(.text+0x9568): Section mismatch in reference from
      the function kirkwood_timer_init() to the function
      .init.text:kirkwood_find_tclk()
      The function kirkwood_timer_init() references
      the function __init kirkwood_find_tclk().
      This is often because kirkwood_timer_init lacks a __init
      annotation or the annotation of kirkwood_find_tclk is wrong.
      
      WARNING: vmlinux.o(.text+0x979c): Section mismatch in reference from
      the function kirkwood_pcie_setup() to the function
      .init.text:orion_pcie_setup()
      The function kirkwood_pcie_setup() references
      the function __init orion_pcie_setup().
      This is often because kirkwood_pcie_setup lacks a __init
      annotation or the annotation of orion_pcie_setup is wrong.
      Signed-off-by: Nlijie <eltshanli@gmail.com>
      Signed-off-by: NNicolas Pitre <nico@fluxnic.net>
      6de95c19
  15. 09 6月, 2009 1 次提交
  16. 09 1月, 2009 1 次提交
  17. 26 9月, 2008 1 次提交
  18. 09 8月, 2008 1 次提交
  19. 23 6月, 2008 1 次提交
    • S
      [ARM] add Marvell Kirkwood (88F6000) SoC support · 651c74c7
      Saeed Bishara 提交于
      The Marvell Kirkwood (88F6000) is a family of ARM SoCs based on a
      Shiva CPU core, and features a DDR2 controller, a x1 PCIe interface,
      a USB 2.0 interface, a SPI controller, a crypto accelerator, a TS
      interface, and IDMA/XOR engines, and depending on the model, also
      features one or two Gigabit Ethernet interfaces, two SATA II
      interfaces, one or two TWSI interfaces, one or two UARTs, a
      TDM/SLIC interface, a NAND controller, an I2S/SPDIF interface, and
      an SDIO interface.
      
      This patch adds supports for the Marvell DB-88F6281-BP Development
      Board and the RD-88F6192-NAS and the RD-88F6281 Reference Designs,
      enabling support for the PCIe interface, the USB interface, the
      ethernet interfaces, the SATA interfaces, the TWSI interfaces, the
      UARTs, and the NAND controller.
      Signed-off-by: NSaeed Bishara <saeed@marvell.com>
      Signed-off-by: NLennert Buytenhek <buytenh@marvell.com>
      651c74c7