From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Raag Jadav <raag.jadav@intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org
Cc: Andy Shevchenko <andy@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>
Subject: [PATCH v1 0/3] pinctrl: intel: Add generic platform driver
Date: Mon, 30 Oct 2023 16:10:31 +0200 [thread overview]
Message-ID: <20231030141034.3241674-1-andriy.shevchenko@linux.intel.com> (raw)
New Intel platforms one-by-one will be switching to use generic
approach for the pin control description in ACPI, hence this driver.
It depends on the patches in current Linux Next (will be part of
v6.7-rc1) and this series
https://lore.kernel.org/r/20231030120734.2831419-1-andriy.shevchenko@linux.intel.com.
Andy Shevchenko (3):
pinctrl: intel: Revert "Unexport intel_pinctrl_probe()"
pinctrl: intel: Add a generic Intel pin control platform driver
pinctrl: intel: Add ACPI ID to the generic platform driver
drivers/pinctrl/intel/Kconfig | 8 +
drivers/pinctrl/intel/Makefile | 1 +
.../pinctrl/intel/pinctrl-intel-platform.c | 224 ++++++++++++++++++
drivers/pinctrl/intel/pinctrl-intel.c | 5 +-
drivers/pinctrl/intel/pinctrl-intel.h | 3 +
5 files changed, 239 insertions(+), 2 deletions(-)
create mode 100644 drivers/pinctrl/intel/pinctrl-intel-platform.c
--
2.40.0.1.gaa8946217a0b
next reply other threads:[~2023-10-30 14:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 14:10 Andy Shevchenko [this message]
2023-10-30 14:10 ` [PATCH v1 1/3] pinctrl: intel: Revert "Unexport intel_pinctrl_probe()" Andy Shevchenko
2023-10-30 14:10 ` [PATCH v1 2/3] pinctrl: intel: Add a generic Intel pin control platform driver Andy Shevchenko
2023-11-03 5:57 ` Mika Westerberg
2023-11-13 12:12 ` Andy Shevchenko
2023-11-13 12:53 ` Mika Westerberg
2023-10-30 14:10 ` [PATCH v1 3/3] pinctrl: intel: Add ACPI ID to the generic " Andy Shevchenko
2023-11-01 6:32 ` Mika Westerberg
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=20231030141034.3241674-1-andriy.shevchenko@linux.intel.com \
--to=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=mika.westerberg@linux.intel.com \
--cc=raag.jadav@intel.com \
/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).