1. 14 2月, 2010 2 次提交
    • P
      powerpc/85xx: Fix SMP when "cpu-release-addr" is in lowmem · d1d47ec6
      Peter Tyser 提交于
      Recent U-Boot commit 5ccd29c3679b3669b0bde5c501c1aa0f325a7acb caused
      the "cpu-release-addr" device tree property to contain the physical RAM
      location that secondary cores were spinning at.  Previously, the
      "cpu-release-addr" property contained a value referencing the boot page
      translation address range of 0xfffffxxx, which then indirectly accessed
      RAM.
      
      The "cpu-release-addr" is currently ioremapped and the secondary cores
      kicked.  However, due to the recent change in "cpu-release-addr", it
      sometimes points to a memory location in low memory that cannot be
      ioremapped.  For example on a P2020-based board with 512MB of RAM the
      following error occurs on bootup:
      
        <...>
        mpic: requesting IPIs ...
        __ioremap(): phys addr 0x1ffff000 is RAM lr c05df9a0
        Unable to handle kernel paging request for data at address 0x00000014
        Faulting instruction address: 0xc05df9b0
        Oops: Kernel access of bad area, sig: 11 [#1]
        SMP NR_CPUS=2 P2020 RDB
        Modules linked in:
        <... eventual kernel panic>
      
      Adding logic to conditionally ioremap or access memory directly resolves
      the issue.
      Signed-off-by: NPeter Tyser <ptyser@xes-inc.com>
      Signed-off-by: NNate Case <ncase@xes-inc.com>
      Reported-by: NDipen Dudhat <B09055@freescale.com>
      Tested-by: NDipen Dudhat <B09055@freescale.com>
      Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
      d1d47ec6
    • A
      powerpc/85xx: Fix oops during MSI driver probe on MPC85xxMDS boards · fa644298
      Anton Vorontsov 提交于
      MPC85xx chips report the wrong value in feature reporting register,
      and that causes the following oops:
      
       Unable to handle kernel paging request for data at address 0x00000c00
       Faulting instruction address: 0xc0019294
       Oops: Kernel access of bad area, sig: 11 [#1]
       MPC8569 MDS
       Modules linked in:
       [...]
       NIP [c0019294] mpic_set_irq_type+0x2f0/0x368
       LR [c0019124] mpic_set_irq_type+0x180/0x368
       Call Trace:
       [ef851d60] [c0019124] mpic_set_irq_type+0x180/0x368 (unreliable)
       [ef851d90] [c007958c] __irq_set_trigger+0x44/0xd4
       [ef851db0] [c007b550] set_irq_type+0x40/0x7c
       [ef851dc0] [c0004a60] irq_create_of_mapping+0xb4/0x114
       [ef851df0] [c0004af0] irq_of_parse_and_map+0x30/0x40
       [ef851e20] [c0405678] fsl_of_msi_probe+0x1a0/0x328
       [ef851e60] [c02e6438] of_platform_device_probe+0x5c/0x84
       [...]
      
      This is because mpic_alloc() assigns wrong values to
      mpic->isu_{size,shift,mask}, and things eventually break when
      _mpic_irq_read() is trying to use them.
      
      This patch fixes the issue by enabling MPIC_BROKEN_FRR_NIRQS quirk.
      Signed-off-by: NAnton Vorontsov <avorontsov@ru.mvista.com>
      Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
      fa644298
  2. 18 12月, 2009 1 次提交
  3. 09 12月, 2009 1 次提交
  4. 24 11月, 2009 1 次提交
  5. 21 11月, 2009 2 次提交
  6. 12 11月, 2009 3 次提交
  7. 30 10月, 2009 1 次提交
  8. 11 9月, 2009 1 次提交
  9. 28 8月, 2009 3 次提交
  10. 25 8月, 2009 3 次提交
  11. 20 8月, 2009 1 次提交
  12. 30 7月, 2009 1 次提交
  13. 23 6月, 2009 4 次提交
    • H
      powerpc/85xx: remove duplicated #include · 6cc7959f
      Huang Weiyi 提交于
      Remove duplicated #include in arch/powerpc/platforms/85xx/xes_mpc85xx.c.
      Signed-off-by: NHuang Weiyi <weiyi.huang@gmail.com>
      Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
      6cc7959f
    • K
      powerpc/85xx: Fix issue found by lockdep trace in smp_85xx_kick_cpu · cb1ffb62
      Kumar Gala 提交于
      lockdep trace found the following:
      
      ------------[ cut here ]------------
      Badness at c007baf0 [verbose debug info unavailable]
      NIP: c007baf0 LR: c007bad8 CTR: 00000000
      REGS: ef855e00 TRAP: 0700   Tainted: G        W
      (2.6.30-06736-g12a31df-dirty)
      MSR: 00021000 <ME,CE>  CR: 24044022  XER: 20000000
      TASK = ef858000[1] 'swapper' THREAD: ef854000 CPU: 0
      GPR00: 00000000 ef855eb0 ef858000 00000001 000000d0 f1000000 ffbc8000 ffffffff
      GPR08: 000000d0 c0760000 c0710000 00000007 2fffffff 1004a388 7ffd9400 00000000
      GPR16: 00000000 7ffcd100 7ffcd100 7ffcd100 c059cd78 c075c498 c057da7c ffffffff
      GPR24: ffbc8000 f1000000 00000001 c00bf8b0 c07595d4 000000d0 00021000 000000d0
      NIP [c007baf0] lockdep_trace_alloc+0xc0/0xf0
      LR [c007bad8] lockdep_trace_alloc+0xa8/0xf0
      Call Trace:
      [ef855eb0] [c007ba60] lockdep_trace_alloc+0x30/0xf0 (unreliable)
      [ef855ec0] [c00cb3ac] kmem_cache_alloc+0x2c/0xf0
      [ef855ee0] [c00bf8b0] __get_vm_area_node+0x80/0x1c0
      [ef855f10] [c0017580] __ioremap_caller+0x1d0/0x1e0
      [ef855f40] [c057da7c] smp_85xx_kick_cpu+0x64/0x124
      [ef855f60] [c0599180] __cpu_up+0xd0/0x1a4
      [ef855f80] [c05997c4] cpu_up+0x14c/0x1e0
      [ef855fc0] [c05732a0] kernel_init+0x100/0x1c4
      [ef855ff0] [c0011524] kernel_thread+0x4c/0x68
      Instruction dump:
      8009c174 2f800000 409e0048 73c08000 40820040 4818980d 2f830000 419effa0
      3d20c076 8009c388 2f800000 409eff90 <0fe00000> 4bffff88 60000000 60000000
      
      We were calling ioremap after we local_irq_restore(flags).  A simple
      reorder fixes the problem.
      Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
      cb1ffb62
    • R
      powerpc/85xx: Fix FSL RapidIO probing on MDS boards · fa874618
      Randy Vinson 提交于
      FSL RapidIO won't probe without a proper compatible entry. This
      patch fixes the issue by adding fsl,rapidio-delta compatible to
      mpc85xx_ids.
      Signed-off-by: NRandy Vinson <rvinson@mvista.com>
      Signed-off-by: NAnton Vorontsov <avorontsov@ru.mvista.com>
      Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
      fa874618
    • K
      powerpc/85xx: Stop using ppc_md.init on socrates · a44a23ed
      Kumar Gala 提交于
      Match what other 85xx platforms do for of_platform_bus_probe and use
      machine_device_initcall.  This is one small step in killing of
      ppc_md.init.
      Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
      a44a23ed
  14. 16 6月, 2009 2 次提交
  15. 19 5月, 2009 4 次提交
  16. 30 3月, 2009 1 次提交
  17. 27 3月, 2009 1 次提交
  18. 24 3月, 2009 1 次提交
  19. 11 3月, 2009 2 次提交
  20. 31 12月, 2008 2 次提交
  21. 16 12月, 2008 1 次提交
  22. 04 12月, 2008 2 次提交