1. 30 4月, 2013 3 次提交
    • K
      powerpc/fsl-booke: add the reg prop for pci bridge device node for T4/B4 · 9e2ecdbb
      Kevin Hao 提交于
      The reg property in the pci bridge device node is used to bind this
      device node to the pci bridge device. Then all the pci devices under
      this bridge could use the interrupt maps defined in this device node
      to do the irq translation. So if this property is missed, the pci
      traditional irq mechanism will not work.
      Signed-off-by: NKevin Hao <haokexin@gmail.com>
      Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
      9e2ecdbb
    • K
      powerpc/fsl-pci: don't unmap the PCI SoC controller registers in setup_pci_atmu · 04aa99cd
      Kevin Hao 提交于
      In patch 34642bbb (powerpc/fsl-pci: Keep PCI SoC controller registers in
      pci_controller) we choose to keep the map of the PCI SoC controller
      registers. But we missed to delete the unmap in setup_pci_atmu
      function. This will cause the following call trace once we access
      the PCI SoC controller registers later.
      
      Unable to handle kernel paging request for data at address 0x8000080080040f14
      Faulting instruction address: 0xc00000000002ea58
      Oops: Kernel access of bad area, sig: 11 [#1]
      SMP NR_CPUS=24 T4240 QDS
      Modules linked in:
      NIP: c00000000002ea58 LR: c00000000002eaf4 CTR: c00000000002eac0
      REGS: c00000017e10b4a0 TRAP: 0300   Not tainted  (3.9.0-rc1-00052-gfa3529f-dirty)
      MSR: 0000000080029000 <CE,EE,ME>  CR: 28adbe22  XER: 00000000
      SOFTE: 0
      DEAR: 8000080080040f14, ESR: 0000000000000000
      TASK = c00000017e100000[1] 'swapper/0' THREAD: c00000017e108000 CPU: 2
      GPR00: 0000000000000000 c00000017e10b720 c0000000009928d8 c00000017e578e00
      GPR04: 0000000000000000 000000000000000c 0000000000000001 c00000017e10bb40
      GPR08: 0000000000000000 8000080080040000 0000000000000000 0000000000000016
      GPR12: 0000000088adbe22 c00000000fffa800 c000000000001ba0 0000000000000000
      GPR16: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
      GPR20: 0000000000000000 0000000000000000 0000000000000000 c0000000008a5b70
      GPR24: c0000000008af938 c0000000009a28d8 c0000000009bb5dc c00000017e10bb40
      GPR28: c00000017e32a400 c00000017e10bc00 c00000017e32a400 c00000017e578e00
      NIP [c00000000002ea58] .fsl_pcie_check_link+0x88/0xf0
      LR [c00000000002eaf4] .fsl_indirect_read_config+0x34/0xb0
      Call Trace:
      [c00000017e10b720] [c00000017e10b7a0] 0xc00000017e10b7a0 (unreliable)
      [c00000017e10ba30] [c00000000002eaf4] .fsl_indirect_read_config+0x34/0xb0
      [c00000017e10bad0] [c00000000033aa08] .pci_bus_read_config_byte+0x88/0xd0
      [c00000017e10bb90] [c00000000088d708] .pci_apply_final_quirks+0x9c/0x18c
      [c00000017e10bc40] [c0000000000013dc] .do_one_initcall+0x5c/0x1f0
      [c00000017e10bcf0] [c00000000086ebac] .kernel_init_freeable+0x180/0x26c
      [c00000017e10bdb0] [c000000000001bbc] .kernel_init+0x1c/0x460
      [c00000017e10be30] [c000000000000880] .ret_from_kernel_thread+0x64/0xe4
      Instruction dump:
      38210310 2b800015 4fdde842 7c600026 5463fffe e8010010 7c0803a6 4e800020
      60000000 60000000 e92301d0 7c0004ac <80690f14> 0c030000 4c00012c 38210310
      ---[ end trace 7a8fe0cbccb7d992 ]---
      
      Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
      Signed-off-by: NKevin Hao <haokexin@gmail.com>
      Acked-by: NRoy Zang <tie-fei.zang@freescale.com>
      Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
      04aa99cd
    • Z
      powerpc/dts: Fix the dts for p1025rdb 36bit · 9aa171fb
      Zhicheng Fan 提交于
      Fix the following errors:
      
      Error: p1025rdb.dtsi:326.2-3 label or path, 'qe', not found
      Error: p1021si-post.dtsi:242.2-3 label or path, 'qe', not found
      FATAL ERROR: Syntax error parsing input tree
      Signed-off-by: NZhicheng Fan <B32736@freescale.com>
      Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
      9aa171fb
  2. 11 4月, 2013 4 次提交
  3. 10 4月, 2013 7 次提交
  4. 09 4月, 2013 1 次提交
  5. 04 4月, 2013 5 次提交
  6. 19 3月, 2013 4 次提交
  7. 16 3月, 2013 3 次提交
  8. 15 3月, 2013 1 次提交
  9. 14 3月, 2013 1 次提交
  10. 13 3月, 2013 9 次提交
  11. 06 3月, 2013 2 次提交