All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gururaja Hebbar <gururaja.hebbar@ti.com>
To: "Fernandes, Joel" <joelf@ti.com>
Cc: Daniel Mack <zonque@gmail.com>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"neumann@teufel.de" <neumann@teufel.de>,
	"bigeasy@linutronix.de" <bigeasy@linutronix.de>,
	"vinod.koul@intel.com" <vinod.koul@intel.com>,
	"dan.j.williams@intel.com" <dan.j.williams@intel.com>,
	"Balbi, Felipe" <balbi@ti.com>
Subject: Re: [PATCH v3] ARM: omap: edma: add suspend suspend/resume hooks
Date: Wed, 9 Oct 2013 11:48:53 +0530	[thread overview]
Message-ID: <5254F54D.7060709@ti.com> (raw)
In-Reply-To: <F774F8C9-0A8F-4B27-8607-874FB0901A78@ti.com>

On Wednesday 09 October 2013 11:33 AM, Fernandes, Joel wrote:
> Some temporary issues with my mua so forgive any artifacts in this email.
> 
> On Oct 9, 2013, at 12:14 AM, "Hebbar, Gururaja" <gururaja.hebbar@ti.com> wrote:
> 
>> On Wednesday 09 October 2013 09:58 AM, Joel Fernandes wrote:
>>> On 10/01/2013 10:04 AM, Daniel Mack wrote:
>>>> This patch makes the edma driver resume correctly after suspend. Tested
>>>> on an AM33xx platform with cyclic audio streams.
>>>>
>>>> The code was shamelessly taken from an ancient BSP tree.
>>>>
>>>> Signed-off-by: Daniel Mack <zonque@gmail.com>
>>>> ---
>>>> arch/arm/common/edma.c | 133 +++++++++++++++++++++++++++++++++++++++++++++++++
>>>> 1 file changed, 133 insertions(+)
>>
>> ..snip..
>> ..snip..
>>>
>>>> +        edma_cc[j]->context.ch_map =
>>>> +            kzalloc((sizeof(unsigned int) *
>>>> +                 edma_cc[j]->num_channels), GFP_KERNEL);
>>>> +        edma_cc[j]->context.que_num =
>>>> +            kzalloc((sizeof(unsigned int) * 8), GFP_KERNEL);
>>>
>>> Can these allocations be moved to the suspend path? For systems that don't
>>> suspend/resume even once, I feel we shouldn't allocate memory that we don't use.
>>> These allocations are better to do there.
>>
>> AFAIK, Suspend/resume should be quick. Allocating and deallocating on
>> every iterating would be useless and time consuming.
> 
> Nobody said allocate and deallocate on every iteration. Allocate once during the first suspend call and then don't have to allocate on subsequent calls.

I couldn't find any code which allocates parameters inside suspend.
Could you show me some code which does this?

> 
> As for suspend resume being quick, that argument can flipped the other way too, booting should be quick which is far more frequent than suspend/resume. Apart from the fact that we're not allocating useless memory we would never use.
> 
>>
>> Also this task is one time and quick.
> 
> Exactly.

i was referring to allocating in probe call..

> 
>>
>> Are there any systems (Linux based for now) which doesn't
>> suspend/resume? I believe the probability is very less.
> 
> Nobody talked about suspend/resume not being supported in Linux so not sure what your argument is here.

I meant linux systems which doesn't go to suspend and resume. Not
suspend/resume feature.

Also, I was referring to your 1st comment "... For systems that don't
suspend/resume even once, ...."


regards
Gururaja

> 
> regards,
> 
> -Joel
> 
>>
>> regards
>> Gururaja
>>
>>>
>>> -Joel
>>>
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>


  reply	other threads:[~2013-10-09  6:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-01 15:04 [PATCH v3] ARM: omap: edma: add suspend suspend/resume hooks Daniel Mack
2013-10-09  4:28 ` Joel Fernandes
2013-10-09  5:13   ` Gururaja Hebbar
2013-10-09  6:03     ` Fernandes, Joel
2013-10-09  6:18       ` Gururaja Hebbar [this message]
2013-10-09  7:38         ` Daniel Mack
     [not found]           ` <52550809.2000407-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-10-09 14:12             ` Joel Fernandes
2013-10-09 20:14               ` Joel Fernandes
     [not found]                 ` <5255B942.5000601-l0cyMroinI0@public.gmane.org>
2013-10-18 15:57                   ` Daniel Mack
     [not found]                     ` <52615A52.5070506-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-10-30  9:49                       ` Balaji T K
2013-10-09 14:19         ` Joel Fernandes

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=5254F54D.7060709@ti.com \
    --to=gururaja.hebbar@ti.com \
    --cc=balbi@ti.com \
    --cc=bigeasy@linutronix.de \
    --cc=dan.j.williams@intel.com \
    --cc=joelf@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=neumann@teufel.de \
    --cc=vinod.koul@intel.com \
    --cc=zonque@gmail.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.