[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <75b1798fbef0f941a7c58b91583d62dff6384671.camel@pengutronix.de>
Date: Fri, 21 Jun 2024 16:45:52 +0200
From: Philipp Zabel <p.zabel@...gutronix.de>
To: Prabhakar <prabhakar.csengg@...il.com>, Geert Uytterhoeven
<geert+renesas@...der.be>
Cc: linux-kernel@...r.kernel.org, linux-renesas-soc@...r.kernel.org,
Fabrizio Castro <fabrizio.castro.jz@...esas.com>, Lad Prabhakar
<prabhakar.mahadev-lad.rj@...renesas.com>
Subject: Re: [RFC PATCH] reset: Add devm_reset_control_deassert helper
Hi,
On Do, 2024-04-18 at 14:26 +0100, Prabhakar wrote:
> From: Lad Prabhakar <prabhakar.mahadev-lad.rj@...renesas.com>
>
> A typical code pattern for reset_control_deassert() call is to call it in
> the _probe function and to call reset_control_assert() both from _probe
> error path and from _remove function.
>
> Add helper function to replace this bolierplate piece of code. Calling
> devm_reset_control_deassert() removes the need for calling
> reset_control_assert() both in the probe()'s error path and in the
> remove() function.
>
> Suggested-by: Geert Uytterhoeven <geert+renesas@...der.be>
> Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@...renesas.com>
I'm not sure this aligns well with the intended use of devres for
resource acquisition and release.
Note how there is no devm_clk_prepare_enable, devm_regulator_enable,
devm_gpiod_set_value_cansleep, or devm_pwm_enable either.
I've sent an alternative suggestion that adds
devm_reset_control_get..._deasserted calls, similarly to the existing
devm_clk_get..._enabled calls. Please let me know what you think.
regards
Philipp
Powered by blists - more mailing lists