fix rp2xxx-specific -> rp2xxx_specific

Author: kilograham

src/rp2_common/hardware_gpio/include/hardware/gpio.h

@@ -42,12 +42,12 @@ extern "C" {
  *
  * RP-series microcontrollers have two banks of General Purpose Input / Output (GPIO) pins, which are assigned as follows:
  * 
- * \if rp2040-specific
+ * \if rp2040_specific
  * RP2040 has 30 user GPIO pins in bank 0, and 6 QSPI pins in the QSPI bank 1 (QSPI_SS, QSPI_SCLK and QSPI_SD0 to QSPI_SD3). The QSPI 
  * pins are used to execute code from an external flash device, leaving the User bank (GPIO0 to GPIO29) for the programmer to use. 
  * \endif
  * 
- * \if rp2350-specific
+ * \if rp2350_specific
  * The number of GPIO pins available depends on the package. There are 30 user GPIOs in bank 0 in the QFN-60 package (RP2350A), or 48 user GPIOs 
  * in the QFN-80 package. Bank 1 contains the 6 QSPI pins and the USB DP/DM pins.
  * \endif

src/rp2_common/hardware_xip_cache/include/hardware/xip_cache.h

@@ -20,14 +20,14 @@
  * of flash), so pointers should have XIP_BASE subtracted before passing into one of these
  * functions.
  *
- * \if rp2040-specific
+ * \if rp2040_specific
  * The only valid cache maintenance operation on RP2040 is "invalidate", which tells the cache to
  * forget everything it knows about some address. This is necessary after a programming operation,
  * because the cache does not automatically know about any serial programming operations performed
  * on the external flash device, and could return stale data.
  * \endif
  *
- * \if rp2350-specific
+ * \if rp2350_specific
  * On RP2350, the three types of operation are:
  *
  * * Invalidate: tell the cache to forget everything it knows about some address. The next access to
@@ -136,12 +136,12 @@ void xip_cache_invalidate_range(uintptr_t start_offset, uintptr_t size_bytes);
  * This function is faster than calling xip_cache_clean_range() for the entire address space,
  * because it iterates over cachelines instead of addresses.
  *
- * \if rp2040-specific
+ * \if rp2040_specific
  * On RP2040 this is a no-op, as the XIP cache is read-only. This is indicated by the
  * XIP_CACHE_IS_READ_ONLY macro.
  * \endif
  *
- * \if rp2350-specific
+ * \if rp2350_specific
  * On RP2350, due to the workaround applied for RP2350-E11, this function also effectively
  * invalidates all cache lines after cleaning them. The next access to each line will miss. Avoid
  * this by calling xip_cache_clean_range() which does not suffer this issue.
@@ -155,7 +155,7 @@ void xip_cache_clean_all(void);
  *
  * This causes the cache to write out pending write data at these offsets to the downstream memory.
  *
- * \if rp2040-specific
+ * \if rp2040_specific
  * On RP2040 this is a no-op, as the XIP cache is read-only. This is indicated by the
  * XIP_CACHE_IS_READ_ONLY macro.
  * \endif