From: ldewangan@nvidia•com (Laxman Dewangan)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH V1] arm: tegra: dma: not required to move requestor when stopping.
Date: Tue, 31 Jan 2012 16:32:48 +0530 [thread overview]
Message-ID: <4F27CA58.2020809@nvidia.com> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF178CB81E5F@HQMAIL01.nvidia.com>
On Wednesday 25 January 2012 02:27 AM, Stephen Warren wrote:
> Laxman Dewangan wrote at Tuesday, January 24, 2012 1:11 AM:
>> It is not require to move the requestor of dma to INVALID
>> option before stopping dma.
>>
>> Signed-off-by: Laxman Dewangan<ldewangan@nvidia•com>
> Acked-by: Stephen Warren<swarren@nvidia•com>
> Tested-by: Stephen Warren<swarren@nvidia•com>
>
> I know that Laxman has checked with the HW engineers, and they see no
> reason to do this. I was originally worried about hung FIFOs preventing
> an in-progress DMA from completely without the removed code, but according
> to HW, that isn't a concern.
>
Olaf,
Can it be applied if it is OK to you?
Thanks,
Laxman
next prev parent reply other threads:[~2012-01-31 11:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 8:10 [PATCH V1] arm: tegra: dma: not required to move requestor when stopping Laxman Dewangan
2012-01-24 20:57 ` Stephen Warren
2012-01-31 11:02 ` Laxman Dewangan [this message]
2012-02-01 7:09 ` Olof Johansson
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=4F27CA58.2020809@nvidia.com \
--to=ldewangan@nvidia$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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