From: Aaro Koskinen <aaro.koskinen@iki.fi>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: vinod.koul@intel.com, dan.j.williams@intel.com,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org, tony@atomide.com,
stable@vger.kernel.org
Subject: Re: [PATCH] dmaengine: omap-dma: Fix dynamic lch_map alocation
Date: Mon, 2 Jan 2017 21:13:28 +0200 [thread overview]
Message-ID: <20170102191328.pssv24pzxhguyeby@raspberrypi-2.musicnaut.iki.fi> (raw)
In-Reply-To: <20170102100737.11927-1-peter.ujfalusi@ti.com>
Hi,
On Mon, Jan 02, 2017 at 12:07:37PM +0200, Peter Ujfalusi wrote:
> The original patch did not done what it was supposed to be doing and even
> worst it broke legacy boot (OMAP1).
>
> The lch_map size should be the number of available logical channels in sDMA
> and the od->dma_requests should store the number of available DMA request
> lines usable in sDMA.
>
> In legacy mode we do not have a way to get the DMA request count, in that
> case we use OMAP_SDMA_REQUESTS (127), despite the fact that OMAP1510 have
> only 31 DMA request line.
>
> Fixes: 2d1a9a946fae ("dmaengine: omap-dma: Dynamically allocate memory for lch_map")
> Reported-by: Aaro Koskinen <aaro.koskinen@iki.fi>
> Cc: stable@vger.kernel.org # v4.9
> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
Tested-by: Aaro Koskinen <aaro.koskinen@iki.fi>
Thanks,
A.
prev parent reply other threads:[~2017-01-02 19:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-02 10:07 [PATCH] dmaengine: omap-dma: Fix dynamic lch_map alocation Peter Ujfalusi
2017-01-02 10:07 ` Peter Ujfalusi
2017-01-02 10:09 ` Peter Ujfalusi
2017-01-02 10:09 ` Peter Ujfalusi
2017-01-02 10:09 ` Peter Ujfalusi
2017-01-02 10:21 ` Vinod Koul
2017-01-02 10:23 ` Peter Ujfalusi
2017-01-02 10:23 ` Peter Ujfalusi
2017-01-02 10:23 ` Peter Ujfalusi
2017-01-03 3:41 ` Vinod Koul
2017-01-02 19:13 ` Aaro Koskinen [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=20170102191328.pssv24pzxhguyeby@raspberrypi-2.musicnaut.iki.fi \
--to=aaro.koskinen@iki.fi \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@ti.com \
--cc=stable@vger.kernel.org \
--cc=tony@atomide.com \
--cc=vinod.koul@intel.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.