All of lore.kernel.org
 help / color / mirror / Atom feed
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 v1 0/2] pinctrl: intel: retrieve pure platform driver data as well
Date: Mon, 31 Aug 2026 16:25:45 +0200	[thread overview]
Message-ID: <20260831142853.1995573-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.

Radek, please test at least the second patch and provide your formal
Tested-by tag in case it works as expected.

Cc: Radek Válko <rvalko@lipicko.cz>

Andy Shevchenko (2):
  pinctrl: intel: Move intel_pinctrl_get_soc_data() upper in the code
  pinctrl: intel: Try to retrieve driver data for pure platform drivers

 drivers/pinctrl/intel/pinctrl-intel.c | 47 +++++++++++++++++++--------
 1 file changed, 33 insertions(+), 14 deletions(-)

-- 
2.50.1


             reply	other threads:[~2026-08-31 14:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-31 14:25 Andy Shevchenko [this message]
2026-08-31 14:25 ` [PATCH v1 1/2] pinctrl: intel: Move intel_pinctrl_get_soc_data() upper in the code Andy Shevchenko
2026-08-31 14:25 ` [PATCH v1 2/2] pinctrl: intel: Try to retrieve driver data for pure platform drivers Andy Shevchenko
2026-09-01 10:24   ` Mika Westerberg
2026-09-01 10:27     ` Andy Shevchenko
2026-09-01 14:45       ` Radek Válko
2026-09-02 18:12   ` Radek Válko

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=20260831142853.1995573-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.