From: viresh.kumar@st.com (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-pm Query] Power Management Device Suspend/ Resume
Date: Wed, 28 Sep 2011 08:55:56 +0530 [thread overview]
Message-ID: <4E8293C4.5090009@st.com> (raw)
In-Reply-To: <CAO1yOm2pbApTwa0gj3Q9RsC1mxNGGirxm6FzaDC7zbgjHdkKDw@mail.gmail.com>
Hi,
Can somebody please help us understand suspend/resume.
It would be a great help, even if you can point us to some earlier fruitful
discussion.
--
viresh
On 9/22/2011 4:19 PM, Deepak Sikri wrote:
> Hi,
>
> We are in the process of adding Suspend/ Resume call backs for the devices on SPEAr platform.
> The platform makes use of various power domains which could be turned off (during suspend, implying
> the devices in those power domains lose their context).
>
> *There are certain queries*.
>
> *Query- 1*. Suppose my platform has a ADC driver under char framework, which internally uses the
> DMA driver (channels). Now, ADC driver can be used by other kernel drivers or directly from user application.
>
> *1. a.* What are the expectations from the suspend and resume routines of both the devices, DMA & ADC ?
>
> */-- Given that few of the options are/*
> */1.a.1. On suspend,/*
> In ADC suspend function: ADC releases all the DMA channels, latches its registers; and
> DMA suspend function: DMA does nothing except for lataching of registers if required.
>
> */1.a.2. On suspend, /*
> ADC suspend function: ADC just latches its registers and stops R/W through DMA, no DMA channel release;
> DMA suspend function: DMA halts its operating channels, and latches its registers if required.
>
> */1.a.3 Some other alternative/*
> *//*
>
> *1.b* Will the suspend resume for the dependent drivers follow sequencing, i.e. Suspend of ADC followed by
> Suspend of DMA? (Assume both of these devices are hooked on to Platform bus, given that ADC uses DMA)
>
> *Query-2*
>
> 2.1 The user space threads freeze first followed by kernel space. In case the user space process issues a a system
> call (lets assume an ioctl system call), how will the user space thread respond in case of suspend to ram?
>
> 2.2 Will the kernel thread running on behalf of user space process complete the ioctl call OR
> freeze upon in the middle of execution?
>
> *Query-3*
> **
> Are there any modalities w.r.t latching and restoring the contents at the driver level ?
> that is: Should this process be handled at drier level or platform specific code can also handle this
>
>
> Thanks & Regards
> Deepak
WARNING: multiple messages have this Message-ID (diff)
From: Viresh Kumar <viresh.kumar@st.com>
To: "linux-pm@lists.linux-foundation.org"
<linux-pm@lists.linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
"Koul, Vinod" <vinod.koul@intel.com>,
Linus Walleij <linus.walleij@linaro.org>
Cc: Deepak Sikri <deepak.sikri79@gmail.com>,
Shiraz HASHIM <shiraz.hashim@st.com>,
Deepak SIKRI <deepak.sikri@st.com>,
Vipin KUMAR <vipin.kumar@st.com>,
Vipul Kumar SAMAR <vipulkumar.samar@st.com>,
Pratyush ANAND <pratyush.anand@st.com>,
Rajeev KUMAR <rajeev-dlh.kumar@st.com>,
Armando VISCONTI <armando.visconti@st.com>,
Bhupesh SHARMA <bhupesh.sharma@st.com>,
Amit VIRDI <Amit.VIRDI@st.com>,
Vincenzo FRASCINO <Vincenzo.FRASCINO@st.com>
Subject: Re: [linux-pm Query] Power Management Device Suspend/ Resume
Date: Wed, 28 Sep 2011 08:55:56 +0530 [thread overview]
Message-ID: <4E8293C4.5090009@st.com> (raw)
In-Reply-To: <CAO1yOm2pbApTwa0gj3Q9RsC1mxNGGirxm6FzaDC7zbgjHdkKDw@mail.gmail.com>
Hi,
Can somebody please help us understand suspend/resume.
It would be a great help, even if you can point us to some earlier fruitful
discussion.
--
viresh
On 9/22/2011 4:19 PM, Deepak Sikri wrote:
> Hi,
>
> We are in the process of adding Suspend/ Resume call backs for the devices on SPEAr platform.
> The platform makes use of various power domains which could be turned off (during suspend, implying
> the devices in those power domains lose their context).
>
> *There are certain queries*.
>
> *Query- 1*. Suppose my platform has a ADC driver under char framework, which internally uses the
> DMA driver (channels). Now, ADC driver can be used by other kernel drivers or directly from user application.
>
> *1. a.* What are the expectations from the suspend and resume routines of both the devices, DMA & ADC ?
>
> */-- Given that few of the options are/*
> */1.a.1. On suspend,/*
> In ADC suspend function: ADC releases all the DMA channels, latches its registers; and
> DMA suspend function: DMA does nothing except for lataching of registers if required.
>
> */1.a.2. On suspend, /*
> ADC suspend function: ADC just latches its registers and stops R/W through DMA, no DMA channel release;
> DMA suspend function: DMA halts its operating channels, and latches its registers if required.
>
> */1.a.3 Some other alternative/*
> *//*
>
> *1.b* Will the suspend resume for the dependent drivers follow sequencing, i.e. Suspend of ADC followed by
> Suspend of DMA? (Assume both of these devices are hooked on to Platform bus, given that ADC uses DMA)
>
> *Query-2*
>
> 2.1 The user space threads freeze first followed by kernel space. In case the user space process issues a a system
> call (lets assume an ioctl system call), how will the user space thread respond in case of suspend to ram?
>
> 2.2 Will the kernel thread running on behalf of user space process complete the ioctl call OR
> freeze upon in the middle of execution?
>
> *Query-3*
> **
> Are there any modalities w.r.t latching and restoring the contents at the driver level ?
> that is: Should this process be handled at drier level or platform specific code can also handle this
>
>
> Thanks & Regards
> Deepak
next parent reply other threads:[~2011-09-28 3:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAO1yOm2pbApTwa0gj3Q9RsC1mxNGGirxm6FzaDC7zbgjHdkKDw@mail.gmail.com>
2011-09-28 3:25 ` Viresh Kumar [this message]
2011-09-28 3:25 ` [linux-pm Query] Power Management Device Suspend/ Resume Viresh Kumar
2011-09-28 3:42 ` Vinod Koul
2011-09-28 3:42 ` Vinod Koul
2011-09-28 6:45 ` Viresh Kumar
2011-09-28 6:45 ` Viresh Kumar
2011-09-28 8:54 ` Vinod Koul
2011-09-28 8:54 ` Vinod Koul
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=4E8293C4.5090009@st.com \
--to=viresh.kumar@st.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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.