Skip to content

Correct some doxygen/sphinx warnings or errors.#721

Merged
zeddii merged 4 commits intodevicetree-org:masterfrom
sipke:feature/remove-toc-not-included-warnings
Mar 30, 2026
Merged

Correct some doxygen/sphinx warnings or errors.#721
zeddii merged 4 commits intodevicetree-org:masterfrom
sipke:feature/remove-toc-not-included-warnings

Conversation

@sipke
Copy link
Copy Markdown

@sipke sipke commented Mar 16, 2026

This pull request (PR) corrects some doxygen/sphinx warnings or errors.
Most of these have no direct effect on documentation output, except one where heading levels changed, so the size of the heading is likely to increase for the subheading.

This is a second round of changes focusing on documentation generation errors rather than layout preferences to address initial review comments.

These warnings/errors were found during attempts to further integrate submodules into openamp-docs via PR OpenAMP/openamp-docs#82.

Welcome to Linux Device Tree Generation for AMD SOCs using Lopper and SDT's documentation!
===========================================================================================
Linux Device Tree Generation for AMD SOCs using Lopper and SDT's
================================================================
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd prefer to leave this as-is, there's different consumers of this, and I'm not fond of tweaking it to suit one over the others.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok. fair.

Copy link
Copy Markdown
Collaborator

@zeddii zeddii left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You'll need to be more specific here.

How does this change the output of the docs ? What's the old versus the new look like ?

I have no idea about the open-amp readthedocs, so using that as a reason for a change unfortunately doesn't mean anything to me.

Copy link
Copy Markdown
Collaborator

@zeddii zeddii left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You'll need to be more specific here.

How does this change the output of the docs ? What's the old versus the new look like ?

I have no idea about the open-amp readthedocs, so using that as a reason for a change unfortunately doesn't mean anything to me.

Basic Workflow (without board-specific device-tree):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Gen 2 Basic Workflow (without board-specific device-tree):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know very little about sphinx (outside of occasioning editing file and generating with it).

What is the significance of "Gen 2" in the updated lines ?

Copy link
Copy Markdown
Author

@sipke sipke Mar 17, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can enable autosectionlabel generation when using sphinx/doxygen. i.e. for every heading in an rst or md file a label is created based on the heading. https://www.sphinx-doc.org/en/master/usage/extensions/autosectionlabel.html
Where the autosectionlabel can be used in external other rst files to reference/link these headings directly, without having to add manual labels.
Unfortunately sphinx does not prefix subheadings with the previous heading level so any subheading which is the same in multiple higher level headings is a duplicate label.
What you had is cleaner (more readable), so maybe not a good idea to change, but anyone using autosectionlabel will receive a warning currently if enabled.
The Gen 2 was just propogated from the top level heading "For Versal Gen 2 Platform:"

@sipke
Copy link
Copy Markdown
Author

sipke commented Mar 17, 2026

Can't do it at moment, but I will rework the branch to target "actual" documentation errors, and remove the format/layout change ones where there is a sphinx warning but arguably not an issue.

In terms of how things change, apart from the obvious ones where the title changed, there were only really heading level changes, where subheadings were slightly smaller, and each file receive a top level heading. The main difference is the sphinx build output generates less warnings.
Understand your concerns though, so will rework and resubmit.

@sipke sipke marked this pull request as draft March 17, 2026 06:59
@sipke sipke marked this pull request as draft March 17, 2026 06:59
Correct table formatting to fix sphinx error
ERROR: Malformed table

Signed-off-by: Sipke Vriend <sipke@direktembedded.com>
@sipke sipke force-pushed the feature/remove-toc-not-included-warnings branch from 3285e5f to 3b0b972 Compare March 22, 2026 22:24
Sipke Vriend added 3 commits March 23, 2026 10:22
Add a delimiter to the bold/* emphasis character to avoid the warning
WARNING: Inline emphasis start-string without end-string

Signed-off-by: Sipke Vriend <sipke@direktembedded.com>
…y line

the - (dash) for the bullet point was to left of Optional tag making
the sphinx document generator think it is a new line rather than bullet
point, so move it to the left to correct the warning:
WARNING: Bullet list ends without a blank line

Signed-off-by: Sipke Vriend <sipke@direktembedded.com>
Change the H3 headings after an H1 heading to H3 to remove the sphinx
warning:

WARNING: Non-consecutive header level increase; H1 to H3 [myst.header]

Signed-off-by: Sipke Vriend <sipke@direktembedded.com>
@sipke sipke force-pushed the feature/remove-toc-not-included-warnings branch from 13eb169 to 2c9142c Compare March 23, 2026 00:23
@sipke sipke changed the title Feature/remove toc not included warnings Correct some doxygen/sphinx warnings or errors. Mar 23, 2026
@sipke sipke marked this pull request as ready for review March 23, 2026 04:44
@zeddii zeddii merged commit 1404471 into devicetree-org:master Mar 30, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants