From: Paul Walmsley <paul@pwsan.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: Tony Lindgren <tony@atomide.com>,
robh+dt@kernel.org, Tero Kristo <t-kristo@ti.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 10/11] ARM: DRA7: hwmod: Add data for McASP1/2/4/5/6/7/8
Date: Thu, 3 Mar 2016 15:38:28 +0000 (UTC) [thread overview]
Message-ID: <alpine.DEB.2.02.1603031532130.32459@utopia.booyaka.com> (raw)
In-Reply-To: <56D81C49.6030706@ti.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 735 bytes --]
Hi Péter,
On Thu, 3 Mar 2016, Peter Ujfalusi wrote:
> On 03/01/2016 07:01 PM, Paul Walmsley wrote:
> >>> 3. Can McASP1,2,3 bus-master onto the L3? If so, then there should be
> >>> "dra7xx_mcasp1__l3_main_1"-style links to indicate this.
> >>
> >> I need to check this, but I don't think McASP1,2,3 can be bus-master onto L3.
> >
> > OK. When you get back, maybe doublecheck this - it looks to me from
> > SPRUHZ6 that McASP1-3 have built-in DMA controllers.
>
> They are only targets on L3. Not sure about the built-in DMA controller
OK thanks. I took a closer look at SPRUHZ6E and I think I was mistaken
about those blocks having DMA controllers. So you can ignore this part
of my comments :-)
- Paul
WARNING: multiple messages have this Message-ID (diff)
From: Paul Walmsley <paul-DWxLp4Yu+b8AvxtiuMwx3w@public.gmane.org>
To: Peter Ujfalusi <peter.ujfalusi-l0cyMroinI0@public.gmane.org>
Cc: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
Tero Kristo <t-kristo-l0cyMroinI0@public.gmane.org>,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 10/11] ARM: DRA7: hwmod: Add data for McASP1/2/4/5/6/7/8
Date: Thu, 3 Mar 2016 15:38:28 +0000 (UTC) [thread overview]
Message-ID: <alpine.DEB.2.02.1603031532130.32459@utopia.booyaka.com> (raw)
In-Reply-To: <56D81C49.6030706-l0cyMroinI0@public.gmane.org>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 735 bytes --]
Hi Péter,
On Thu, 3 Mar 2016, Peter Ujfalusi wrote:
> On 03/01/2016 07:01 PM, Paul Walmsley wrote:
> >>> 3. Can McASP1,2,3 bus-master onto the L3? If so, then there should be
> >>> "dra7xx_mcasp1__l3_main_1"-style links to indicate this.
> >>
> >> I need to check this, but I don't think McASP1,2,3 can be bus-master onto L3.
> >
> > OK. When you get back, maybe doublecheck this - it looks to me from
> > SPRUHZ6 that McASP1-3 have built-in DMA controllers.
>
> They are only targets on L3. Not sure about the built-in DMA controller
OK thanks. I took a closer look at SPRUHZ6E and I think I was mistaken
about those blocks having DMA controllers. So you can ignore this part
of my comments :-)
- Paul
WARNING: multiple messages have this Message-ID (diff)
From: paul@pwsan.com (Paul Walmsley)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 10/11] ARM: DRA7: hwmod: Add data for McASP1/2/4/5/6/7/8
Date: Thu, 3 Mar 2016 15:38:28 +0000 (UTC) [thread overview]
Message-ID: <alpine.DEB.2.02.1603031532130.32459@utopia.booyaka.com> (raw)
In-Reply-To: <56D81C49.6030706@ti.com>
Hi P?ter,
On Thu, 3 Mar 2016, Peter Ujfalusi wrote:
> On 03/01/2016 07:01 PM, Paul Walmsley wrote:
> >>> 3. Can McASP1,2,3 bus-master onto the L3? If so, then there should be
> >>> "dra7xx_mcasp1__l3_main_1"-style links to indicate this.
> >>
> >> I need to check this, but I don't think McASP1,2,3 can be bus-master onto L3.
> >
> > OK. When you get back, maybe doublecheck this - it looks to me from
> > SPRUHZ6 that McASP1-3 have built-in DMA controllers.
>
> They are only targets on L3. Not sure about the built-in DMA controller
OK thanks. I took a closer look at SPRUHZ6E and I think I was mistaken
about those blocks having DMA controllers. So you can ignore this part
of my comments :-)
- Paul
next prev parent reply other threads:[~2016-03-03 15:38 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 14:50 [PATCH 00/11] ARM: DTS/clk: DRA7 family: enable eDMA and audio updates Peter Ujfalusi
2016-02-25 14:50 ` Peter Ujfalusi
2016-02-25 14:50 ` Peter Ujfalusi
2016-02-25 14:50 ` [PATCH 01/11] ARM: DTS: dra7: Move the sDMA crossbar node under l4_cfg/scm Peter Ujfalusi
2016-02-25 14:50 ` Peter Ujfalusi
2016-02-25 14:50 ` Peter Ujfalusi
2016-02-25 14:50 ` [PATCH 02/11] ARM: DRA7: hwmod: Add data for eDMA tpcc, tptc0, tptc1 Peter Ujfalusi
2016-02-25 14:50 ` Peter Ujfalusi
2016-02-25 14:50 ` Peter Ujfalusi
2016-03-01 8:55 ` Paul Walmsley
2016-03-01 8:55 ` Paul Walmsley
2016-03-01 8:55 ` Paul Walmsley
2016-02-25 14:50 ` [PATCH 03/11] ARM: DTS: dra7: Enable eDMA Peter Ujfalusi
2016-02-25 14:50 ` Peter Ujfalusi
2016-02-25 14:50 ` Peter Ujfalusi
2016-02-25 14:50 ` [PATCH 04/11] ARM: DTS: dra7: Use eDMA and add DAT port address for McASP3 Peter Ujfalusi
2016-02-25 14:50 ` Peter Ujfalusi
2016-02-25 14:50 ` Peter Ujfalusi
2016-02-25 14:50 ` [PATCH 05/11] ARM: DTS: dra7-evm: Enable AFIFO use " Peter Ujfalusi
2016-02-25 14:50 ` Peter Ujfalusi
2016-02-25 14:50 ` Peter Ujfalusi
2016-02-25 14:50 ` [PATCH 06/11] ARM: DTS: dra72-evm: " Peter Ujfalusi
2016-02-25 14:50 ` Peter Ujfalusi
2016-02-25 14:50 ` Peter Ujfalusi
2016-02-25 14:50 ` [PATCH 07/11] ARM: DTS: am57xx-beagle-x15: Move clkout2 source selection to codec node Peter Ujfalusi
2016-02-25 14:50 ` Peter Ujfalusi
2016-02-25 14:50 ` Peter Ujfalusi
2016-02-25 14:50 ` [PATCH 08/11] ARM: DTS: am57xx-beagle-x15: Enable AFIFO use for McASP3 Peter Ujfalusi
2016-02-25 14:50 ` Peter Ujfalusi
2016-02-25 14:50 ` Peter Ujfalusi
2016-02-25 14:50 ` [PATCH 09/11] ARM: clk: dra7xx: Correct mcasp8_ahclkx_mux name Peter Ujfalusi
2016-02-25 14:50 ` Peter Ujfalusi
2016-02-25 14:50 ` Peter Ujfalusi
2016-02-25 14:50 ` [PATCH 10/11] ARM: DRA7: hwmod: Add data for McASP1/2/4/5/6/7/8 Peter Ujfalusi
2016-02-25 14:50 ` Peter Ujfalusi
2016-02-25 14:50 ` Peter Ujfalusi
2016-03-01 9:11 ` Paul Walmsley
2016-03-01 9:11 ` Paul Walmsley
2016-03-01 16:43 ` Peter Ujfalusi
2016-03-01 16:43 ` Peter Ujfalusi
2016-03-01 16:43 ` Peter Ujfalusi
2016-03-01 17:01 ` Paul Walmsley
2016-03-01 17:01 ` Paul Walmsley
2016-03-03 11:13 ` Peter Ujfalusi
2016-03-03 11:13 ` Peter Ujfalusi
2016-03-03 11:13 ` Peter Ujfalusi
2016-03-03 15:38 ` Paul Walmsley [this message]
2016-03-03 15:38 ` Paul Walmsley
2016-03-03 15:38 ` Paul Walmsley
2016-02-25 14:50 ` [PATCH 11/11] ARM: DTS: dra7: Add nodes " Peter Ujfalusi
2016-02-25 14:50 ` Peter Ujfalusi
2016-02-25 14:50 ` 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=alpine.DEB.2.02.1603031532130.32459@utopia.booyaka.com \
--to=paul@pwsan.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@ti.com \
--cc=robh+dt@kernel.org \
--cc=t-kristo@ti.com \
--cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.