1. 27 9月, 2012 10 次提交
    • G
      m68knommu: remove address offsets relative to IPSBAR for ColdFire 527x · f821e349
      Greg Ungerer 提交于
      Remove the last address definitions relative to the IPSBAR peripheral region
      for the ColdFire 527x family. This involved cleaning up some magic numbers
      used in the code part, and making them proper register definitions in the 527x
      specific header.
      
      This is part of the process of cleaning up the ColdFire register definitions
      to make them consistently use absolute addresses for the primary registers.
      This will reduce the occasional bugs caused by inconsistent definition of
      the register addresses.
      Signed-off-by: NGreg Ungerer <gerg@uclinux.org>
      f821e349
    • G
      m68knommu: fix wrong register offsets used for ColdFire 5272 multi-function pins · 4fb62ede
      Greg Ungerer 提交于
      The registers used to configure and set the multifunction pins on the 5272
      ColdFire are defined as absolute addresses. So the use of them does not need
      to be offset relative to the peripheral region address.
      
      Fix two cases of incorrect usage of these addresses. Both affect UART
      initialization, one in the common UART pin setup code, the other in the
      NETtel board specific UART signal handling.
      Signed-off-by: NGreg Ungerer <gerg@uclinux.org>
      4fb62ede
    • G
      m68knommu: make ColdFire 5249 MBAR2 register definitions absolute addresses · 041a89a4
      Greg Ungerer 提交于
      Make the ColdFire 5249 MBAR peripheral register definitions absolute
      addresses, instead of offsets into the 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: NGreg Ungerer <gerg@uclinux.org>
      041a89a4
    • G
      m68knommu: make remaining ColdFire 5272 register definitions absolute addresses · d72a5abb
      Greg Ungerer 提交于
      Make the remaining definitions of the 5272 ColdFire 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: NGreg Ungerer <gerg@uclinux.org>
      d72a5abb
    • G
      m68knommu: make ColdFire Chip Select register definitions absolute addresses · 1419ea3b
      Greg Ungerer 提交于
      Make all definitions of the ColdFire Chip Select 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: NGreg Ungerer <gerg@uclinux.org>
      1419ea3b
    • G
      m68knommu: make ColdFire Interrupt Source register definitions absolute addresses · c986a3d5
      Greg Ungerer 提交于
      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: NGreg Ungerer <gerg@uclinux.org>
      c986a3d5
    • G
      m68knommu: make ColdFire watchdog register definitions absolute addresses · 660b73e3
      Greg Ungerer 提交于
      Make all definitions of the ColdFire Software watchdog 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: NGreg Ungerer <gerg@uclinux.org>
      660b73e3
    • G
      m68knommu: make ColdFire SYPCR and RSR register definitions absolute addresses · e1e362dc
      Greg Ungerer 提交于
      Make all definitions of the ColdFire Reset and System 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 abolsute
      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: NGreg Ungerer <gerg@uclinux.org>
      e1e362dc
    • G
      m68knommu: make ColdFire IMR and IPR register definitions absolute addresses · 6a3a786d
      Greg Ungerer 提交于
      Make all definitions of the ColdFire Interrupt Mask and Pending 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: NGreg Ungerer <gerg@uclinux.org>
      6a3a786d
    • P
      m68k: drop unused parts of 68VZ328 Makefile · 0c0e6db8
      Paul Bolle 提交于
      DRAGEN2 should obviously be CONFIG_DRAGEN2, but the screen.h entry it
      triggers only references files that are nowhere to be found in the
      current tree. Besides, nothing uses screen.h. So just drop all that.
      Signed-off-by: NPaul Bolle <pebolle@tiscali.nl>
      Signed-off-by: NGreg Ungerer <gerg@uclinux.org>
      0c0e6db8
  2. 16 9月, 2012 1 次提交
  3. 17 7月, 2012 1 次提交
  4. 16 7月, 2012 8 次提交
  5. 27 6月, 2012 1 次提交
  6. 25 6月, 2012 1 次提交
    • G
      m68knommu: define a local devm_clk_get() function · 19a1d332
      Greg Ungerer 提交于
      Commit f4d40de3 ("net fec: do not depend
      on grouped clocks") breaks compilation of the FEC driver for non iMX
      platforms in linux-3.5-rc1. For example when compiling for ColdFire I get:
      
            LD      vmlinux
          drivers/built-in.o: In function `fec_probe':
          fec.c:(.devinit.text+0x1e0): undefined reference to `devm_clk_get'
      
      Define a simple devm_clk_get() function for the m68knommu architecture.
      Signed-off-by: NGreg Ungerer <gerg@uclinux.org>
      19a1d332
  7. 12 6月, 2012 2 次提交
    • G
      m68knommu: fix 68360 local setting of timer interrupt handler · 1b461d76
      Greg Ungerer 提交于
      Compiling for 68360 based targets fails with:
      
          arch/m68k/platform/68360/config.c: In function ‘hw_tick’:
          arch/m68k/platform/68360/config.c:55:2: error: implicit declaration of function ‘arch_timer_interrupt’
          arch/m68k/platform/68360/config.c: At top level:
          arch/m68k/platform/68360/config.c:64:6: error: conflicting types for ‘hw_timer_init’
          arch/m68k/include/asm/machdep.h:36:13: note: previous declaration of ‘hw_timer_init’ was here
      
      Changes made to hw_timer_init() didn't get updated in the 68328 timer code.
      So process and call the "handler" arg that is now passed into that
      hw_timer_init() function.
      Signed-off-by: NGreg Ungerer <gerg@uclinux.org>
      1b461d76
    • G
      m68knommu: fix 68328 local setting of timer interrupt handler · dc5588ae
      Greg Ungerer 提交于
      Compiling for 68328 based targets fails with:
      
          arch/m68k/platform/68328/timers.c: In function ‘hw_tick’:
          arch/m68k/platform/68328/timers.c:65:2: error: implicit declaration of function ‘arch_timer_interrupt’
          arch/m68k/platform/68328/timers.c: At top level:
          arch/m68k/platform/68328/timers.c:102:6: error: conflicting types for ‘hw_timer_init’
          arch/m68k/include/asm/machdep.h:36:13: note: previous declaration of ‘hw_timer_init’ was here
      
      Changes made to hw_timer_init() didn't get updated in the 68328 timer code.
      So process and call the "handler" arg that is now passed into that
      hw_timer_init() function.
      Signed-off-by: NGreg Ungerer <gerg@uclinux.org>
      dc5588ae
  8. 22 5月, 2012 1 次提交
    • A
      m68k: add TIF_NOTIFY_RESUME and handle it. · a54f1655
      Al Viro 提交于
      TIF_NOTIFY_RESUME added (as bit 5).  That way nommu glue needs no changes at
      all; mmu one needs just to replace jmi do_signal_return to jne do_signal_return
      There we have flags shifted up, until bit 6 (SIGPENDING) is in MSBit; instead
      of checking that MSBit is set (jmi) we check that MSBit or something below it
      is set (jne); bits 0..4 are never set, so that's precisely "bit 6 or bit 5 is
      set".
      
      Usual handling of NOTIFY_RESUME/SIGPENDING is done in do_notify_resume(); glue
      calls it instead of do_signal().
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      a54f1655
  9. 20 5月, 2012 15 次提交