Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Subject: Re: [PATCH v3 0/9] arm64: dts: ti: UDMAP and McASP support
To:     Lokesh Vutla <lokeshvutla@ti.com>,
        Peter Ujfalusi <peter.ujfalusi@ti.com>, <nm@ti.com>
CC:     <robh+dt@kernel.org>, <mark.rutland@arm.com>,
        <linux-arm-kernel@lists.infradead.org>,
        <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
References: <20200123114528.26552-1-peter.ujfalusi@ti.com>
 <7a34dbfa-426d-061e-cbf6-3da1d8bada65@ti.com>
From:   Tero Kristo <t-kristo@ti.com>
Message-ID: <14b395ad-122a-3331-5b89-b6f8708bc00e@ti.com>
Date:   Fri, 24 Jan 2020 13:32:50 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.2.2
MIME-Version: 1.0
In-Reply-To: <7a34dbfa-426d-061e-cbf6-3da1d8bada65@ti.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On 23/01/2020 14:35, Lokesh Vutla wrote:
> 
> 
> On 23/01/20 5:15 PM, Peter Ujfalusi wrote:
>> Hi,
>>
>> Changes since v2:
>> - Correct unit addresses for the McASP nodes
>> - Remove unit address and label for MAIN and MCU NAVSS
>>
>> Changes since v1:
>> - rebased on ti-k3-next
>> - Corrected j721e mcu_udma node: s/udmap/dma-controller
>> - Moved the two McASP node patch at the end of the series
>>
>> The ringacc and UDMA documentation and drivers are in next-20200122.
>>
>> While adding the DMA support I have noticed few issues which is also fixed by
>> this series.
> 
> 
> Entire series looks good to me.
> 
> Reviewed-by: Lokesh Vutla <lokeshvutla@ti.com>

Queued the whole series towards 5.6, thanks.

-Tero

> 
>>
>> Tero: I have included the McASP nodes as well to have examples for other
>> peripherals on how he binding should be used.
>> The patches for the McASP driver is not in next, but they are only internal
>> driver changes (and Kconfig), not adding new DT dependencies.
>> Since the McASP is disabled in SoC dtsi due to board level configuration needs
>> it is not going to erroneously probe drivers.
>>
>> It is up to you if you pick them or not, but I believe they serve a safe and
>> nice example how the dma binding should be used for UDMA.
>>
>> Regards,
>> Peter
>> ---
>> Peter Ujfalusi (9):
>>    arm64: dts: ti: k3-am65-main: Correct main NAVSS representation
>>    arm64: dts: ti: k3-am65-main: Move secure proxy under cbass_main_navss
>>    arm64: dts: ti: k3-am65: DMA support
>>    arm64: dts: ti: k3-j721e: Correct the address for MAIN NAVSS
>>    arm64: dts: ti: k3-j721e-main: Correct main NAVSS representation
>>    arm64: dts: ti: k3-j721e-main: Move secure proxy and smmu under
>>      main_navss
>>    arm64: dts: ti: k3-j721e: DMA support
>>    arm64: dts: ti: k3-am654-main: Add McASP nodes
>>    arm64: dts: ti: k3-j721e-main: Add McASP nodes
>>
>>   arch/arm64/boot/dts/ti/k3-am65-main.dtsi      | 122 ++++++-
>>   arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi       |  46 +++
>>   arch/arm64/boot/dts/ti/k3-j721e-main.dtsi     | 313 ++++++++++++++++--
>>   .../boot/dts/ti/k3-j721e-mcu-wakeup.dtsi      |  45 +++
>>   arch/arm64/boot/dts/ti/k3-j721e.dtsi          |   2 +-
>>   5 files changed, 491 insertions(+), 37 deletions(-)
>>

--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki