From: Hans de Goede <hansg@kernel.org>
To: Tj <tj.iam.tj@proton.me>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
"metux IT consult\"" <info@metux.net>,
platform-driver-x86@vger.kernel.org
Subject: Re: pcengines_apuv2: LEDs/Input fails since v6.18
Date: Tue, 17 Feb 2026 12:42:13 +0100 [thread overview]
Message-ID: <ef96006e-ca94-4525-9727-4a6011fde7e1@kernel.org> (raw)
In-Reply-To: <b553243c-9ec6-4016-9fd6-d33f549a3dad@proton.me>
Hi,
On 16-Feb-26 20:01, Tj wrote:
> Installed v6.19 recently and realised the heartbeat/network LED
> configuration I'd set wasn't working. Checking the log I see:
>
> kernel: platform gpio-keys-polled: deferred probe pending:
> gpio-keys-polled: failed to get gpio
> kernel: platform leds-gpio: deferred probe pending: leds-gpio: Failed to
> get GPIO 'apu2-leds/led-1'
>
> Looking through commits I found b8754092dfed4fc2fc
>
> platform/x86: pcengines-apuv2: Use static device properties
>
> After reverting it the LEDs operate as expected. This entered in v6.18
> so will affect it as well.
>
> In v6.17 I see:
>
> kernel: platform gpio-keys-polled: deferred probe pending:
> gpio-keys-polled: unable to claim gpio 0
>
> that is a slight variation on the v6.19 report. I've not pin-pointed the
> cause yet.
This should be fixed by this patch:
https://lore.kernel.org/linux-gpio/20260211085313.16792-1-bartosz.golaszewski@oss.qualcomm.com/
If possible, please give a kernel with that patch added a spin
and confirm if it fixes things.
Regards,
Hans
next prev parent reply other threads:[~2026-02-17 11:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 19:01 pcengines_apuv2: LEDs/Input fails since v6.18 Tj
2026-02-17 11:42 ` Hans de Goede [this message]
2026-02-17 15:25 ` Tj
2026-02-17 17:29 ` Dmitry Torokhov
2026-02-17 19:34 ` Tj
2026-02-18 9:55 ` Bartosz Golaszewski
2026-02-18 17:25 ` Dmitry Torokhov
2026-02-18 19:36 ` Dmitry Torokhov
2026-02-18 20:21 ` Bartosz Golaszewski
2026-02-18 21:04 ` Dmitry Torokhov
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=ef96006e-ca94-4525-9727-4a6011fde7e1@kernel.org \
--to=hansg@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=info@metux.net \
--cc=platform-driver-x86@vger.kernel.org \
--cc=tj.iam.tj@proton.me \
/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