Code size report:

Reference:  tests: Update ESP32-Cx detection to match standard name. [334c031]
Comparison: Fix formatting of comments in rp2_psram.c [merge of a21b9b0]
  mpy-cross:    +0 +0.000% 
   bare-arm:    +0 +0.000% 
minimal x86:    +0 +0.000% 
   unix x64:    +0 +0.000% standard
      stm32:    +0 +0.000% PYBV10
      esp32:    +0 +0.000% ESP32_GENERIC
     mimxrt:    +0 +0.000% TEENSY40
        rp2:    +0 +0.000% RPI_PICO_W
       samd:    +0 +0.000% ADAFRUIT_ITSYBITSY_M4_EXPRESS
  qemu rv32:    +0 +0.000% VIRT_RV32

NOTE - Failed Checks are happening in areas of the code far away from what I changed.

If with failed checks you mean the CI errors, then those are related to your changes. Given what you committed I reckon you probably didn't read CODECONVENTIONS.md and maybe didn't set up the environment as described in that document.

Just in case, please read that document. There's all the necessary information to not cause the two CI errors you see here.

Also, since the commits have to be altered, please squash those three commits into just one atomic change. You're just making minor modifications to your main change, after all.

Support for PSRAM on RP2 should be moved upstream to rely on the Pico SDK functions when possible- #19209

As such it would be prudent to make sure these issues don't also exist in the Pico SDK implementation, or we'll get a regression sometime in the future- raspberrypi/pico-sdk#2919

Support for PSRAM on RP2 should be moved upstream to rely on the Pico SDK functions when possible- #19209

As such it would be prudent to make sure these issues don't also exist in the Pico SDK implementation, or we'll get a regression sometime in the future- raspberrypi/pico-sdk#2919

Upstream support isn't affected by this, as the timing calculation is already separated from the direct mode use