From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: "Mika Westerberg" <mika.westerberg@linux.intel.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Linus Walleij" <linusw@kernel.org>,
"Radek Válko" <rvalko@lipicko.cz>
Subject: [PATCH v2 0/3] pinctrl: intel: retrieve pure platform driver data as well
Date: Thu, 3 Sep 2026 13:46:11 +0200 [thread overview]
Message-ID: <20260903114832.1996235-1-andriy.shevchenko@linux.intel.com> (raw)
The reported platform can't be enumerated as it misses driver data
associated with the firmware node. Instead we should use platform
driver data. This mini-series to make it happen.
Changes v2:
- constified parameter in intel_pinctrl_get_soc_data() (Mika)
- added tag (Radek)
Cc: Radek Válko <rvalko@lipicko.cz>
Andy Shevchenko (3):
pinctrl: intel: Move intel_pinctrl_get_soc_data() upper in the code
pinctrl: intel: constify parameter in intel_pinctrl_get_soc_data()
pinctrl: intel: Try to retrieve driver data for pure platform drivers
drivers/pinctrl/intel/pinctrl-intel.c | 51 ++++++++++++++++++---------
drivers/pinctrl/intel/pinctrl-intel.h | 2 +-
2 files changed, 36 insertions(+), 17 deletions(-)
--
2.50.1
next reply other threads:[~2026-09-03 11:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 11:46 Andy Shevchenko [this message]
2026-09-03 11:46 ` [PATCH v2 1/3] pinctrl: intel: Move intel_pinctrl_get_soc_data() upper in the code Andy Shevchenko
2026-09-03 11:46 ` [PATCH v2 2/3] pinctrl: intel: constify parameter in intel_pinctrl_get_soc_data() Andy Shevchenko
2026-09-03 11:46 ` [PATCH v2 3/3] pinctrl: intel: Try to retrieve driver data for pure platform drivers Andy Shevchenko
2026-09-03 11:54 ` [PATCH v2 0/3] pinctrl: intel: retrieve pure platform driver data as well Mika Westerberg
2026-09-03 13:43 ` 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=20260903114832.1996235-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=andy@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rvalko@lipicko.cz \
/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®