From: Tero Kristo <t-kristo@ti.com>
To: Vignesh Raghavendra <vigneshr@ti.com>, Nishanth Menon <nm@ti.com>
Cc: Rob Herring <robh+dt@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] arm64: dts: ti: k3-am65-mcu: Add DMA entries for ADC
Date: Fri, 20 Mar 2020 11:07:26 +0200 [thread overview]
Message-ID: <5b1703e1-b1af-6436-3e46-34e27f7c8ada@ti.com> (raw)
In-Reply-To: <20200312092823.21587-2-vigneshr@ti.com>
On 12/03/2020 11:28, Vignesh Raghavendra wrote:
> Add DMA entries for ADC nodes
>
> Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
Queued both patches towards 5.7, thanks.
-Tero
> ---
> arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi b/arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi
> index 92629cbdc184..e85498f0dd05 100644
> --- a/arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi
> @@ -82,6 +82,9 @@ tscadc0: tscadc@40200000 {
> assigned-clocks = <&k3_clks 0 2>;
> assigned-clock-rates = <60000000>;
> clock-names = "adc_tsc_fck";
> + dmas = <&mcu_udmap 0x7100>,
> + <&mcu_udmap 0x7101 >;
> + dma-names = "fifo0", "fifo1";
>
> adc {
> #io-channel-cells = <1>;
> @@ -97,6 +100,9 @@ tscadc1: tscadc@40210000 {
> assigned-clocks = <&k3_clks 1 2>;
> assigned-clock-rates = <60000000>;
> clock-names = "adc_tsc_fck";
> + dmas = <&mcu_udmap 0x7102>,
> + <&mcu_udmap 0x7103>;
> + dma-names = "fifo0", "fifo1";
>
> adc {
> #io-channel-cells = <1>;
>
--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
prev parent reply other threads:[~2020-03-20 9:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 9:28 [PATCH 1/2] arm64: dts: ti: k3-am65-main: Add DMA entries for main_spi0 Vignesh Raghavendra
2020-03-12 9:28 ` [PATCH 2/2] arm64: dts: ti: k3-am65-mcu: Add DMA entries for ADC Vignesh Raghavendra
2020-03-20 9:07 ` Tero Kristo [this message]
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=5b1703e1-b1af-6436-3e46-34e27f7c8ada@ti.com \
--to=t-kristo@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=vigneshr@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).