From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Andy Shevchenko <andy@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Paul Cercueil <paul@crapouillou.net>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: Re: [PATCH v3 00/17] pinctrl: intel: Use NOIRQ PM helper
Date: Fri, 10 Nov 2023 08:14:22 +0200 [thread overview]
Message-ID: <20231110061422.GI17433@black.fi.intel.com> (raw)
In-Reply-To: <20231030120734.2831419-1-andriy.shevchenko@linux.intel.com>
Hi Andy,
On Mon, Oct 30, 2023 at 02:07:17PM +0200, Andy Shevchenko wrote:
> Intel pin control drivers use NOIRQ variant of the PM callbacks.
> To make them smaller and less error prone against different
> kernel configurations (with possible defined but not used variables)
> switch to use NOIRQ PM helper.
>
> Changelog v3:
> - dropped applied patches
> - dropped MediaTek patch for now
> - split Intel patch to the series using suggection by Paul
>
> Changelog v2:
> - rewritten commit message in patch 1 (Rafael)
> - converted non-Intel pin control drivers as well
> - added couple of kinda related patches to use pm_ptr()
>
> Andy Shevchenko (17):
> pinctrl: intel: Provide Intel pin control wide PM ops structure
> pinctrl: alderlake: Switch to use Intel pin control PM ops
> pinctrl: broxton: Switch to use Intel pin control PM ops
> pinctrl: cannonlake: Switch to use Intel pin control PM ops
> pinctrl: cedarfork: Switch to use Intel pin control PM ops
> pinctrl: denverton: Switch to use Intel pin control PM ops
> pinctrl: elkhartlake: Switch to use Intel pin control PM ops
> pinctrl: emmitsburg: Switch to use Intel pin control PM ops
> pinctrl: geminilake: Switch to use Intel pin control PM ops
> pinctrl: icelake: Switch to use Intel pin control PM ops
> pinctrl: jasperlake: Switch to use Intel pin control PM ops
> pinctrl: lakefield: Switch to use Intel pin control PM ops
> pinctrl: lewisburg: Switch to use Intel pin control PM ops
> pinctrl: meteorlake: Switch to use Intel pin control PM ops
> pinctrl: sunrisepoint: Switch to use Intel pin control PM ops
> pinctrl: tigerlake: Switch to use Intel pin control PM ops
> pinctrl: intel: Make PM ops functions static
>
> drivers/pinctrl/intel/pinctrl-alderlake.c | 5 ++---
> drivers/pinctrl/intel/pinctrl-broxton.c | 5 ++---
> drivers/pinctrl/intel/pinctrl-cannonlake.c | 5 ++---
> drivers/pinctrl/intel/pinctrl-cedarfork.c | 5 ++---
> drivers/pinctrl/intel/pinctrl-denverton.c | 5 ++---
> drivers/pinctrl/intel/pinctrl-elkhartlake.c | 5 ++---
> drivers/pinctrl/intel/pinctrl-emmitsburg.c | 5 ++---
> drivers/pinctrl/intel/pinctrl-geminilake.c | 5 ++---
> drivers/pinctrl/intel/pinctrl-icelake.c | 5 ++---
> drivers/pinctrl/intel/pinctrl-intel.c | 14 +++++++-------
> drivers/pinctrl/intel/pinctrl-intel.h | 11 +----------
> drivers/pinctrl/intel/pinctrl-jasperlake.c | 5 ++---
> drivers/pinctrl/intel/pinctrl-lakefield.c | 5 ++---
> drivers/pinctrl/intel/pinctrl-lewisburg.c | 5 ++---
> drivers/pinctrl/intel/pinctrl-meteorlake.c | 5 ++---
> drivers/pinctrl/intel/pinctrl-sunrisepoint.c | 5 ++---
> drivers/pinctrl/intel/pinctrl-tigerlake.c | 5 ++---
> 17 files changed, 38 insertions(+), 62 deletions(-)
Nice! For the series,
Acked-by: Mika Westerberg <mika.westerberg@linux.intel.com>
next prev parent reply other threads:[~2023-11-10 17:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 12:07 [PATCH v3 00/17] pinctrl: intel: Use NOIRQ PM helper Andy Shevchenko
2023-10-30 12:07 ` [PATCH v3 01/17] pinctrl: intel: Provide Intel pin control wide PM ops structure Andy Shevchenko
2023-10-30 19:41 ` Jonathan Cameron
2023-10-30 19:43 ` Jonathan Cameron
2023-10-30 19:56 ` Andy Shevchenko
2023-10-30 12:07 ` [PATCH v3 02/17] pinctrl: alderlake: Switch to use Intel pin control PM ops Andy Shevchenko
2023-10-30 12:07 ` [PATCH v3 03/17] pinctrl: broxton: " Andy Shevchenko
2023-10-30 12:07 ` [PATCH v3 04/17] pinctrl: cannonlake: " Andy Shevchenko
2023-10-30 12:07 ` [PATCH v3 05/17] pinctrl: cedarfork: " Andy Shevchenko
2023-10-30 12:07 ` [PATCH v3 06/17] pinctrl: denverton: " Andy Shevchenko
2023-10-30 12:07 ` [PATCH v3 07/17] pinctrl: elkhartlake: " Andy Shevchenko
2023-10-30 12:07 ` [PATCH v3 08/17] pinctrl: emmitsburg: " Andy Shevchenko
2023-10-30 12:07 ` [PATCH v3 09/17] pinctrl: geminilake: " Andy Shevchenko
2023-10-30 12:07 ` [PATCH v3 10/17] pinctrl: icelake: " Andy Shevchenko
2023-10-30 12:07 ` [PATCH v3 11/17] pinctrl: jasperlake: " Andy Shevchenko
2023-10-30 12:07 ` [PATCH v3 12/17] pinctrl: lakefield: " Andy Shevchenko
2023-10-30 12:07 ` [PATCH v3 13/17] pinctrl: lewisburg: " Andy Shevchenko
2023-10-30 12:07 ` [PATCH v3 14/17] pinctrl: meteorlake: " Andy Shevchenko
2023-10-30 12:07 ` [PATCH v3 15/17] pinctrl: sunrisepoint: " Andy Shevchenko
2023-10-30 12:07 ` [PATCH v3 16/17] pinctrl: tigerlake: " Andy Shevchenko
2023-10-30 12:07 ` [PATCH v3 17/17] pinctrl: intel: Make PM ops functions static Andy Shevchenko
2023-11-02 12:57 ` [PATCH v3 00/17] pinctrl: intel: Use NOIRQ PM helper Linus Walleij
2023-11-10 6:14 ` Mika Westerberg [this message]
2023-11-13 11:35 ` Andy Shevchenko
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=20231110061422.GI17433@black.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@crapouillou.net \
/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