Skip to content

Dev/adhv4711#3181

Open
raezt wants to merge 2 commits into
mainfrom
dev/adhv4711
Open

Dev/adhv4711#3181
raezt wants to merge 2 commits into
mainfrom
dev/adhv4711

Conversation

@raezt

@raezt raezt commented Jul 1, 2026

Copy link
Copy Markdown
Collaborator

Pull Request Description

Add ADHV4711 variant support via chip-info table:
The ADHV4710 and ADHV4711 are variants of the same device, sharing the
register map and control logic and differing only in the product-version
(chip-id) register CTRL_REG_26 (0x46 vs 0x47). Support both from the
single driver instead of duplicating it.

PR Type

  • Bug fix (change that fixes an issue)
  • New feature (change that adds new functionality)
  • Breaking change (has dependencies in other repos or will cause CI to fail)

PR Checklist

  • I have followed the Coding style guidelines
  • I have complied with the Submission Checklist
  • I have performed a self-review of the changes
  • I have commented my code, at least hard-to-understand parts
  • I have build all projects affected by the changes in this PR
  • I have tested in hardware affected projects, at the relevant boards
  • I have signed off all commits from this PR
  • I have updated the documentation (wiki pages, ReadMe etc), if applies

Add enum adhv4710_type { ID_ADHV4710, ID_ADHV4711 } and a
struct adhv4710_chip_info table indexed by that enum, holding the
per-variant expected version_product value.
- Add an id field to adhv4710_init_param and adhv4710_dev; init now
stores the selected variant and validates CTRL_REG_26 against
chip_info[dev->id].version_product.

Signed-off-by: Radu Etz <radu.etz@analog.com>
- Add ADHV4710_DEV_ID macro (default ID_ADHV4710) in common_data.h and
set adhv4710_ip.id from it in main.c.
- Add README.rst documenting both boards, the variant-selection
mechanism and the Maxim build commands.

ID_ADHV4710 is enum value 0, so zero-initialized init params default to
the ADHV4710 variant and existing callers are unaffected.

Signed-off-by: Radu Etz <radu.etz@analog.com>
.. code-block:: bash

# to delete current build
make reset

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

can you please document the new build system rather than the old one ? all maxim projects are currently transitioning, there is a big PR currently open #3184 and if you add a README.md, new build system should be documented

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants