From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: <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: [PATCH 0/9] arm64: dts: ti: UDMAP and McASP support
Date: Tue, 12 Nov 2019 16:32:52 +0200 [thread overview]
Message-ID: <20191112143301.3168-1-peter.ujfalusi@ti.com> (raw)
Hi,
This series will enable DMA and adds the McASP nodes for am654 and j721e.
The DT bindings for DMA is not expected to change much anymore:
v5 of the UDMAP bindings patch is:
https://lore.kernel.org/lkml/20191111135330.8235-9-peter.ujfalusi@ti.com/
While adding the DMA support I have noticed few issues which is also fixed by
this series.
I have included the McASP nodes as well to have examples for other peripherals
on how he binding should be used.
I have been using this set on top of linux-next (the series is generated on top
of next-20191112) with audio on am654-evm and j721e evm + ivi card.
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-am654-main: Add McASP nodes
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-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 | 312 ++++++++++++++++--
.../boot/dts/ti/k3-j721e-mcu-wakeup.dtsi | 45 +++
arch/arm64/boot/dts/ti/k3-j721e.dtsi | 2 +-
5 files changed, 491 insertions(+), 36 deletions(-)
--
Peter
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
next reply other threads:[~2019-11-12 14:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 14:32 Peter Ujfalusi [this message]
2019-11-12 14:32 ` [PATCH 1/9] arm64: dts: ti: k3-am65-main: Correct main NAVSS representation Peter Ujfalusi
2019-11-12 14:32 ` [PATCH 2/9] arm64: dts: ti: k3-am65-main: Move secure proxy under cbass_main_navss Peter Ujfalusi
2019-11-12 14:32 ` [PATCH 3/9] arm64: dts: ti: k3-am65: DMA support Peter Ujfalusi
2019-11-12 14:32 ` [PATCH 4/9] arm64: dts: ti: k3-am654-main: Add McASP nodes Peter Ujfalusi
2019-11-12 14:32 ` [PATCH 5/9] arm64: dts: ti: k3-j721e: Correct the address for MAIN NAVSS Peter Ujfalusi
2019-11-12 14:32 ` [PATCH 6/9] arm64: dts: ti: k3-j721e-main: Correct main NAVSS representation Peter Ujfalusi
2019-11-12 14:32 ` [PATCH 7/9] arm64: dts: ti: k3-j721e-main: Move secure proxy and smmu under main_navss Peter Ujfalusi
2019-11-12 14:33 ` [PATCH 8/9] arm64: dts: ti: k3-j721e: DMA support Peter Ujfalusi
2019-11-12 14:33 ` [PATCH 9/9] arm64: dts: ti: k3-j721e-main: Add McASP nodes Peter Ujfalusi
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=20191112143301.3168-1-peter.ujfalusi@ti.com \
--to=peter.ujfalusi@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=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
all inboxes | Powered by JetHome®