All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Mack <zonque@gmail.com>
To: Nishanth Menon <nm@ti.com>,
	Gururaja Hebbar <gururaja.hebbar@ti.com>,
	joelf@ti.com, Vaibhav Bedia <vaibhav.bedia@gmail.com>
Cc: Matt Porter <matt@ohporter.com>,
	balajitk@ti.com, s.neumann@raumfeld.com,
	Sekhar Nori <nsekhar@ti.com>, Russ Dill <Russ.Dill@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	Linux ARM Kernel List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v4] ARM: omap: edma: add suspend suspend/resume hooks
Date: Thu, 07 Nov 2013 16:36:42 +0100	[thread overview]
Message-ID: <527BB38A.1060609@gmail.com> (raw)
In-Reply-To: <527BAF63.10308@ti.com>

On 11/07/2013 04:18 PM, Nishanth Menon wrote:
> Tested this on a vendor V3.12 tag based kernel:
> 
> Test patch: http://pastebin.com/AmnktQ7B
> test: echo -n "1">/sys/power/pm_print_times; rtcwake -d /dev/rtc0 -m
> mem -s 5
> 
> 
> with the current patch: http://pastebin.com/RujarRLV
> suspend_late and resume_early: http://pastebin.com/RujarRLV

These two are identical.

> suspend_noirq and resume_noirq: http://pastebin.com/nKfbm7Mj

And I can't see any difference between this one and the first one,
except for slightly different timings. Am I missing anything?

> one needs to be careful of the sequence - donot forget that
> omap_device also does stuff in the background to every SoC device in
> noirq - sequence is paramount. you would want to ensure edma is saving
> after every single dependent device is done with it's stuff and
> guarenteed to never request any further transaction, and resume is
> done before any of the dependent devices need edma. but edma is also a
> peripheral that omap_device and generic runtime pm framework deals
> with - so ensure sequences consider that as well.

So, what would you say which sequence is correct then? :)


Thanks,
Daniel




WARNING: multiple messages have this Message-ID (diff)
From: zonque@gmail.com (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4] ARM: omap: edma: add suspend suspend/resume hooks
Date: Thu, 07 Nov 2013 16:36:42 +0100	[thread overview]
Message-ID: <527BB38A.1060609@gmail.com> (raw)
In-Reply-To: <527BAF63.10308@ti.com>

On 11/07/2013 04:18 PM, Nishanth Menon wrote:
> Tested this on a vendor V3.12 tag based kernel:
> 
> Test patch: http://pastebin.com/AmnktQ7B
> test: echo -n "1">/sys/power/pm_print_times; rtcwake -d /dev/rtc0 -m
> mem -s 5
> 
> 
> with the current patch: http://pastebin.com/RujarRLV
> suspend_late and resume_early: http://pastebin.com/RujarRLV

These two are identical.

> suspend_noirq and resume_noirq: http://pastebin.com/nKfbm7Mj

And I can't see any difference between this one and the first one,
except for slightly different timings. Am I missing anything?

> one needs to be careful of the sequence - donot forget that
> omap_device also does stuff in the background to every SoC device in
> noirq - sequence is paramount. you would want to ensure edma is saving
> after every single dependent device is done with it's stuff and
> guarenteed to never request any further transaction, and resume is
> done before any of the dependent devices need edma. but edma is also a
> peripheral that omap_device and generic runtime pm framework deals
> with - so ensure sequences consider that as well.

So, what would you say which sequence is correct then? :)


Thanks,
Daniel

  reply	other threads:[~2013-11-07 15:36 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-30 20:21 [PATCH v4] ARM: omap: edma: add suspend suspend/resume hooks Daniel Mack
2013-10-30 20:21 ` Daniel Mack
2013-10-31 22:25 ` Vaibhav Bedia
2013-10-31 22:25   ` Vaibhav Bedia
2013-11-06 17:36   ` Joel Fernandes
2013-11-06 17:36     ` Joel Fernandes
2013-11-07 13:30     ` Gururaja Hebbar
2013-11-07 13:30       ` Gururaja Hebbar
2013-11-07 13:32       ` Daniel Mack
2013-11-07 13:32         ` Daniel Mack
2013-11-07 15:18         ` Nishanth Menon
2013-11-07 15:18           ` Nishanth Menon
2013-11-07 15:36           ` Daniel Mack [this message]
2013-11-07 15:36             ` Daniel Mack
2013-11-07 15:48             ` Nishanth Menon
2013-11-07 15:48               ` Nishanth Menon
2013-11-07 20:42               ` Vaibhav Bedia
2013-11-07 20:42                 ` Vaibhav Bedia
2013-11-15 14:39                 ` Nishanth Menon
2013-11-15 14:39                   ` Nishanth Menon
2013-11-17 22:09                   ` Daniel Mack
2013-11-17 22:09                     ` Daniel Mack
2013-11-07 20:34     ` Vaibhav Bedia
2013-11-07 20:34       ` Vaibhav Bedia
2013-11-07 15:34 ` Nishanth Menon
2013-11-07 15:34   ` Nishanth Menon
2013-11-07 16:27   ` Grygorii Strashko
2013-11-07 16:27     ` Grygorii Strashko
2013-11-07 20:46     ` Vaibhav Bedia
2013-11-07 20:46       ` Vaibhav Bedia
2013-11-07 16:34 ` Joel Fernandes
2013-11-07 16:34   ` Joel Fernandes
2013-11-07 16:49   ` Joel Fernandes
2013-11-07 16:49     ` Joel Fernandes
2013-11-07 17:37   ` Daniel Mack
2013-11-07 17:37     ` Daniel Mack
2013-11-07 21:39     ` Joel Fernandes
2013-11-07 21:39       ` Joel Fernandes
2013-11-08  4:07     ` Gururaja Hebbar
2013-11-08  4:07       ` Gururaja Hebbar
2013-11-08  7:51       ` Daniel Mack
2013-11-08  7:51         ` Daniel Mack

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=527BB38A.1060609@gmail.com \
    --to=zonque@gmail.com \
    --cc=Russ.Dill@ti.com \
    --cc=balajitk@ti.com \
    --cc=gururaja.hebbar@ti.com \
    --cc=joelf@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=matt@ohporter.com \
    --cc=nm@ti.com \
    --cc=nsekhar@ti.com \
    --cc=s.neumann@raumfeld.com \
    --cc=vaibhav.bedia@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.