linux-kernel - Re: [PATCH v3 2/2] soc: samsung: exynos-pmu: update to use 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: Windows password security audit tool. GUI, reports in PDF.

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

Date: Fri, 21 Jun 2024 16:57:15 -0700
From: William McVicker <willmcvicker@...gle.com>
To: Peter Griffin <peter.griffin@...aro.org>
Cc: lee@...nel.org, arnd@...db.de, krzk@...nel.org, alim.akhtar@...sung.com,
	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, semen.protsenko@...aro.org,
	kernel-team@...roid.com
Subject: Re: [PATCH v3 2/2] soc: samsung: exynos-pmu: update to use
 of_syscon_register_regmap()

On 06/21/2024, Peter Griffin wrote:
> For SoCs like gs101 that need a special regmap, register this with
> of_syscon_register_regmap api, so it can be returned by
> syscon_regmap_lookup_by_phandle() and friends.
> 
> For SoCs that don't require a custom regmap, revert back to syscon
> creating the mmio regmap rather than duplicating the logic here.
> 
> exynos_get_pmu_regmap_by_phandle() api is also updated to retrieve
> the regmap via syscon. The exynos_get_pmu_regmap_by_phandle() api
> is kept around until fw_devlink support for syscon property is added
> for the pinctrl-samsung driver that also runs at postcore_initcall
> level.
> 
> All other exynos client drivers can revert back to
> syscon_regmap_lookup_by_phandle().
> 
> Signed-off-by: Peter Griffin <peter.griffin@...aro.org>
> Reviewed-by: Arnd Bergmann <arnd@...db.de>
> Reviewed-by: Sam Protsenko <semen.protsenko@...aro.org>

Tested-by: Will McVicker <willmcvicker@...gle.com>

[...]

(Testing details in patch 1)

Thanks,
Will