From: Sekhar Nori <nsekhar-l0cyMroinI0@public.gmane.org>
To: Peter Ujfalusi <peter.ujfalusi-l0cyMroinI0@public.gmane.org>,
joelf-l0cyMroinI0@public.gmane.org,
vinod.koul-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org
Cc: davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.org,
linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
dmaengine-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH 0/3] ARM/dma: edma: Serve cyclic clients via high priority queue
Date: Mon, 28 Jul 2014 12:02:17 +0530 [thread overview]
Message-ID: <53D5EE71.3040707@ti.com> (raw)
In-Reply-To: <53D5E9CF.10706-l0cyMroinI0@public.gmane.org>
On Monday 28 July 2014 11:42 AM, Peter Ujfalusi wrote:
> On 07/08/2014 01:46 PM, Peter Ujfalusi wrote:
>> Hi,
>>
>> It is preferred that audio is served with the highest priority queue in order to
>> avoid delays in data transfer between memory and audio IP.
>>
>> The following series will add an API to arch code to assign a channel to a given
>> queue.
>> The default queue is changed from 0 (highest priority) to lowest priority.
This should not really change any performance behavior as everything at
highest priority is same as everything at lowest priority.
>> In the dmaengine driver we move the cyclic channel to queue0 (highest priority)
>> and move it back to default queue when the channel is terminated.
>
> ping?
For 1/3 and 2/3:
Acked-by: Sekhar Nori <nsekhar-l0cyMroinI0@public.gmane.org>
Vinod, can you take the series together with your tree (if you are happy
with the series, that is)? I don't have anything else queued for this
merge window.
Thanks,
Sekhar
WARNING: multiple messages have this Message-ID (diff)
From: nsekhar@ti.com (Sekhar Nori)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] ARM/dma: edma: Serve cyclic clients via high priority queue
Date: Mon, 28 Jul 2014 12:02:17 +0530 [thread overview]
Message-ID: <53D5EE71.3040707@ti.com> (raw)
In-Reply-To: <53D5E9CF.10706@ti.com>
On Monday 28 July 2014 11:42 AM, Peter Ujfalusi wrote:
> On 07/08/2014 01:46 PM, Peter Ujfalusi wrote:
>> Hi,
>>
>> It is preferred that audio is served with the highest priority queue in order to
>> avoid delays in data transfer between memory and audio IP.
>>
>> The following series will add an API to arch code to assign a channel to a given
>> queue.
>> The default queue is changed from 0 (highest priority) to lowest priority.
This should not really change any performance behavior as everything at
highest priority is same as everything at lowest priority.
>> In the dmaengine driver we move the cyclic channel to queue0 (highest priority)
>> and move it back to default queue when the channel is terminated.
>
> ping?
For 1/3 and 2/3:
Acked-by: Sekhar Nori <nsekhar@ti.com>
Vinod, can you take the series together with your tree (if you are happy
with the series, that is)? I don't have anything else queued for this
merge window.
Thanks,
Sekhar
WARNING: multiple messages have this Message-ID (diff)
From: Sekhar Nori <nsekhar@ti.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>, <joelf@ti.com>,
<vinod.koul@intel.com>
Cc: <linux@arm.linux.org.uk>, <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-omap@vger.kernel.org>,
<davinci-linux-open-source@linux.davincidsp.com>,
<dmaengine@vger.kernel.org>
Subject: Re: [PATCH 0/3] ARM/dma: edma: Serve cyclic clients via high priority queue
Date: Mon, 28 Jul 2014 12:02:17 +0530 [thread overview]
Message-ID: <53D5EE71.3040707@ti.com> (raw)
In-Reply-To: <53D5E9CF.10706@ti.com>
On Monday 28 July 2014 11:42 AM, Peter Ujfalusi wrote:
> On 07/08/2014 01:46 PM, Peter Ujfalusi wrote:
>> Hi,
>>
>> It is preferred that audio is served with the highest priority queue in order to
>> avoid delays in data transfer between memory and audio IP.
>>
>> The following series will add an API to arch code to assign a channel to a given
>> queue.
>> The default queue is changed from 0 (highest priority) to lowest priority.
This should not really change any performance behavior as everything at
highest priority is same as everything at lowest priority.
>> In the dmaengine driver we move the cyclic channel to queue0 (highest priority)
>> and move it back to default queue when the channel is terminated.
>
> ping?
For 1/3 and 2/3:
Acked-by: Sekhar Nori <nsekhar@ti.com>
Vinod, can you take the series together with your tree (if you are happy
with the series, that is)? I don't have anything else queued for this
merge window.
Thanks,
Sekhar
next prev parent reply other threads:[~2014-07-28 6:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-08 10:46 [PATCH 0/3] ARM/dma: edma: Serve cyclic clients via high priority queue Peter Ujfalusi
2014-07-08 10:46 ` Peter Ujfalusi
2014-07-08 10:46 ` Peter Ujfalusi
2014-07-08 10:46 ` [PATCH 2/3] ARM: edma: Add edma_assign_channel_eventq() to move channel to a give queue Peter Ujfalusi
2014-07-08 10:46 ` Peter Ujfalusi
2014-07-08 10:46 ` Peter Ujfalusi
2014-07-08 10:46 ` [PATCH 3/3] dma: edma: Serve cyclic (audio) channels with high priority queue Peter Ujfalusi
2014-07-08 10:46 ` Peter Ujfalusi
2014-07-08 10:46 ` Peter Ujfalusi
[not found] ` <1404816398-12338-1-git-send-email-peter.ujfalusi-l0cyMroinI0@public.gmane.org>
2014-07-08 10:46 ` [PATCH 1/3] ARM: edma: Set default queue to lowest priority Peter Ujfalusi
2014-07-08 10:46 ` Peter Ujfalusi
2014-07-08 10:46 ` Peter Ujfalusi
2014-07-28 6:12 ` [PATCH 0/3] ARM/dma: edma: Serve cyclic clients via high priority queue Peter Ujfalusi
2014-07-28 6:12 ` Peter Ujfalusi
2014-07-28 6:12 ` Peter Ujfalusi
[not found] ` <53D5E9CF.10706-l0cyMroinI0@public.gmane.org>
2014-07-28 6:32 ` Sekhar Nori [this message]
2014-07-28 6:32 ` Sekhar Nori
2014-07-28 6:32 ` Sekhar Nori
2014-07-28 11:34 ` Vinod Koul
2014-07-28 11:34 ` Vinod Koul
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=53D5EE71.3040707@ti.com \
--to=nsekhar-l0cymroini0@public.gmane.org \
--cc=davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.org \
--cc=dmaengine-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=joelf-l0cyMroinI0@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-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=peter.ujfalusi-l0cyMroinI0@public.gmane.org \
--cc=vinod.koul-ral2JQCrhuEAvxtiuMwx3w@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.