Linting: Align DTS linting rules and formatting

[kylebonnici]

Since the merging of:

• devicetree: format files in boards #92805
• devicetree: format files in dts #92803
• devicetree: format files in samples #92802
• devicetree: format files in tests #92801

Now that #92334 is merged, We should align remaining files as Some files were added without proper formatting, and new rules were introduced to the DTS linter.

This PR aligns all remaining files in the repository with the updated DTS linting and formatting rules.

Bump up dts-linter to 0.3.1 to fix issue when json output is not flushed to stdout
before dts-linter exits.

Bump up dts-linter to 0.3.2 to address undefined in annotation
messages

[kylebonnici]

Linter Found was unable to format this file due to syntax error in the file.

zephyr/dts/arm/nxp/nxp_mcxe31x_common.dtsi#L679

Node name is missing.

	quadspi_ardb: @68000000 {
		compatible = "nxp,";
		reg = <0x68000000 0x21c>;
		status = "disabled";
	};

[JarmouniA]

Linter Found was unable to format this file due to syntax error in the file.

zephyr/dts/arm/nxp/nxp_mcxe31x_common.dtsi#L679

Node name is missing.

	quadspi_ardb: @68000000 {
		compatible = "nxp,";
		reg = <0x68000000 0x21c>;
		status = "disabled";
	};

That file is filled with fake compatibles and meaningless node names I don't know how it was approved, looks generated by an LLM (the commit msg says "generate")

Update: was generated by a script #95560 (comment)

[kylebonnici]

Do you need me to split commits for better review as I had done in

• devicetree: format files in boards #92805
• devicetree: format files in dts #92803
• devicetree: format files in samples #92802
• devicetree: format files in tests #92801
  ?

[aescolar]

@kylebonnici this PR is changing so many files that part of the automation seems to have given up.

Do you need me to split commits for better review as I had done in

Either that, or somebody reviews the patch (probably locally) and dares bless it here

[aescolar]

All spaces changes filtered out:

git pr 98158
git diff --ignore-space-at-eol -b -w --ignore-blank-lines HEAD^ | less

diff: https://gist.githubusercontent.com/aescolar/c673230e9b07d4c5809f5b54ac5e9096/raw/04975260fbc896e06e8b7568d2dad3f75b17f48b/gistfile1.txt

Includes changes to package-lock.json & package.json

CC @mbolivar @decsny @rruuaanng @kartben @nashif @nordicjm

[kylebonnici]

All spaces changes filtered out:

git pr 98158
git diff --ignore-space-at-eol -b -w --ignore-blank-lines HEAD^ | less

diff: https://gist.githubusercontent.com/aescolar/c673230e9b07d4c5809f5b54ac5e9096/raw/04975260fbc896e06e8b7568d2dad3f75b17f48b/gistfile1.txt

Includes changes to package-lock.json & package.json

CC @mbolivar @decsny @rruuaanng @kartben @nashif @nordicjm

FYI linter is bumped up as requested in a separate PR

[kylebonnici]

@kylebonnici this PR is changing so many files that part of the automation seems to have given up.

Do you need me to split commits for better review as I had done in

Either that, or somebody reviews the patch (probably locally) and dares bless it here

Will split commits and see if it helps

[mbolivar]

Generally looks good, thanks for continuing to push on this!

One issue I'd like to see fixed, and one question.

[kylebonnici]

@mbolivar am I right to assume this PR will be merged after the release?

[mbolivar]

@mbolivar am I right to assume this PR will be merged after the release?

It definitely won't be merged for this release, but let's try to get it in early in the next cycle so you don't have to rebase this thing forever. Thanks again! LGTM now.

[mbolivar]

@kylebonnici please take a look at the CI failures and fix htem

[fabiobaltieri]

thanks, I'd suggest just doing a commit per root directory here, like one for boards/ and one for tests/, I see you like to live on the edge of the rebase limit but these commit bomb can be a bit of a pain to deal with downstream :-) anyway won't bother doing it now just if you need to do another push on top of this

[kylebonnici]

thanks, I'd suggest just doing a commit per root directory here, like one for boards/ and one for tests/, I see you like to live on the edge of the rebase limit but these commit bomb can be a bit of a pain to deal with downstream :-) anyway won't bother doing it now just if you need to do another push on top of this

@fabiobaltieri Rebased. Squashed per dir. Last commit is the only formatting needed after rebasing

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[fabiobaltieri]

Thanks

[fabiobaltieri]

Looks like Marti previously approved it, merging so it does not get caught in an infinite rebase loop.