Skip to content

Conversation

danmois
Copy link
Contributor

@danmois danmois commented Aug 28, 2025

PR Description

Add observation inputs for ADRV902X.

PR Type

  • Bug fix (a change that fixes an issue)
  • New feature (a change that adds new functionality)
  • Breaking change (a change that affects other repos or cause CIs to fail)

PR Checklist

  • I have conducted a self-review of my own code changes
  • I have tested the changes on the relevant hardware
  • I have updated the documentation outside this repo accordingly (if there is the case)

@danmois
Copy link
Contributor Author

danmois commented Aug 28, 2025

V2

  • make all JESD ops static
  • use parentheses for logical operations

Copy link
Collaborator

@nunojsa nunojsa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi,

So the first patch needs splitting... Do not mix driver code with devicetree and the config change should also be in a separate patch. Then, the second patch seems to be relevant for the whole "Add ORx support" so to me it would only be one patch. So to sum up, I think this should be:

  1. "iio: adc: adrv902x: Make JESD ops static"
  2. Add ORx support in DT;
  3. Add defconfig change;
  4. Add ORx support in the driver:

Make all JESD ops static.

Signed-off-by: George Mois <[email protected]>
@danmois
Copy link
Contributor Author

danmois commented Aug 29, 2025

V3

  • reorganize commits

Copy link
Collaborator

@nunojsa nunojsa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just some minor stuff that might no need a re-spin

*
* Copyright (C) 2020-2025 Analog Devices Inc.
*/
#include "vcu118_adrv9025.dts"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah I failed to realize this... Being nitpicky, the microblaze DT should be in a separate patch. Anyways, just a hint for the future. No need to change it if there isn't a stronger reason for you to re-spin.

@@ -0,0 +1,3030 @@
{
"dataInterface": {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The firmware should be in a different patch. Different change and different directory :)

@@ -74,7 +74,7 @@ CONFIG_NET_DSA=y
CONFIG_PCI=y
CONFIG_DEVTMPFS=y
CONFIG_DEVTMPFS_MOUNT=y
CONFIG_EXTRA_FIRMWARE="ad9467_intbypass_ad9517.stp ad9517.stp Mykonos_M3.bin TaliseStream.bin TaliseTDDArmFirmware.bin TaliseTxArmFirmware.bin TaliseRxArmFirmware.bin ADRV9025_DPDCORE_FW.bin ADRV9025_FW.bin ADRV9025_RxGainTable.csv ADRV9025_TxAttenTable.csv stream_image_6E3E00EFB74FE7D465FA88A171B81B8F.bin ActiveUseCase.profile ActiveUtilInit.profile"
CONFIG_EXTRA_FIRMWARE="ad9467_intbypass_ad9517.stp ad9517.stp Mykonos_M3.bin TaliseStream.bin TaliseTDDArmFirmware.bin TaliseTxArmFirmware.bin TaliseRxArmFirmware.bin ADRV9025_DPDCORE_FW.bin ADRV9025_FW.bin ADRV9025_RxGainTable.csv ADRV9025_TxAttenTable.csv stream_image_6E3E00EFB74FE7D465FA88A171B81B8F.bin ActiveUseCase.profile ActiveUtilInit.profile ActiveUseCase_NLS.profile"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would also be a different patch

case CHAN_RX1:
case CHAN_RX2:
case CHAN_RX3:
case CHAN_RX4:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

case CHAN_RX1 ... CHAN_RX4? If it's sequential, it should be fine

@@ -1724,8 +1821,18 @@ static int adrv9025_clk_register(struct adrv9025_rf_phy *phy, const char *name,

switch (source) {
case RX_SAMPL_CLK:
adrv9025_RxLinkSamplingRateFind(phy->madDevice, &phy->deviceInitStruct,
ADI_ADRV9025_FRAMER_0,
&rate);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it a void function?

case OBS_SAMPL_CLK:
adrv9025_RxLinkSamplingRateFind(phy->madDevice, &phy->deviceInitStruct,
ADI_ADRV9025_FRAMER_1,
&rate);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same question, do we need to check return values?

Add ORx support in DT for ZCU102.

Signed-off-by: George Mois <[email protected]>
Add ORx support in DT for VCU118.

Signed-off-by: George Mois <[email protected]>
Add non-link sharing profile for ADRV9025.

Signed-off-by: George Mois <[email protected]>
Update defconfig for ZynqMP.

Signed-off-by: George Mois <[email protected]>
Update defconfig for MicroBlaze.

Signed-off-by: George Mois <[email protected]>
Add ORx support in the ADRV902X driver.

Signed-off-by: George Mois <[email protected]>
@danmois
Copy link
Contributor Author

danmois commented Aug 29, 2025

V4

  • split commits
  • add error handling
  • separate ORx digital paths available selection

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants