From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: "Radek Válko" <rvalko@lipicko.cz>
Cc: Andy Shevchenko <andy@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pinctrl: denverton: Fix probe of MFD-created platform device
Date: Thu, 27 Aug 2026 22:02:06 +0300 [thread overview]
Message-ID: <apCJrj-rORIXCIAQ@ashevche-desk.local> (raw)
In-Reply-To: <apCHdNBSQ7ub6lNi@ashevche-desk.local>
On Thu, Aug 27, 2026 at 09:52:40PM +0300, Andy Shevchenko wrote:
> On Thu, Aug 27, 2026 at 08:42:58PM +0200, Radek Válko wrote:
> > The Denverton pinctrl device can be instantiated by the Intel LPC
> > driver as an MFD platform device named "denverton-pinctrl".
> >
> > On affected systems the platform device does not carry the INTC3000
> > ACPI match data itself. As a result, intel_pinctrl_probe_by_hid()
> > fails to obtain the SoC data using device_get_match_data() and
> > returns -ENODATA.
> >
> > This results in:
> >
> > denverton-pinctrl denverton-pinctrl.0:
> > probe with driver denverton-pinctrl failed with error -61
> >
> > Denverton has a single fixed intel_pinctrl_soc_data instance. Pass
> > dnv_soc_data directly to intel_pinctrl_probe() instead of requiring
> > firmware match data for the MFD-created platform device.
> >
> > Tested on an Intel Atom C3000 system with LPC/eSPI device 8086:19dc.
> > Before this change the Denverton pinctrl driver failed to probe and
> > no Denverton GPIO controller was registered. After the change,
> > denverton-pinctrl.0 registers with pinmux and pinconf support and
> > exposes 154 GPIO lines.
>
> Thanks for the report.
>
> Can you instead try to replace device_get_match_data() in
> intel_pinctrl_probe_by_hid() by intel_pinctrl_get_soc_data() in the way how
> it's done in intel_pinctrl_probe_by_uid()?
Ah, it won't work as direct replacement. So, the intel_pinctrl_probe_by_hid()
should be modified accordingly. I will send a formal patch tomorrow.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2026-08-27 19:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 18:42 [PATCH] pinctrl: denverton: Fix probe of MFD-created platform device Radek Válko
2026-08-27 18:52 ` Andy Shevchenko
2026-08-27 19:02 ` Andy Shevchenko [this message]
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=apCJrj-rORIXCIAQ@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=linus.walleij@linaro.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 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.