From: Viresh Kumar <viresh.kumar@st.com>
To: <pavel@ucw.cz>, "Rafael J. Wysocki" <rjw@sisk.pl>, <len.brown@intel.com>
Cc: "linux-pm@lists.linux-foundation.org"
<linux-pm@lists.linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Shiraz HASHIM <shiraz.hashim@st.com>,
Armando VISCONTI <armando.visconti@st.com>,
Vipin KUMAR <vipin.kumar@st.com>,
deepak sikri <deepak.sikri@st.com>,
Vipul Kumar SAMAR <vipulkumar.samar@st.com>,
Amit VIRDI <amit.virdi@st.com>,
Rajeev KUMAR <rajeev-dlh.kumar@st.com>,
Pratyush ANAND <pratyush.anand@st.com>,
Mirko GARDI <mirko.gardi@st.com>,
Vincenzo FRASCINO <Vincenzo.FRASCINO@st.com>,
Bhupesh SHARMA <bhupesh.sharma@st.com>
Subject: Query: When will drv->poweroff() called
Date: Mon, 6 Feb 2012 11:25:12 +0530 [thread overview]
Message-ID: <4F2F6B40.6070308@st.com> (raw)
Hi Guys,
Sorry for asking this silly question, but i couldn't locate much
help for it in documentation, so asking it.
We were testing hibernation for SPEAr13xx SoC family, based on
ARM Cortex a9.
I observed that poweroff() callback of individual drivers are not
getting called at all, while we test hibernate.
I tried to go through the code to see what happened. It looked like
there should be call to hibernation_set_ops() for platforms that are
willing to get a call to poweroff() for their drivers. Otherwise
shutdown of the busses gets called, which is a completely different path.
There are many drivers today, that are registering poweroff() from dev_pm_ops
but are not doing bus specific shutdown stuff.
Even i tried to look for hibernation_set_ops() in kernel, and only acpi
code is calling it. I didn't understood how other ARM Sub-Arch's are handling
this.
Thanks in advance :)
--
viresh
next reply other threads:[~2012-02-06 5:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-06 5:55 Viresh Kumar [this message]
2012-02-06 12:07 ` Query: When will drv->poweroff() called Rafael J. Wysocki
2012-02-07 4:19 ` Viresh Kumar
2012-02-16 15:16 ` viresh kumar
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=4F2F6B40.6070308@st.com \
--to=viresh.kumar@st.com \
--cc=Vincenzo.FRASCINO@st.com \
--cc=amit.virdi@st.com \
--cc=armando.visconti@st.com \
--cc=bhupesh.sharma@st.com \
--cc=deepak.sikri@st.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mirko.gardi@st.com \
--cc=pavel@ucw.cz \
--cc=pratyush.anand@st.com \
--cc=rajeev-dlh.kumar@st.com \
--cc=rjw@sisk.pl \
--cc=shiraz.hashim@st.com \
--cc=vipin.kumar@st.com \
--cc=vipulkumar.samar@st.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