You can either use the ADI kernel as whole - or if you only need the ADF5355 driver -
just copy adf5355.c, adf5355.h into linux/drivers/iio/frequency
and add following lines to these files:
There's a small inconsistency between the filenames; so to make sure:
It's quite explainable.
When the FMCOMMS5 was designed and build the ADF5355 was not released.
Only recently the ADF5355 released. And boards that are ordered now have the ADF5355 populated.
I got the first board with the PLL assembled only a few…
In my design, ADF5355 shares the SPI bus with others components, like SPI GPIO expander, etc. Sometimes when ADF5355 is powered off, the SPI MOSI and CLK are still alive with 0 to 3.3V swing for other components. In addition, the LE of ADF5355…
► Process for each step:
1. ADF5355 locks to desired frequency using internal PLL.
2. ADF5355 internal PLL is disabled.
3. HMC704 then locks the ADF5355 VCO.
Here is the commit:
drivers/iio/frequency/adf5355: IIO device driver for ADF5355/ADF4355 · analogdevicesinc/linux@7816102 · GitHub
This document is now on Analog.com. Please go to the ADF5355 product page, scroll down to Documentation.
HMC704 CP output connects to the ADF5355's VTUNE input. ADF5355 CP output can be disconnected.
Yes - AN-873 applies to ADF5355.
However, it is not recommended to use analog lock detect on the ADF5355. It can lead to spurs on the RF output.