[PATCH v4 0/8] arm64: Automatic system register definition generation

[Mark Brown]

On Thu, Apr 21, 2022 at 11:15:24AM +0100, Mark Rutland wrote:

> The only things that I'm really not sure about is what we do for registers
> whose structure changes, or where a register has multiple names (like some
> GICv3 ICV regs), and it would be nice if we could see an example of those.

I replied elsewhere about the structure changing registers - I think the
general shape of what to do is relatively obvious there, how concretely
to achieve that is more of an issue.  For multiple names I think that's
something that we should just treat it as sharing the same layout and
punt to higher levels to work out that it's actually the same underlying
register, that seems like a higher level issue.

> Otherwise, I think we just need to agree upon the naming/structure we want to
> generate. With that we can do some preparatory renaming (and any strucutral
> changes for things like shifts) ahead of a bulk conversion to generated
> definitions.

Hopefully there's enough examples in this subset for the naming and
structure if people agree to it.  I was thinking it would be more
digestable to go through in small groups of registers rather than try to
do a bulk conversion - there's a lot of registers and probably going to
be a fair number of preparatory changes needed which could easily add up
to be a lot to digest in one sitting, which will be magnified for
resends.

> Does that sound about right to you, or is there any concern that I've missed
> that we should consider?

I think that about covers it.
-------------- 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/20220421/6985cf08/attachment.sig>