1. 16 Sep, 2015 1 commit
    • Thomas Gleixner's avatar
      genirq: Remove irq argument from irq flow handlers · bd0b9ac4
      Thomas Gleixner authored
      Most interrupt flow handlers do not use the irq argument. Those few
      which use it can retrieve the irq number from the irq descriptor.
      
      Remove the argument.
      
      Search and replace was done with coccinelle and some extra helper
      scripts around it. Thanks to Julia for her help!
      Signed-off-by: default avatarThomas Gleixner <tglx@linutronix.de>
      Cc: Julia Lawall <Julia.Lawall@lip6.fr>
      Cc: Jiang Liu <jiang.liu@linux.intel.com>
      bd0b9ac4
  2. 01 Aug, 2015 1 commit
    • Thomas Gleixner's avatar
      m68k/irq: Prepare irq handlers for irq argument removal · 625b86ad
      Thomas Gleixner authored
      The irq argument of most interrupt flow handlers is unused or merily
      used instead of a local variable. The handlers which need the irq
      argument can retrieve the irq number from the irq descriptor.
      
      Search and update was done with coccinelle and the invaluable help of
      Julia Lawall.
      Signed-off-by: default avatarThomas Gleixner <tglx@linutronix.de>
      Cc: Julia Lawall <Julia.Lawall@lip6.fr>
      Cc: Geert Uytterhoeven <geert@linux-m68k.org>
      Cc: linux-m68k@lists.linux-m68k.org
      625b86ad
  3. 28 Sep, 2014 2 commits
    • Greg Ungerer's avatar
      m68knommu: fix size of address field for 5272 interrupt controller · ecb6bdcd
      Greg Ungerer authored
      Picked up by the 0-day buidler:
      
      All warnings:
      >> arch/m68k/coldfire/intc-5272.c:46:20: warning: large integer implicitly truncated to unsigned type [-Woverflow]
           /*MCF_IRQ_EINT1*/ { .icr = MCFSIM_ICR1, .index = 28, .ack = 1, },
      ...
      
      The problem stems from the changes to make all ColdFire register addresses
      absolute, in commit d72a5abb ("make remaining ColdFire 5272 register
      definitions absolute"). That change did not take into account that the
      addresses were stored as offsets in the irqmap of the intc-5272.c code.
      Make the field that now stores register addresses big enough to hold
      addresses.
      Signed-off-by: default avatarGreg Ungerer <gerg@uclinux.org>
      ecb6bdcd
    • Greg Ungerer's avatar
      m68k: move coldfire platform code · f86b9e03
      Greg Ungerer authored
      Move the m68k ColdFire platform support code directory to be with the
      existing m68k platforms. Although the ColdFire is not a platform as such,
      we have always kept all its support together. No reason to change that
      as this time.
      Signed-off-by: default avatarGreg Ungerer <gerg@uclinux.org>
      Acked-by: default avatarGeert Uytterhoeven <geert@linux-m68k.org>
      f86b9e03
  4. 27 Sep, 2012 1 commit
    • Greg Ungerer's avatar
      m68knommu: make ColdFire Interrupt Source register definitions absolute addresses · c986a3d5
      Greg Ungerer authored
      Make all definitions of the ColdFire Interrupt Source registers absolute
      addresses. Currently some are relative to the MBAR peripheral region.
      
      The various ColdFire parts use different methods to address the internal
      registers, some are absolute, some are relative to peripheral regions
      which can be mapped at different address ranges (such as the MBAR and IPSBAR
      registers). We don't want to deal with this in the code when we are
      accessing these registers, so make all register definitions the absolute
      address - factoring out whether it is an offset into a peripheral region.
      
      This makes them all consistently defined, and reduces the occasional bugs
      caused by inconsistent definition of the register addresses.
      Signed-off-by: default avatarGreg Ungerer <gerg@uclinux.org>
      c986a3d5
  5. 20 May, 2012 1 commit
  6. 25 Jul, 2011 1 commit
    • Greg Ungerer's avatar
      m68knommu: correctly use trap_init · 622e9472
      Greg Ungerer authored
      Currently trap_init() is an empty function for m68knommu. Instead
      the vectors are being setup as part of the IRQ initialization.
      This is inconsistent with m68k and other architectures.
      
      Change the local init_vectors() to be trap_init(), and init the
      vectors at the correct time during startup. This will help merge of
      m68k and m68knommu trap code in the furture.
      Signed-off-by: default avatarGreg Ungerer <gerg@uclinux.org>
      622e9472
  7. 31 Mar, 2011 1 commit
  8. 29 Mar, 2011 1 commit
  9. 25 Mar, 2011 1 commit
    • Greg Ungerer's avatar
      m68k: merge m68k and m68knommu arch directories · 66d857b0
      Greg Ungerer authored
      There is a lot of common code that could be shared between the m68k
      and m68knommu arch branches. It makes sense to merge the two branches
      into a single directory structure so that we can more easily share
      that common code.
      
      This is a brute force merge, based on a script from Stephen King
      <sfking@fdwdc.com>, which was originally written by Arnd Bergmann
      <arnd@arndb.de>.
      
      > The script was inspired by the script Sam Ravnborg used to merge the
      > includes from m68knommu. For those files common to both arches but
      > differing in content, the m68k version of the file is renamed to
      > <file>_mm.<ext> and the m68knommu version of the file is moved into the
      > corresponding m68k directory and renamed <file>_no.<ext> and a small
      > wrapper file <file>.<ext> is used to select between the two version. Files
      > that are common to both but don't differ are removed from the m68knommu
      > tree and files and directories that are unique to the m68knommu tree are
      > moved to the m68k tree. Finally, the arch/m68knommu tree is removed.
      >
      > To select between the the versions of the files, the wrapper uses
      >
      > #ifdef CONFIG_MMU
      > #include <file>_mm.<ext>
      > #else
      > #include <file>_no.<ext>
      > #endif
      
      On top of this file merge I have done a simplistic merge of m68k and
      m68knommu Kconfig, which primarily attempts to keep existing options and
      menus in place. Other than a handful of options being moved it produces
      identical .config outputs on m68k and m68knommu targets I tested it on.
      
      With this in place there is now quite a bit of scope for merge cleanups
      in future patches.
      Signed-off-by: default avatarGreg Ungerer <gerg@uclinux.org>
      66d857b0
  10. 15 Mar, 2011 2 commits
  11. 21 Oct, 2010 2 commits
  12. 15 Sep, 2009 1 commit