lkml.org 
[lkml]   [2019]   [Nov]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH AUTOSEL 4.19 122/219] powerpc/44x/bamboo: Fix PCI range
    Date
    From: Benjamin Herrenschmidt <benh@kernel.crashing.org>

    [ Upstream commit 3cfb9ebe906b51f2942b1e251009bb251efd2ba6 ]

    The bamboo dts has a bug: it uses a non-naturally aligned range
    for PCI memory space. This isnt' supported by the code, thus
    causing PCI to break on this system.

    This is due to the fact that while the chip memory map has 1G
    reserved for PCI memory, it's only 512M aligned. The code doesn't
    know how to split that into 2 different PMMs and fails, so limit
    the region to 512M.

    Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
    Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
    Signed-off-by: Sasha Levin <sashal@kernel.org>
    ---
    arch/powerpc/boot/dts/bamboo.dts | 4 +++-
    1 file changed, 3 insertions(+), 1 deletion(-)

    diff --git a/arch/powerpc/boot/dts/bamboo.dts b/arch/powerpc/boot/dts/bamboo.dts
    index 538e42b1120d8..b5861fa3836c1 100644
    --- a/arch/powerpc/boot/dts/bamboo.dts
    +++ b/arch/powerpc/boot/dts/bamboo.dts
    @@ -268,8 +268,10 @@
    /* Outbound ranges, one memory and one IO,
    * later cannot be changed. Chip supports a second
    * IO range but we don't use it for now
    + * The chip also supports a larger memory range but
    + * it's not naturally aligned, so our code will break
    */
    - ranges = <0x02000000 0x00000000 0xa0000000 0x00000000 0xa0000000 0x00000000 0x40000000
    + ranges = <0x02000000 0x00000000 0xa0000000 0x00000000 0xa0000000 0x00000000 0x20000000
    0x02000000 0x00000000 0x00000000 0x00000000 0xe0000000 0x00000000 0x00100000
    0x01000000 0x00000000 0x00000000 0x00000000 0xe8000000 0x00000000 0x00010000>;

    --
    2.20.1
    \
     
     \ /
      Last update: 2019-11-22 07:24    [W:4.137 / U:0.004 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site