From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.4 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 02D45C33CAF for ; Thu, 23 Jan 2020 12:36:24 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id C3A2324673 for ; Thu, 23 Jan 2020 12:36:23 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=ti.com header.i=@ti.com header.b="g268vZIO" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726204AbgAWMgX (ORCPT ); Thu, 23 Jan 2020 07:36:23 -0500 Received: from lelv0143.ext.ti.com ([198.47.23.248]:55956 "EHLO lelv0143.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726170AbgAWMgX (ORCPT ); Thu, 23 Jan 2020 07:36:23 -0500 Received: from lelv0266.itg.ti.com ([10.180.67.225]) by lelv0143.ext.ti.com (8.15.2/8.15.2) with ESMTP id 00NCaGxm109845; Thu, 23 Jan 2020 06:36:16 -0600 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1579782976; bh=IkR/GADZB2jJ/si7sIhU8tzPE9tlQ6+SnBIdU/caiXQ=; h=Subject:To:CC:References:From:Date:In-Reply-To; b=g268vZIOeiS+P7SMSmdYyI/s0tMl8DMdhp8Ax99oM/P1TRIKGF+lIv8buw21OUcsh Lhj786PA3Wt6WvGQfXUElMTeK4gKFVsuMb0S02OIOp6aoAxAgbLEzlRRSSo4pqSxVV xvbsLi+jbUt5f0CbvF53L9IUslP4vmF13nOK5rcA= Received: from DFLE100.ent.ti.com (dfle100.ent.ti.com [10.64.6.21]) by lelv0266.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 00NCaFLd039644 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Thu, 23 Jan 2020 06:36:16 -0600 Received: from DFLE112.ent.ti.com (10.64.6.33) by DFLE100.ent.ti.com (10.64.6.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1847.3; Thu, 23 Jan 2020 06:36:15 -0600 Received: from fllv0039.itg.ti.com (10.64.41.19) by DFLE112.ent.ti.com (10.64.6.33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1847.3 via Frontend Transport; Thu, 23 Jan 2020 06:36:15 -0600 Received: from [10.24.69.20] (ileax41-snat.itg.ti.com [10.172.224.153]) by fllv0039.itg.ti.com (8.15.2/8.15.2) with ESMTP id 00NCaCxp130706; Thu, 23 Jan 2020 06:36:13 -0600 Subject: Re: [PATCH v3 0/9] arm64: dts: ti: UDMAP and McASP support To: Peter Ujfalusi , , CC: , , , , References: <20200123114528.26552-1-peter.ujfalusi@ti.com> From: Lokesh Vutla Message-ID: <7a34dbfa-426d-061e-cbf6-3da1d8bada65@ti.com> Date: Thu, 23 Jan 2020 18:05:22 +0530 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-Version: 1.0 In-Reply-To: <20200123114528.26552-1-peter.ujfalusi@ti.com> Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 Sender: devicetree-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org 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 Thanks and regards, Lokesh > > 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(-) >