Re: [PATCH V3 03/16] arm64/cpufeature: Make doublelock a signed feature in ID_AA64DFR0

On 05/05/2020 04:40 PM, Will Deacon wrote: > On Sat, May 02, 2020 at 07:03:52PM +0530, Anshuman Khandual wrote: >> Double lock feature can have the following possible values. >> >> 0b - Double lock implemented >> 0b - Double lock not implemented >> >> But in case of a conflict the safe

Re: [PATCH V3 03/16] arm64/cpufeature: Make doublelock a signed feature in ID_AA64DFR0

On Sat, May 02, 2020 at 07:03:52PM +0530, Anshuman Khandual wrote: > Double lock feature can have the following possible values. > > 0b - Double lock implemented > 0b - Double lock not implemented > > But in case of a conflict the safe value should be 0b. Hence this must > be a

[PATCH V3 03/16] arm64/cpufeature: Make doublelock a signed feature in ID_AA64DFR0

Double lock feature can have the following possible values. 0b - Double lock implemented 0b - Double lock not implemented But in case of a conflict the safe value should be 0b. Hence this must be a signed feature instead. Also change FTR_EXACT to FTR_LOWER_SAFE. Cc: Catalin Marinas