Re: [PATCH RFC 1/2] of: property: fw_devlink: Follow GPIO nexus maps

From: Bartosz Golaszewski

Date: Wed Sep 02 2026 - 08:36:32 EST


On Wed, 2 Sep 2026 13:41:39 +0200, Ernest Van Hoecke
<ernestvanhoecke@xxxxxxxxx> said:
> From: Ernest Van Hoecke <ernest.vanhoecke@xxxxxxxxxxx>
>
> GPIO consumers use of_parse_phandle_with_args_map() to resolve specifiers
> through gpio-map properties. fw_devlink instead parses GPIO properties as

Unlike PWM, there's no such thing as "gpio-map" properties.

> direct phandle references, so it records the nexus node as the supplier
> rather than the mapped GPIO provider.
>

Can you point me to an example? I'm not sure what a nexus node is in the
context of GPIO.

> A nexus is a translation node, not the GPIO provider, and need not be
> populated as a device. The resulting fwnode link can therefore remain
> unresolved and indefinitely defer the consumer while
> device_links_check_suppliers() waits for the nexus.
>
> Use the map-aware parser for all supported GPIO property spellings. This
> makes fw_devlink resolve the same provider as the GPIO consumer API. Direct
> GPIO references continue to work because the map-aware parser returns the
> original provider when no gpio-map property is present.
>
> Add OF unittest coverage for mapped and direct GPIO suppliers, including
> the deprecated singular and unprefixed property spellings.
>

Since this is a fix that we may want to backport, the unit tests should go in
a separate, follow-up commit.

Bart