[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <4e8f3cd6-de4f-492a-b1c0-8e0a356d2954@app.fastmail.com>
Date: Tue, 18 Jun 2024 16:43:45 +0200
From: "Arnd Bergmann" <arnd@...db.de>
To: "Peter Griffin" <peter.griffin@...aro.org>, "Lee Jones" <lee@...nel.org>,
"Krzysztof Kozlowski" <krzk@...nel.org>,
"Alim Akhtar" <alim.akhtar@...sung.com>
Cc: linux-arm-kernel@...ts.infradead.org, linux-samsung-soc@...r.kernel.org,
linux-kernel@...r.kernel.org, "Tudor Ambarus" <tudor.ambarus@...aro.org>,
André Draszik <andre.draszik@...aro.org>,
"Saravana Kannan" <saravanak@...gle.com>,
"William McVicker" <willmcvicker@...gle.com>,
"Sam Protsenko" <semen.protsenko@...aro.org>, kernel-team@...roid.com
Subject: Re: [PATCH 1/2] mfd: syscon: add of_syscon_register_regmap() API
On Fri, Jun 14, 2024, at 16:04, Peter Griffin wrote:
> The of_syscon_register_regmap() API allows an externally created regmap
> to be registered with syscon. This regmap can then be returned to client
> drivers using the syscon_regmap_lookup_by_phandle() APIs.
>
> The API is used by platforms where mmio access to the syscon registers is
> not possible, and a underlying soc driver like exynos-pmu provides a SoC
> specific regmap that can issue a SMC or hypervisor call to write the
> register.
>
> This approach keeps the SoC complexities out of syscon, but allows common
> drivers such as syscon-poweroff, syscon-reboot and friends that are used
> by many SoCs already to be re-used.
>
> Signed-off-by: Peter Griffin <peter.griffin@...aro.org>
Reviewed-by: Arnd Bergmann <arnd@...db.de>
Powered by blists - more mailing lists