Hi Krzysztof, On Wed, Jun 29, 2022 at 7:44 PM Krzysztof Kozlowski <krzysztof.kozlowski@xxxxxxxxxx> wrote: > On 27/06/2022 17:31, Geert Uytterhoeven wrote: > > While the acquired resources are tied to the lifetime of the RPC-IF core > > device (through the use of managed resource functions), the actual > > resource acquisition is triggered from the HyperBus and SPI child > > drivers. Due to this mismatch, unbinding and rebinding the child > > drivers manually fails with -EBUSY: > > > > # echo rpc-if-hyperflash > /sys/bus/platform/drivers/rpc-if-hyperflash/unbind > > # echo rpc-if-hyperflash > /sys/bus/platform/drivers/rpc-if-hyperflash/bind > > rpc-if ee200000.spi: can't request region for resource [mem 0xee200000-0xee2001ff] > > rpc-if-hyperflash: probe of rpc-if-hyperflash failed with error -16 > > > > Fix this by moving all resource acquisition to the core driver's probe > > routine. > > > > Signed-off-by: Geert Uytterhoeven <geert+renesas@xxxxxxxxx> > > This looks like a fix, so how about putting it as first in the series, > so backporting is easy/automatic? Unfortunately that is not as simple as it sounds, as this really depends on patch 4. I agree patches 1-3 could be moved later, if you think it is worthwhile. > Plus a fixes tag? It's been like that since forever. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds