From: Todd Poynor <tpoynor@mvista.com>
To: Vitaly Wool <vwool@ru.mvista.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: power management routines for NAND driver
Date: Thu, 11 Aug 2005 13:23:13 -0700 [thread overview]
Message-ID: <42FBB3B1.2080609@mvista.com> (raw)
In-Reply-To: <42FB5E72.2010402@ru.mvista.com>
Vitaly Wool wrote:
> I've looked through mtd code and found mtd_pm_callback that should be
> called to handle PM events. This callback should in turn call
> mtd->suspend/mtd->resume functions, if any. Therefore one evident way of
> PM stuff implementation for this NAND flash is to provide suspend/resume
> functions. However, pm_send (that calls mtd_pm_callback) is never called
> on ARM targets. So I doubt if it's appropriate to implement PM for the
> driver this way since it's looking somehow obsolete.
>
> Another way could be define the platform_device and provide its
> suspend/resume functions, that would be called during the power state
> transition.
Yes, the pm_send etc. APM-style calls are deprecated. The Linux Driver
Model PM hooks (incl. struct device_driver suspend/resume callbacks) are
the way to do it now. I floated a patch for another board in thread
"MTD PM Resume" in July that does approximately what you're talking
about, although calling existing Intel/Sharp CFI NOR flash routines. If
there's no objections to that style of PM support then I'll check it in.
--
Todd
next prev parent reply other threads:[~2005-08-11 20:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-11 14:19 power management routines for NAND driver Vitaly Wool
2005-08-11 15:09 ` Thomas Gleixner
2005-08-11 15:25 ` Vitaly Wool
2005-08-11 16:25 ` Thomas Gleixner
2005-08-12 15:11 ` Vitaly Wool
2005-08-12 15:36 ` Thomas Gleixner
2005-08-12 15:41 ` Thomas Gleixner
2005-08-12 15:55 ` Vitaly Wool
2005-08-12 16:16 ` Thomas Gleixner
2005-08-12 16:46 ` Vitaly Wool
2005-08-22 12:54 ` Vitaly Wool
2005-08-12 15:57 ` Vitaly Wool
2005-08-11 20:23 ` Todd Poynor [this message]
2005-08-11 20:31 ` Thomas Gleixner
2005-08-11 20:49 ` Vitaly Wool
2005-08-11 20:53 ` Thomas Gleixner
2005-08-11 20:55 ` Josh Boyer
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=42FBB3B1.2080609@mvista.com \
--to=tpoynor@mvista.com \
--cc=linux-mtd@lists.infradead.org \
--cc=vwool@ru.mvista.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.