From: Tony Lindgren <tony@atomide.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: Aaro Koskinen <aaro.koskinen@iki.fi>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, arnd@arndb.de
Subject: Re: [PATCH 1/2] ARM: OMAP1: DMA: Provide dma_slave_map to omap-dma
Date: Mon, 22 Feb 2016 10:02:01 -0800 [thread overview]
Message-ID: <20160222180201.GK13417@atomide.com> (raw)
In-Reply-To: <56CAB676.6080309@ti.com>
* Peter Ujfalusi <peter.ujfalusi@ti.com> [160221 23:19]:
> On 2016-02-19 23:44, Aaro Koskinen wrote:
> > On Tue, Feb 02, 2016 at 04:27:06PM +0200, Peter Ujfalusi wrote:
> >> OMAP1 can not boot in DT mode and to be able to clean up the driver
> >> regarding to the dmaengine API use (switching to the new API) the
> >> device/slave -> filter mapping needs to be provided to the omap-dma driver.
> >>
> >> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
> >
> > Acked-by: Aaro Koskinen <aaro.koskinen@iki.fi>
>
> Thanks Aaro,
>
> I believe the map covers all drivers using DMA, but in case I missed any we -
> you ;) will notice it as they will fail to get the DMA channels. This only
> going to be visible after I send the driver changes for 4.7. In such a case we
> will need to add the given device to the list.
Yeah makes sense. Applying both into omap-for-v4.6/soc thanks.
Tony
next prev parent reply other threads:[~2016-02-22 18:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 14:27 [PATCH 0/2] ARM: OMAP1/OMAP2+: Add dma_slave_map to board files Peter Ujfalusi
2016-02-02 14:27 ` [PATCH 1/2] ARM: OMAP1: DMA: Provide dma_slave_map to omap-dma Peter Ujfalusi
2016-02-19 18:07 ` Tony Lindgren
2016-02-19 21:44 ` Aaro Koskinen
2016-02-22 7:19 ` Peter Ujfalusi
2016-02-22 18:02 ` Tony Lindgren [this message]
2016-02-02 14:27 ` [PATCH 2/2] ARM: OMAP2+: DMA: Provide dma_slave_map to omap-dma for legacy boot 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=20160222180201.GK13417@atomide.com \
--to=tony@atomide.com \
--cc=aaro.koskinen@iki.fi \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@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).