[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c65d6a94-b5c2-e2e4-6fdb-b7982d291e01@linaro.org>
Date: Wed, 29 Jun 2022 19:44:11 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Geert Uytterhoeven <geert+renesas@...der.be>,
Vignesh Raghavendra <vigneshr@...com>,
Sergey Shtylyov <s.shtylyov@....ru>,
Wolfram Sang <wsa+renesas@...g-engineering.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@...renesas.com>,
Miquel Raynal <miquel.raynal@...tlin.com>,
Richard Weinberger <richard@....at>
Cc: Mark Brown <broonie@...nel.org>, linux-mtd@...ts.infradead.org,
linux-renesas-soc@...r.kernel.org, linux-spi@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 5/7] memory: renesas-rpc-if: Move resource acquisition to
.probe()
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@...der.be>
This looks like a fix, so how about putting it as first in the series,
so backporting is easy/automatic? Plus a fixes tag?
Best regards,
Krzysztof
Powered by blists - more mailing lists