[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <701084d1-d03d-8890-c2ca-16daaa3085d6@gmail.com>
Date: Fri, 27 Mar 2020 09:17:03 -0700
From: Florian Fainelli <f.fainelli@...il.com>
To: Matthias Brugger <matthias.bgg@...il.com>,
Nicolas Saenz Julienne <nsaenzjulienne@...e.de>,
Rob Herring <robh+dt@...nel.org>,
Florian Fainelli <f.fainelli@...il.com>,
Ray Jui <rjui@...adcom.com>,
Scott Branden <sbranden@...adcom.com>,
bcm-kernel-feedback-list@...adcom.com
Cc: devicetree@...r.kernel.org, linux-rpi-kernel@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ARM: dts: bcm283x: Add cells encoding format to firmware
bus
On 3/27/2020 9:15 AM, Matthias Brugger wrote:
>
>
> On 26/03/2020 14:44, Nicolas Saenz Julienne wrote:
>> With the introduction of 55c7c0621078 ("ARM: dts: bcm283x: Fix vc4's
>> firmware bus DMA limitations") the firmware bus has to comply with
>> /soc's DMA limitations. Ultimately linking both buses to a same
>> dma-ranges property. The patch (and author) missed the fact that a bus'
>> #address-cells and #size-cells properties are not inherited, but set to
>> a fixed value which, in this case, doesn't match /soc's. This, although
>> not breaking Linux's DMA mapping functionality, generates ugly dtc
>> warnings.
>>
>> Fix the issue by adding the correct address and size cells properties
>> under the firmware bus.
>>
>> Fixes: 55c7c0621078 ("ARM: dts: bcm283x: Fix vc4's firmware bus DMA limitations")
>> Signed-off-by: Nicolas Saenz Julienne <nsaenzjulienne@...e.de>
>
> Reviewed-by: Matthias Brugger <mbrugger@...e.com>
Should this be squashed into "ARM: dts: bcm283x: Fix vc4's firmware bus
DMA limitations"? I have not gotten a response it has been accepted yet.
--
Florian
Powered by blists - more mailing lists