linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>
To: Ulf Hansson <ulf.hansson@linaro.org>, linux-pm@vger.kernel.org
Cc: Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Preventing PM from suspending device
Date: Mon, 9 Jan 2017 18:22:47 +0100	[thread overview]
Message-ID: <20170109172247.GI29854@bigcity.dyn.berto.se> (raw)

Hi Ulf and Linux PM,

I have a question regarding if a driver can signal to the PM core that 
it should not be suspended from its struct dev_pm_ops suspend callback.

My use-case is the sh_eth driver which I have added Wake-on-Lan support 
to, see [1]. In this driver I need to prevent the PM core to disable the 
module clock to the device if WoL is enabled. Currently I call 
clk_enable()/clk_disable() from the suspend/resume callbacks to modify 
the usage count of the clock to prevent the clock from being switched 
off by PM. This do not feel like the best solution to my problem.

Is there a more generic way to let PM know that I'm fine with the system 
being suspended and I have suspended as much as I can but I'm a wake up source 
so could please not switch of my clock and power domain?

1. https://marc.info/?l=linux-pm&m=148397620011501&w=2

-- 
Regards,
Niklas Söderlund

             reply	other threads:[~2017-01-09 17:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-09 17:22 Niklas Söderlund [this message]
2017-01-11 23:19 ` Preventing PM from suspending device Ulf Hansson
2017-01-12  7:10   ` Geert Uytterhoeven
2017-01-12 17:02     ` Ulf Hansson
2017-01-13  9:38       ` Geert Uytterhoeven
2017-03-29 19:28       ` Niklas Söderlund
2017-03-30 16:44         ` Ulf Hansson
2017-03-30 20:35           ` Niklas Söderlund
2017-10-18 11:35             ` Geert Uytterhoeven
2017-10-18 12:06               ` Ulf Hansson

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=20170109172247.GI29854@bigcity.dyn.berto.se \
    --to=niklas.soderlund@ragnatech.se \
    --cc=geert@linux-m68k.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=ulf.hansson@linaro.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 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).