1. 27 9月, 2012 1 次提交
  2. 17 7月, 2012 1 次提交
  3. 05 3月, 2012 1 次提交
    • G
      m68knommu: make 54xx UART platform addressing consistent · bbbeeaf2
      Greg Ungerer 提交于
      If we make all UART addressing consistent across all ColdFire family members
      then we will be able to remove the duplicated plaform data and use a single
      setup for all.
      
      So modify the ColdFire 54xx UART addressing so that:
      
      . UARTs are numbered from 0 up
      . base addresses are absolute (not relative to MBAR peripheral register)
      . use a common name for IRQs used
      Signed-off-by: NGreg Ungerer <gerg@uclinux.org>
      bbbeeaf2
  4. 15 3月, 2011 3 次提交
    • G
      m68knommu: external interrupt support to ColdFire intc-2 controller · 57b48143
      Greg Ungerer 提交于
      The EDGE Port module of some ColdFire parts using the intc-2 interrupt
      controller provides support for 7 external interrupts. These interrupts
      go off-chip (that is they are not for internal peripherals). They need
      some special handling and have some extra setup registers. Add code to
      support them.
      Signed-off-by: NGreg Ungerer <gerg@uclinux.org>
      57b48143
    • G
      m68knommu: remove ColdFire CLOCK_DIV config option · ce3de78a
      Greg Ungerer 提交于
      The reality is that you do not need the abiltity to configure the
      clock divider for ColdFire CPUs. It is a fixed ratio on any given
      ColdFire family member. It is not the same for all ColdFire parts,
      but it is always the same in a model range. So hard define the divider
      for each supported ColdFire CPU type and remove the Kconfig option.
      Signed-off-by: NGreg Ungerer <gerg@uclinux.org>
      ce3de78a
    • G
      m68knommu: remove kludge seting of MCF_IPSBAR for ColdFire 54xx · 254eef74
      Greg Ungerer 提交于
      The ColdFire 54xx family shares the same interrupt controller used
      on the 523x, 527x and 528x ColdFire parts, but it isn't offset
      relative to the IPSBAR register. The 54xx doesn't have an IPSBAR
      register.
      
      By including the base address of the peripheral registers in the register
      definitions (MCFICM_INTC0 and MCFICM_INTC1 in this case) we can avoid
      having to define a fake IPSBAR for the 54xx. And this makes the register
      address definitions of these more consistent, the majority of the other
      register address defines include the peripheral base address already.
      Signed-off-by: NGreg Ungerer <gerg@uclinux.org>
      254eef74
  5. 05 1月, 2011 5 次提交
  6. 21 10月, 2010 1 次提交