From: tixy@linaro.org (Jon Medhurst (Tixy))
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] dma: pl330: Fixes for DMA memcpy
Date: Thu, 13 Nov 2014 10:19:31 +0000 [thread overview]
Message-ID: <1415873971.1725.2.camel@linaro.org> (raw)
In-Reply-To: <20141112093158.GB24582@intel.com>
On Wed, 2014-11-12 at 15:01 +0530, Vinod Koul wrote:
> On Fri, Nov 07, 2014 at 06:05:16PM +0000, Jon Medhurst wrote:
> > This is a couple of patches I produced when trying to get dmatest to run
> > with the pl330 driver. The second one is actually a theoretical fix
> > because the FIFO on the platform I was using is too large for the tests
> > to hit the limit, but the datasheet says the device can lockup if all
> > the FIFO entries are exhausted, so it seems like a sensible precaution.
> >
> Applied, thanks
>
> Please ensure you use the right subsystem name for the patch header
I originally created the patch when working on Linux 3.14 and most
previous updates to the file used 'dma', I see now in recent versions
that the preferred name is 'dmaengine' (and matches the mailing list
name) so will use that in future.
BTW, though I was working on 3.14 I have retested the patches on a
3.18-rc
--
Tixy
WARNING: multiple messages have this Message-ID (diff)
From: "Jon Medhurst (Tixy)" <tixy@linaro.org>
To: Vinod Koul <vinod.koul@intel.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] dma: pl330: Fixes for DMA memcpy
Date: Thu, 13 Nov 2014 10:19:31 +0000 [thread overview]
Message-ID: <1415873971.1725.2.camel@linaro.org> (raw)
In-Reply-To: <20141112093158.GB24582@intel.com>
On Wed, 2014-11-12 at 15:01 +0530, Vinod Koul wrote:
> On Fri, Nov 07, 2014 at 06:05:16PM +0000, Jon Medhurst wrote:
> > This is a couple of patches I produced when trying to get dmatest to run
> > with the pl330 driver. The second one is actually a theoretical fix
> > because the FIFO on the platform I was using is too large for the tests
> > to hit the limit, but the datasheet says the device can lockup if all
> > the FIFO entries are exhausted, so it seems like a sensible precaution.
> >
> Applied, thanks
>
> Please ensure you use the right subsystem name for the patch header
I originally created the patch when working on Linux 3.14 and most
previous updates to the file used 'dma', I see now in recent versions
that the preferred name is 'dmaengine' (and matches the mailing list
name) so will use that in future.
BTW, though I was working on 3.14 I have retested the patches on a
3.18-rc
--
Tixy
next prev parent reply other threads:[~2014-11-13 10:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 18:05 [PATCH 0/2] dma: pl330: Fixes for DMA memcpy Jon Medhurst
2014-11-07 18:05 ` Jon Medhurst
2014-11-07 18:05 ` [PATCH 1/2] dma: pl330: Align DMA memcpy operations to MFIFO width Jon Medhurst
2014-11-07 18:05 ` Jon Medhurst
2014-11-07 18:05 ` [PATCH 2/2] dma: pl330: Limit MFIFO usage for memcpy to avoid exhausting entries Jon Medhurst
2014-11-07 18:05 ` Jon Medhurst
2014-11-12 9:31 ` [PATCH 0/2] dma: pl330: Fixes for DMA memcpy Vinod Koul
2014-11-12 9:31 ` Vinod Koul
2014-11-13 10:19 ` Jon Medhurst (Tixy) [this message]
2014-11-13 10:19 ` Jon Medhurst (Tixy)
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=1415873971.1725.2.camel@linaro.org \
--to=tixy@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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.