tree f0d03e7f365d0f9a6e86a58e8ea72cc3fcce470f
parent 401a9717882581dcebbd48bb4f23563d860c6013
author Yang Chen <yang.chen@quantatw.com> 1745372879 +0800
committer Patrick Williams <patrick@stwcx.xyz> 1746224305 +0000

configurations: minerva: change fan board probe condition

We found that the old probe condition causes a "Duplicate found"
error, as shown in the logs below:

```
May 02 01:45:23 bmc entity-manager[10222]: Duplicates found, replacing $bus - 15 with found device index.
May 02 01:45:23 bmc entity-manager[10222]:  Consider fixing template to not have duplicates
May 02 01:45:23 bmc entity-manager[10222]: Duplicates found, replacing $bus - 15 with found device index.
May 02 01:45:23 bmc entity-manager[10222]:  Consider fixing template to not have duplicates
May 02 01:45:23 bmc entity-manager[10222]: Duplicates found, replacing $bus - 15 with found device index.
May 02 01:45:23 bmc entity-manager[10222]:  Consider fixing template to not have duplicates
May 02 01:45:23 bmc entity-manager[10222]: Duplicates found, replacing $bus - 15 with found device index.
May 02 01:45:23 bmc entity-manager[10222]:  Consider fixing template to not have duplicates
May 02 01:45:23 bmc entity-manager[10222]: Duplicates found, replacing $bus - 15 with found device index.
May 02 01:45:23 bmc entity-manager[10222]:  Consider fixing template to not have duplicates
May 02 01:45:23 bmc entity-manager[10222]: Duplicates found, replacing $bus - 15 with found device index.
May 02 01:45:23 bmc entity-manager[10222]:  Consider fixing template to not have duplicates
```

To resolve this, we expanded the probe conditions to explicitly handle
each fan board, including both 1st/2nd source.

Additionally, we use BOARD_PART_NUMBER for the DVT1 boards and a new
field (BOARD_INFO_AM4) starting from the DVT2 stage to distinguish
between different sources of the fan board.

Change-Id: I46d05f78a1de3202941418aea7be49396f686e54
Signed-off-by: Yang Chen <yang.chen@quantatw.com>