Add support for PHY ID_DP83822HF in PHY handling

[kzorer]

Add DP83822HF PHY identification and handling

Description

This pull request extends the PHY identification and capability handling in the FreeRTOS+TCP network interface layer.

The following PHY IDs were added to the existing PHY switch logic to ensure correct detection and feature handling:

• Added support for DP83822HF PHY
• Included DP83822HF in PHY groups that:
  • Do not implement register 0x1F (PHY Special Control Status)
  • Require explicit PHY-ID–based handling

Additionally, the following PHY identifier macro was introduced:

#define PHY_ID_DP83822HF  0x2000A240

This change aligns DP83822HF behavior with other TI PHYs (e.g. DP83848I) already supported in the stack and prevents invalid register access during PHY initialization and link status polling.

---

Test Steps

1. Build FreeRTOS+TCP with the updated PHY handling.
2. Run the firmware on hardware using DP83822HF PHY.
3. Verify:
   • PHY is detected correctly during startup.
   • No access is attempted to register 0x1F.
   • Link up/down events are reported correctly.
4. Confirm no regression on existing supported PHYs (LAN8742A, DP83848I, TM4C129X).

---

Checklist

• I have tested my changes. No regression in existing tests.
• I have modified and/or added unit-tests to cover the code changes in this Pull Request.

---

Related Issue

N/A

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[kzorer]

@htibosch @AniruddhaKanhere

[htibosch]

I approve the change

[htibosch]

I like this driver, with 2 lines of code you add a new supported PHY.
It is a pity that 1 Gbps driver s are so much more complicated and diverse.