Hi Thomas, thanks for working on this!
Also thanks to Andy for excellent guidance on the series. On Tue, May 6, 2025 at 5:21 PM Thomas Richard <[email protected]> wrote: > This is the fifth version of this series, addressing the few remaining > issues identified by Andy. > > Signed-off-by: Thomas Richard <[email protected]> Looks good to me! > Thomas Richard (12): > gpiolib: add support to register sparse pin range > pinctrl: remove extern specifier for functions in machine.h > pinctrl: core: add devm_pinctrl_register_mappings() > gpio: aggregator: move GPIO forwarder allocation in a dedicated function > gpio: aggregator: refactor the code to add GPIO desc in the forwarder > gpio: aggregator: refactor the forwarder registration part > gpio: aggregator: update gpiochip_fwd_setup_delay_line() parameters > gpio: aggregator: export symbols of the GPIO forwarder library > gpio: aggregator: handle runtime registration of gpio_desc in > gpiochip_fwd > gpio: aggregator: add possibility to attach data to the forwarder > lib/string_choices: Add str_input_output() helper > pinctrl: Add pin controller driver for AAEON UP boards > Most heavy commits are in the GPIO subsystem, once the nitpicks are addressed in v6, Bartosz do you want to create an immutable branch for this and merge into your for-next and see how it works, if all is good I can perhaps pull the same branch into pinctrl as well. If this is stressful I can do the same operation in pinctrl instead so you can just pull it to GPIO from my tree. Yours, Linus Walleij
