-
Notifications
You must be signed in to change notification settings - Fork 867
ADRV9001 new devices #2764
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
nunojsa
wants to merge
16
commits into
main
Choose a base branch
from
staging/adrv9002-new-devs
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
ADRV9001 new devices #2764
+8,641
−145
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ADRV9003 devices do not support digital predistortion. Therefore let's not allow to enable it. Fixes: 0b4d96b ("iio: adc: adrv9002: support adrv9003") Signed-off-by: Nuno Sá <[email protected]>
ADRV9003 does not support Digital predistortion: Hence, fix the DT and make sure we're not enabling it for TX1. Fixes: caa39fb ("arch: arm64: dts: add adrv9003 devicetrees") Signed-off-by: Nuno Sá <[email protected]>
Typically, the preferred way for chip info structures is to have a variable per device as that is more readable and maintainable over time. Note that we need to do a similar conversion in the connected axi-adc converter. Signed-off-by: Nuno Sa <[email protected]>
Instead of reporting everything as adrv9002, allow have different struct axiadc_chip_info with the proper chip name. This will be more important when supporting more chips of the adrv9001 family. Signed-off-by: Nuno Sá <[email protected]>
Add a dedicated compatible for the ADRV9003 device. After all it's a different chip from ADRV9002. Signed-off-by: Nuno Sá <[email protected]>
Add a dedicated compatible for the ADRV9003 device. After all it's a different chip from ADRV9002. Signed-off-by: Nuno Sá <[email protected]>
Add a dedicated compatible for the ADRV9003 device. After all it's a different chip from ADRV9002. Signed-off-by: Nuno Sá <[email protected]>
…atibles Use a dedicated compatible for ADRV9003 devices. This will go inline with new chips being supported in following changes. Signed-off-by: Nuno Sá <[email protected]>
Add LVDS and CMOS profiles for ADRV9004, ADRV9005 and ADRV9006. Signed-off-by: Nuno Sá <[email protected]>
There's no need to the IIO parent device as that is already done by the core when allocating the device. Signed-off-by: Nuno Sá <[email protected]>
Add support for the ADRV9004, ADRV9005 and ADRV9006 Narrow-Band and Wideband RF Transceivers. They are similar to ADRV9002 wirh some key differences: ADRV9004: * No DPD support; ADRV9005: * Only 1R1T and no TX tracking calibrations for FDD profiles. ADRV9006: * No DPD support; * No external LO support; * No High performance ADCs; * Only FH normal mode for PLL locking. Signed-off-by: Nuno Sá <[email protected]>
Add new compatibles for ADRV9004 and ADRV9006 which also have two RX ports and thus make use of this driver. Signed-off-by: Nuno Sá <[email protected]>
Add new compatibles for ADRV9004, ADRV9005 and ADRV9006. These are new devices being supported in the ADRV9002 family. Signed-off-by: Nuno Sá <[email protected]>
Add new compatibles for ADRV9004, ADRV9005 and ADRV9006. These are new devices being supported in the ADRV9002 family. Note that rx2tx2 variants are also being added for devices that support it. ADRV9005 does not have since it only has TX port. Signed-off-by: Nuno Sá <[email protected]>
Add profiles for the new devices supported byu the ADRV9002 driver. Signed-off-by: Nuno Sá <[email protected]>
Add devicetrees to support ADRV9004, ADRV9005 and ADRV9006 (and the rx2tx2 variants where it makes sense). Signed-off-by: Nuno Sá <[email protected]>
ae510f2
to
c6ce2d4
Compare
v2:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Description
This patchseries first fix some issues with ADRV9003 support where DPD is not available. Then, we do some rearrangements (most noticeable, dedicated compatibles for the new chips) and then we proceed to support ADRV9004, ADRV9005 and ADRV9006.
Also to note that these new devices do not have warmboot enabled by default. The only reason for that is because of the associated burden when updating to new APIs (as this coefficients would have to be updated for both CMOS and LVDS). In theory, and for consistency, ADRV9003 should also not have it but now that it has, let's keep them.
Fow now, only DTs for zcu102 but support for ZED and zc706 will come fairly soon after this is merged.
PR Type
PR Checklist