adi: Update ltc2672

[Shetty-Anush]

Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

Fixes # (issue)

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How has this been tested?

Test Configuration:

• Hardware: SDP-K1
• OS: no-OS

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have signed off all commits and they contain "Signed-off by: "
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works

[thorenscientific]

@Shetty-Anush I don't think I've worked with this DAC directly, but I've been reviewing some recent pyadi-iio scripts that use legacy LTC DACS and came across this. Can you fill out the description and all of the various details - testing, documentation, etc? Given that your example is using serial backend, is this using SDP-K1 platform or ST Nucleo, and a no-OS tinyiiod server? If so, is this published to a public repo? If it's internal, best to hold off on this PR until made public.
Also it looks like there is a Raspberry Pi overlay for Kuiper:
https://github.com/analogdevicesinc/linux/blob/rpi-6.6.y/arch/arm/boot/dts/overlays/rpi-ltc2672-overlay.dts
Can you verify that this PR does not break anything with this setup?
Thanks!

[Shetty-Anush]

@Shetty-Anush I don't think I've worked with this DAC directly, but I've been reviewing some recent pyadi-iio scripts that use legacy LTC DACS and came across this. Can you fill out the description and all of the various details - testing, documentation, etc? Given that your example is using serial backend, is this using SDP-K1 platform or ST Nucleo, and a no-OS tinyiiod server? If so, is this published to a public repo? If it's internal, best to hold off on this PR until made public. Also it looks like there is a Raspberry Pi overlay for Kuiper: https://github.com/analogdevicesinc/linux/blob/rpi-6.6.y/arch/arm/boot/dts/overlays/rpi-ltc2672-overlay.dts Can you verify that this PR does not break anything with this setup? Thanks!

@thorenscientific , I am using SDP-K1 with no-OS tinyIIOD server and the IIO application code is already made public.

The Linux team confirmed that this driver was not being used for their linux IIO driver. So, making changes to this python driver will not affect their work.

[thorenscientific]

The pyadi-iio is for customers, ideally the class and examples should work for both no-OS/tinyiiod and Linux. If there are any differences in implementation, then they should be handled cleanly, or at least well documented. It looks like the DC2903A-A should be able to connect to a Raspberry Pi with an PMD-RPI-INTZ, it should be a quick check. Do you have access to these?

[Shetty-Anush]

The pyadi-iio is for customers, ideally the class and examples should work for both no-OS/tinyiiod and Linux. If there are any differences in implementation, then they should be handled cleanly, or at least well documented. It looks like the DC2903A-A should be able to connect to a Raspberry Pi with an PMD-RPI-INTZ, it should be a quick check. Do you have access to these?

I believe it will not work in the Linux setup, based on what is described in the documentation -https://wiki.analog.com/resources/tools-software/linux-drivers/iio-dac/ltc2672. Unfortunately, I also do not have access to the hardware needed to verify this directly.