[PATCH v4 8/8] arm64/sysreg: Generate definitions for SCTLR_EL1

Mark Brown broonie at kernel.org
Fri Apr 22 06:50:31 PDT 2022


On Fri, Apr 22, 2022 at 02:42:30PM +0100, Mark Rutland wrote:
> On Fri, Apr 22, 2022 at 01:14:51PM +0100, Mark Brown wrote:

> > I think I'd come to a similar conclusion but as you say the naming is
> > annoying and in cases like these ones there's so few users and they're
> > oring in other bits so it might be more sensible to just or in these now
> > defined RES1 bits in the user, skipping out on the naming question
> > entirely - in this case the usage is in INIT_SCTLR_EL2_MMU_*.  Looking
> > at it again now I'm inclined to go that way for this one.

> FWIW, I'm perfectly happy with adding those bits explicitly in the
> `INIT_SCTLR_EL*` definitions. The key thing I wanted is that as a
> policy, `<regname>_RES1` is purely the architecturally RES1 bits.

Yes, I agree on that policy - I just happened to refer to an older
version of the architecture in an attempt to avoid this series getting
caught up on the discussion about where exactly to account for them.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20220422/8c2196a0/attachment-0001.sig>


More information about the linux-arm-kernel mailing list