[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201119171801.GE4376@gaia>
Date: Thu, 19 Nov 2020 17:18:01 +0000
From: Catalin Marinas <catalin.marinas@....com>
To: Suzuki K Poulose <suzuki.poulose@....com>
Cc: linux-arm-kernel@...ts.infradead.org, mathieu.poirier@...aro.org,
mike.leach@...aro.org, linux-kernel@...r.kernel.org,
anshuman.khandual@....com, jonathan.zhouwen@...wei.com,
coresight@...ts.linaro.org, Will Deacon <will@...nel.org>
Subject: Re: [PATCH v4 24/25] arm64: Add TRFCR_ELx definitions
On Thu, Nov 19, 2020 at 04:45:46PM +0000, Suzuki K Poulose wrote:
> @@ -988,6 +991,14 @@
> /* Safe value for MPIDR_EL1: Bit31:RES1, Bit30:U:0, Bit24:MT:0 */
> #define SYS_MPIDR_SAFE_VAL (BIT(31))
>
> +#define TRFCR_ELx_TS_SHIFT 5
> +#define TRFCR_ELx_TS_VIRTUAL ((0x1) << TRFCR_ELx_TS_SHIFT)
> +#define TRFCR_ELx_TS_GUEST_PHYSICAL ((0x2) << TRFCR_ELx_TS_SHIFT)
> +#define TRFCR_ELx_TS_PHYSICAL ((0x3) << TRFCR_ELx_TS_SHIFT)
For consistency, I'd use 0x1UL etc. in case the shift goes beyond 32
(not the case here though).
Otherwise:
Acked-by: Catalin Marinas <catalin.marinas@....com>
Powered by blists - more mailing lists