On 05/29/2013 10:25:25 PM, Kevin Hao wrote:
On Tue, May 28, 2013 at 05:45:56PM -0500, Scott Wood wrote:
> On 05/16/2013 01:29:45 AM, Kevin Hao wrote:
> >All these boards use the same configuration file p1_p2_rdb_pc.h in
> >u-boot. So they have the same pci bus address set by the u-boot.
> >But in some of these boards the bus address set in dtb don't match
> >the one used by u-boot. And this will trigger a kernel bug in 32bit
> >kernel and cause the pci device malfunction. For example, on a
> >p2020rdb-pc board the u-boot use the 0xa0000000 as both bus address
> >and cpu address for one pci controller and then assign bus address
> >such as 0xa00004000 to some pci device. But in the kernel, the dtb
> >set the bus address to 0xe0000000 and the cpu address to 0xa0000000.
> >The kernel assumes mistakenly the assigned bus address 0xa0004000
> >in pci device is correct and keep it unchanged. This will definitely
> >cause the pci device malfunction. I have made two patches to fix
> >this in the pci subsystem.
> >http://patchwork.ozlabs.org/patch/243702/
> >http://patchwork.ozlabs.org/patch/243703/
> >
> >But I still think it makes sense to set these bus address to match
> >with the u-boot. This issue can't be reproduced on 36bit kernel.
> >But I also tweak the 36bit dtb for the above reason.
>
> IIRC the reason for using 0xe0000000 on all PCIe roots is to
> maximize the memory that is DMA-addressable without involving
> swiotlb.

OK, this sounds reasonable. I can drop the changes for the 36bit dts. But for the 32bit dts, it does cause the kernel hang on my p2020rdb-pca board when the SiI3132 driver probe the on-board pcie to sata controller. I think this issue should apply to all these boards if it has a pci device plugged. So we should
fix them ASAP.

Is this what your 3.11 patch fixes, or does it hang even with that?

> Maybe U-Boot should be fixed?

Maybe. I have created patch for kernel to detect this kind of mismatch between kernel and bootloader and then try to reassign the bus address automatically.
https://git.kernel.org/cgit/linux/kernel/git/helgaas/pci.git/commit/?h=next&id=cf4d1cf5ac5e7d2b886af6ed906ea0dcdc5b6855

So with this patch the kernel should just work even without this patch and the fix for u-boot. But this patch is just queued for 3.11. So I wish we can tweak the 32bit dts to accommodate to the u-boot now so that we can make sure that these boards are at least bootable for 3.10 or previous kernel. Then we can revert this patch for more DMA address space once the pci patch are
merged into mainline.

Is this a regression, or has it been broken for a while?

-Scott
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

Reply via email to