Cannot compile for ESP32-P4 due to broken GPIO_RANGE_MAX when ENABLE_ETHERNET_TELEMETRY is enabled

[tomasmcguinness]

Using the current 'master' of esp-matter, I am trying to compile for the ESP32-P4.

esp-matter: commit a91b410
esp-idf: 5.5.4

Compilation fails with a python error when ENABLE_ETHERNET_TELEMETRY is enabled. I am attempting to use the platform mDNS.

warning: default value 23 on ETH_MDC_GPIO (defined at /Users/tomasmcguinness/Development/esp/esp-matter/connectedhomeip/connectedhomeip/config/esp32/components/chip/Kconfig:775) clamped to 0 due to being outside the active range ([0, 0])
warning: default value 18 on ETH_MDIO_GPIO (defined at /Users/tomasmcguinness/Development/esp/esp-matter/connectedhomeip/connectedhomeip/config/esp32/components/chip/Kconfig:783) clamped to 0 due to being outside the active range ([0, 0])
warning: default value 5 on ETH_PHY_RST_GPIO (defined at /Users/tomasmcguinness/Development/esp/esp-matter/connectedhomeip/connectedhomeip/config/esp32/components/chip/Kconfig:791) clamped to 0 due to being outside the active range ([-1, 0])

On inspection, the Kconfig configuration doesn't include the ESP32-P4

 config GPIO_RANGE_MAX
            int
            depends on ENABLE_ETHERNET_TELEMETRY
            default 33 if IDF_TARGET_ESP32
            default 46 if IDF_TARGET_ESP32S2
            default 19 if IDF_TARGET_ESP32C3
            default 48 if IDF_TARGET_ESP32S3
            default 26 if IDF_TARGET_ESP32H2

However, the connectedhomeip repo accepted a commit on the 5th of February to amend this, adding a P4

project-chip/connectedhomeip@6008fde

When will esp-matter be updated to include the latest connectedhomeip?

Can I work around this issue?

[shubhamdp]

@tomasmcguinness we recently bumped the submodule with 9f9bddc and this commit you mentioned in part of that submodule.

Please give it a try.