mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Subject: Re: [PATCH v1 1/1] platform/x86/intel: atomisp2: Replace deprecated UNIVERSAL_DEV_PM_OPS()
Date: Tue, 9 Apr 2024 20:15:57 +0300	[thread overview]
Message-ID: <ZhV3zUgZjAMUZ0yD@smile.fi.intel.com> (raw)
In-Reply-To: <609652ce-0336-4d69-ab79-f84c8a8506e5@redhat.com>

On Mon, Apr 08, 2024 at 06:20:03PM +0200, Hans de Goede wrote:
> On 4/3/24 12:55 PM, Andy Shevchenko wrote:

...

> As mentioned in the description of DEFINE_RUNTIME_DEV_PM_OPS()
> DEFINE_RUNTIME_DEV_PM_OPS() is NOT a 1:1 replacement for
> UNIVERSAL_DEV_PM_OPS() specifically it uses pm_runtime_force_suspend() /
> pm_runtime_force_resume() .

Right.

> Specifically pm_runtime_force_suspend() may NOT get set (and in this case
> will not set) needs_force_resume skipping a resume + suspend cycle
> after a system suspend, which is a problem if firmware has touched
> the state of the device during the suspend/resume cycle since the device
> may now actually be left powered on.

I see, thanks for explaining me this. So this driver is kinda very special.
Still the old question, can we get rid altogether of these atomisp "drivers"
in PDx86?

> It seems there is no direct replacement for UNIVERSAL_DEV_PM_OPS()
> without a behavior change.

Correct.

...

Btw, have you seen a few cleanup patches against AtomISP v2 by me?

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2024-04-09 17:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-03 10:55 Andy Shevchenko
2024-04-08 16:20 ` Hans de Goede
2024-04-09 17:15   ` Andy Shevchenko [this message]
2024-04-10 11:00     ` Hans de Goede

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=ZhV3zUgZjAMUZ0yD@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=hdegoede@redhat.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.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

all inboxes | Powered by JetHome®