Merged
Conversation
nathanaelhuffman
force-pushed
the
ndh/flatten-nested-json-regs
branch
from
21b3ecc to
f688bad
Compare
nathanaelhuffman
force-pushed
the
ndh/flatten-nested-json-regs
branch
from
f688bad to
0ed706b
Compare
Aaron-Hartwig
approved these changes
Feb 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
For peripherals that have nested json, we just un-nest this case. There are probably smarter things that could be done to handle this down-stream in generation also but I think this is rare enough that, de-nesting them in the json export is fine and doesn't really make anything worse.