From: Raag Jadav <raag.jadav@intel.com>
To: Jarkko Nikula <jarkko.nikula@linux.intel.com>
Cc: u.kleine-koenig@pengutronix.de, mika.westerberg@linux.intel.com,
andriy.shevchenko@linux.intel.com, linux-pwm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 2/2] pwm: lpss: drop redundant runtime PM handles
Date: Wed, 14 Feb 2024 11:32:24 +0200 [thread overview]
Message-ID: <ZcyIqEFufO39WMqn@black.fi.intel.com> (raw)
In-Reply-To: <91bbea2c-b6f7-48cf-b540-83c73750d1d2@linux.intel.com>
On Wed, Feb 14, 2024 at 09:04:09AM +0200, Jarkko Nikula wrote:
> On 2/12/24 08:10, Raag Jadav wrote:
> > We no longer need empty runtime PM handles for PCI devices after commit
> > c5eb1190074c ("PCI / PM: Allow runtime PM without callback functions").
> > Drop them and let PCI core take care of power state transitions.
> >
> > Signed-off-by: Raag Jadav <raag.jadav@intel.com>
> > Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > ---
> > drivers/pwm/pwm-lpss-pci.c | 22 ----------------------
> > 1 file changed, 22 deletions(-)
> >
> Will this patch cause a regression if applied without your another patch to
> the drivers/pci/pci-driver.c?
>
> https://lore.kernel.org/linux-pci/20240212063233.5599-1-raag.jadav@intel.com/
Yes, I'll send out a v2 with updated commit message after the PCI
one is accepted.
Raag
next prev parent reply other threads:[~2024-02-14 9:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 6:10 [PATCH v1 0/2] LPSS PWM cleanups Raag Jadav
2024-02-12 6:10 ` [PATCH v1 1/2] pwm: lpss: use devm_pm_runtime_enable() helper Raag Jadav
2024-02-12 6:10 ` [PATCH v1 2/2] pwm: lpss: drop redundant runtime PM handles Raag Jadav
2024-02-14 7:04 ` Jarkko Nikula
2024-02-14 9:32 ` Raag Jadav [this message]
2024-02-12 7:14 ` [PATCH v1 0/2] LPSS PWM cleanups Uwe Kleine-König
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=ZcyIqEFufO39WMqn@black.fi.intel.com \
--to=raag.jadav@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=u.kleine-koenig@pengutronix.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).