linux-kernel - Re: [PATCH v3 1/2] mfd: syscon: add of_syscon_register

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Mon, 24 Jun 2024 07:57:51 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Peter Griffin <peter.griffin@...aro.org>, lee@...nel.org, arnd@...db.de,
 alim.akhtar@...sung.com
Cc: linux-arm-kernel@...ts.infradead.org, linux-samsung-soc@...r.kernel.org,
 linux-kernel@...r.kernel.org, tudor.ambarus@...aro.org,
 andre.draszik@...aro.org, saravanak@...gle.com, willmcvicker@...gle.com,
 semen.protsenko@...aro.org, kernel-team@...roid.com
Subject: Re: [PATCH v3 1/2] mfd: syscon: add of_syscon_register_regmap() API

On 21/06/2024 13:55, 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>
> Reviewed-by: Sam Protsenko <semen.protsenko@...aro.org>


Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>

Lee,

The second patch is for Samsung SoC but it depends on this one. I do not
see any conflicting work, so you could take both via MFD tree, but just
in case, could you keep both on a separate patchset? That way I could
still pull it if there are more patches coming.

Best regards,
Krzysztof