MPU driver doesn't recognize device id

[BazookaJoe1900]

Describe the bug
Looking at the nsh of pixhawk4 boot I can see the next line:

WARN [mpu6000] unexpected ID 0xfd accepted

Looking at the code, there is check of valid known product ID. but it seems that its isn't valid.

https://github.com/PX4/Firmware/blob/78ef8aab2df33cd00e2c969bbff37ffd82bcf385/src/drivers/imu/mpu6000/MPU6000.cpp#L246-L278

Looking at the ICM20689, the MPU6000 datasheets I don't even see the register (MPUREG_PRODUCT_ID, 0x0c) documented. Who knows where the ID list came from?

Except for this warning I don't see any strange behavior, but if some of the pixhawk 4 has new device, that might behave different, its better to know, and remove the warning.

To Reproduce
Enable nsh (it can be done to one of the telemetry ports).
and look at the output

[stale]

This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions.

[BazookaJoe1900]

Still relevant.

[mhkabir]

@davids5?

[davids5]

It was early IP shared with PX4. It is there to tell us there is a new version of the IC has arrived - it is a only a warning.

[BazookaJoe1900]

I also tried to get the information about the register from TDK with no luck...
Can you be sure that they have no effect? And if so why do we test them at all?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions.

[BazookaJoe1900]

@davids5 , its look like dead end.
what do you say, maybe, at least to remove the warning? or say that 0xfd is unknown, but in the list?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions.

[BazookaJoe1900]

dead end