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" <linusw@kernel.org>,
"Radek Válko" <rvalko@lipicko.cz>
Subject: Re: [PATCH v2 0/3] pinctrl: intel: retrieve pure platform driver data as well
Date: Thu, 3 Sep 2026 13:54:24 +0200 [thread overview]
Message-ID: <20260903115424.GN106095@black.igk.intel.com> (raw)
In-Reply-To: <20260903114832.1996235-1-andriy.shevchenko@linux.intel.com>
On Thu, Sep 03, 2026 at 01:46:11PM +0200, Andy Shevchenko wrote:
> 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
>
Acked-by: Mika Westerberg <mika.westerberg@linux.intel.com>
next prev parent reply other threads:[~2026-09-03 11:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 11:46 [PATCH v2 0/3] pinctrl: intel: retrieve pure platform driver data as well Andy Shevchenko
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 ` Mika Westerberg [this message]
2026-09-03 13:43 ` [PATCH v2 0/3] pinctrl: intel: retrieve pure platform driver data as well 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=20260903115424.GN106095@black.igk.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=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=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