[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZnymlHiCCIDt2dCJ@google.com>
Date: Wed, 26 Jun 2024 16:39:00 -0700
From: William McVicker <willmcvicker@...gle.com>
To: Peter Griffin <peter.griffin@...aro.org>
Cc: robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org,
alim.akhtar@...sung.com, s.nawrocki@...sung.com,
cw00.choi@...sung.com, mturquette@...libre.com, sboyd@...nel.org,
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,
kernel-team@...roid.com, devicetree@...r.kernel.org,
linux-clk@...r.kernel.org
Subject: Re: [PATCH 2/3] soc: samsung: exynos-pmu: add support for PMU_ALIVE
non atomic registers
On 06/26/2024, Peter Griffin wrote:
> Not all registers in PMU_ALIVE block support atomic set/clear operations.
> GS101_SYSIP_DAT0 and GS101_SYSTEM_CONFIGURATION registers are two regs
> where attempting atomic access fails.
>
> As documentation on exactly which registers support atomic operations is
> not forthcoming. We default to atomic access, unless the register is
> explicitly added to the tensor_is_atomic() function. Update the comment
> to reflect this as well.
>
> Signed-off-by: Peter Griffin <peter.griffin@...aro.org>
Reviewed-by: Will McVicker <willmcvicker@...gle.com>
Tested-by: Will McVicker <willmcvicker@...gle.com>
I verified reboot and power off on my Pixel 6 Pro.
> ---
> drivers/soc/samsung/exynos-pmu.c | 16 ++++++++++++++--
> include/linux/soc/samsung/exynos-regs-pmu.h | 4 ++++
> 2 files changed, 18 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/soc/samsung/exynos-pmu.c b/drivers/soc/samsung/exynos-pmu.c
> index 624324f4001c..5556acc7c092 100644
> --- a/drivers/soc/samsung/exynos-pmu.c
> +++ b/drivers/soc/samsung/exynos-pmu.c
> @@ -129,14 +129,26 @@ static int tensor_set_bits_atomic(void *ctx, unsigned int offset, u32 val,
> return ret;
> }
>
> +static bool tensor_is_atomic(unsigned int reg)
> +{
> + switch (reg) {
> + case GS101_SYSIP_DAT0:
> + case GS101_SYSTEM_CONFIGURATION:
> + return false;
> + default:
> + return true;
> + }
> +}
> +
> static int tensor_sec_update_bits(void *ctx, unsigned int reg,
> unsigned int mask, unsigned int val)
> {
> /*
> * Use atomic operations for PMU_ALIVE registers (offset 0~0x3FFF)
> - * as the target registers can be accessed by multiple masters.
> + * as the target registers can be accessed by multiple masters. Some
> + * SFRs don't support this however as reported by tensor_is_atomic()
> */
> - if (reg > PMUALIVE_MASK)
> + if (reg > PMUALIVE_MASK || !tensor_is_atomic(reg))
nit: Should we just move all the logic, e.g. `reg > PMUALIVE_MASK` into `tensor_is_atomic()`?
[...]
Thanks,
Will
Powered by blists - more mailing lists