[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y8lwGKzWqxfQfG0j@google.com>
Date: Thu, 19 Jan 2023 16:30:16 +0000
From: Lee Jones <lee@...nel.org>
To: Jeremy Kerr <jk@...econstruct.com.au>
Cc: devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Arnd Bergmann <arnd@...db.de>,
Philipp Zabel <p.zabel@...gutronix.de>,
Mark Brown <broonie@...nel.org>
Subject: Re: [PATCH v4 2/2] mfd: syscon: allow reset control for syscon
devices
On Thu, 05 Jan 2023, Jeremy Kerr wrote:
> Simple syscon devices may require deassertion of a reset signal in order
> to access their register set. Rather than requiring a custom driver to
> implement this, we can use the generic "resets" specifiers to link a
> reset line to the syscon.
>
> This change adds an optional reset line to the syscon device
> description, and deasserts the reset if detected.
>
> Signed-off-by: Jeremy Kerr <jk@...econstruct.com.au>
> Reviewed-by: Arnd Bergmann <arnd@...db.de>
>
> ---
> v2:
> * do reset control in the early of_syscon_register() path, rather than
> the platform device init, which isn't used.
> v3:
> * use a direct reset_control_deassert rather than handling in the
> regmap
> v4:
> * collapse unnecessary `else` block
> ---
> drivers/mfd/syscon.c | 27 +++++++++++++++++++++------
> 1 file changed, 21 insertions(+), 6 deletions(-)
Applied, thanks
--
Lee Jones [李琼斯]
Powered by blists - more mailing lists