linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lokesh Vutla <lokeshvutla@ti.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>, <t-kristo@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>
Subject: Re: [PATCH v3 0/9] arm64: dts: ti: UDMAP and McASP support
Date: Thu, 23 Jan 2020 18:05:22 +0530	[thread overview]
Message-ID: <7a34dbfa-426d-061e-cbf6-3da1d8bada65@ti.com> (raw)
In-Reply-To: <20200123114528.26552-1-peter.ujfalusi@ti.com>



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>

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(-)
> 

  parent reply	other threads:[~2020-01-23 12:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-23 11:45 [PATCH v3 0/9] arm64: dts: ti: UDMAP and McASP support Peter Ujfalusi
2020-01-23 11:45 ` [PATCH v3 1/9] arm64: dts: ti: k3-am65-main: Correct main NAVSS representation Peter Ujfalusi
2020-01-23 11:45 ` [PATCH v3 2/9] arm64: dts: ti: k3-am65-main: Move secure proxy under cbass_main_navss Peter Ujfalusi
2020-01-23 11:45 ` [PATCH v3 3/9] arm64: dts: ti: k3-am65: DMA support Peter Ujfalusi
2020-01-23 11:45 ` [PATCH v3 4/9] arm64: dts: ti: k3-j721e: Correct the address for MAIN NAVSS Peter Ujfalusi
2020-01-23 11:45 ` [PATCH v3 5/9] arm64: dts: ti: k3-j721e-main: Correct main NAVSS representation Peter Ujfalusi
2020-01-23 11:45 ` [PATCH v3 6/9] arm64: dts: ti: k3-j721e-main: Move secure proxy and smmu under main_navss Peter Ujfalusi
2020-01-23 11:45 ` [PATCH v3 7/9] arm64: dts: ti: k3-j721e: DMA support Peter Ujfalusi
2020-01-23 11:45 ` [PATCH v3 8/9] arm64: dts: ti: k3-am654-main: Add McASP nodes Peter Ujfalusi
2020-01-23 11:45 ` [PATCH v3 9/9] arm64: dts: ti: k3-j721e-main: " Peter Ujfalusi
2020-01-23 12:35 ` Lokesh Vutla [this message]
2020-01-24 11:32   ` [PATCH v3 0/9] arm64: dts: ti: UDMAP and McASP support Tero Kristo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7a34dbfa-426d-061e-cbf6-3da1d8bada65@ti.com \
    --to=lokeshvutla@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=nm@ti.com \
    --cc=peter.ujfalusi@ti.com \
    --cc=robh+dt@kernel.org \
    --cc=t-kristo@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).