Hi Dusty, thanks for the response.
I had seen a couple posts by linuxdev describing how to de-compile and re-compile dtb files, and I’d located the tegra210-jetson-cv-pinmux-p2597-2180-a00.dtsi file I mentioned in the original post based on what’s currently referenced in my extlinux.conf file. At this point, I’m pretty confident that’s the right spot for the changes in the *-pinmux.dtsi file produced by the pinmux spreadsheet.
I’m still not sure where to put my changes from the spreadsheet’s *-gpio-default.dtsi file. Before I made any changes in the spreadsheet, I saved a copy of the output files and I’ve been using those for comparison to see what actually changed once I made my modifications for pins 148/149/152. The *-gpio-default.dtsi files have a number of calls to TEGRA_GPIO() separated into 3 groups: gpio-input, gpio-output-low, and gpio-output-high. When I diff the two versions of the file, the calls for pins S4 and S5 move from gpio-output-low to gpio-input, and the call for pin T0 moves from gpio-output-low to gpio-output-high. This all seems to match the changes I made in the spreadsheet.
Any idea which file these changes belong in? There’s a file in the tegra210-platforms directory called tegra210-jetson-e-gpio-p2530-0930-e03.dtsi. That has the same general format as the two *-gpio-default.dtsi files produced by the spreadsheet, but the naming syntax is different from both my extlinux.conf file and the pinmux file I’ve already edited. Any idea what the “p2597-2180” and “p2530-0930” portions of the filename are for?