Temperature sensor reading anomaly.

With an operational design with an ADRV9004 reference clock input of 38.4 MHz, the software can call the adi_adrv9001_Temperature_Get() function with a tempReadMode enumerated parameter value of either ADI_ADRV9001_TEMPERATURE_READ_MAILBOX or ADI_ADRV9001_TEMPERATURE_READ_SPI and the functional call consistently returns a sensible value in degrees Celcius.  However, if the only change that I make is to change the ADRV9004 reference clock input frequency to 153.6 MHz (with a corresponding change to the deviceClock_kHz parameter value in the device software initialisation data), the adi_adrv9001_Temperature_Get() software function exhibits a long delay in returning a temperature value and the value returned is then non-sensical.  This action occurs with both tempReadMode enumerated parameter settings.

The configuration of the ARM clock is in divide by 1 in both cases.  

Advice gratefully received.