linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Mack <zonque@gmail.com>
To: Gururaja Hebbar <gururaja.hebbar@ti.com>
Cc: "Fernandes, Joel" <joelf@ti.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, 09 Oct 2013 09:38:49 +0200	[thread overview]
Message-ID: <52550809.2000407@gmail.com> (raw)
In-Reply-To: <5254F54D.7060709@ti.com>

Hi everyone,

On 09.10.2013 08:18, Gururaja Hebbar wrote:
> 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:

>>> 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. 

Me neighter :)

But on a general note, I wonder whether it's really worth discussing and
merging this patch. As I wrote in the cover letter, it's just a quick
and dirty solution that I copied from a very old BSP tree, and I know
that the file I'm patching here is going to be removed soon anyway.
Actually, the sooner the better.

(And the 'v3' in the subject is really my bad, sorry - I only sent one
version of this patch ever).

I can respin the patch on top of the proper driver once all the edma
bits have eventually been moved to drivers/dma. Is anyone continuing
Matt Porter's work on this?


Thanks,
Daniel

  reply	other threads:[~2013-10-09  7:38 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
2013-10-09  7:38         ` Daniel Mack [this message]
     [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=52550809.2000407@gmail.com \
    --to=zonque@gmail.com \
    --cc=balbi@ti.com \
    --cc=bigeasy@linutronix.de \
    --cc=dan.j.williams@intel.com \
    --cc=gururaja.hebbar@ti.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 \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).