From: Laxman Dewangan <ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: "ccross-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org"
<ccross-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org>,
"olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org"
<olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org>,
"linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org"
<linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>,
"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [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-C7FfzLzN0UxDw2glCA4ptUEOCMrvLtNR@public.gmane.org>
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-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
> Acked-by: Stephen Warren<swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
> Tested-by: Stephen Warren<swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
>
> 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
WARNING: multiple messages have this Message-ID (diff)
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
WARNING: multiple messages have this Message-ID (diff)
From: Laxman Dewangan <ldewangan@nvidia.com>
To: Stephen Warren <swarren@nvidia.com>
Cc: "ccross@android.com" <ccross@android.com>,
"olof@lixom.net" <olof@lixom.net>,
"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [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: 12+ 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 8:10 ` Laxman Dewangan
2012-01-24 8:10 ` Laxman Dewangan
[not found] ` <1327392649-27605-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-01-24 20:57 ` Stephen Warren
2012-01-24 20:57 ` Stephen Warren
2012-01-24 20:57 ` Stephen Warren
[not found] ` <74CDBE0F657A3D45AFBB94109FB122FF178CB81E5F-C7FfzLzN0UxDw2glCA4ptUEOCMrvLtNR@public.gmane.org>
2012-01-31 11:02 ` Laxman Dewangan [this message]
2012-01-31 11:02 ` Laxman Dewangan
2012-01-31 11:02 ` Laxman Dewangan
[not found] ` <4F27CA58.2020809-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-02-01 7:09 ` Olof Johansson
2012-02-01 7:09 ` Olof Johansson
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-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
--cc=ccross-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org \
--cc=swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.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.