From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Tomas Melin <tomas.melin@vaisala.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
Nuno Sa <nuno.sa@analog.com>, Jonathan Cameron <jic23@kernel.org>,
David Lechner <dlechner@baylibre.com>,
Andy Shevchenko <andy@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] iio: adc: ad9467: add support for ad9211
Date: Wed, 3 Dec 2025 14:48:35 +0200 [thread overview]
Message-ID: <aTAxo5sM90vwgxTT@smile.fi.intel.com> (raw)
In-Reply-To: <20251203-add-ad9211-v1-2-170e97e6df11@vaisala.com>
On Wed, Dec 03, 2025 at 12:20:34PM +0000, Tomas Melin wrote:
> The AD9211 is a 10-bit monolithic sampling analog-to-digital
> converter optimized for high performance, low power, and ease
> of use. The product operates at up to a 300 MSPS conversion
> rate and is optimized for outstanding dynamic performance
> in wideband carrier and broadband systems.
>
> The scale table implemented here is not an exact match with the
> datasheet as the table presented there is missing some information.
> The reference presents these values as being linear,
> but that does not add up. There is information missing in the table.
> Implemented scale table matches values at the middle and at the ends,
> smoothing the curve towards middle and end.
> Impact on end result from deviation in scale factor affects only software
> using it for scaling. All the possible hw-settings are also available with
> this implementation.
> Link: https://www.analog.com/media/en/technical-documentation/data-sheets/AD9211.pdf
Datasheet: https://www.analog.com/media/en/technical-documentation/data-sheets/AD9211.pdf
> Signed-off-by: Tomas Melin <tomas.melin@vaisala.com>
...
> +static const struct ad9467_chip_info ad9211_chip_tbl = {
> + .name = "ad9211",
> + .id = CHIPID_AD9211,
> + .max_rate = 300000000UL,
It's too many 0:s. Less error prone is to write it as
300 * HZ_PER_MHZ
> + .scale_table = ad9211_scale_table,
> + .num_scales = ARRAY_SIZE(ad9211_scale_table),
> + .channels = ad9211_channels,
> + .num_channels = ARRAY_SIZE(ad9211_channels),
> + .test_points = AD9647_MAX_TEST_POINTS,
> + .test_mask = GENMASK(AN877_ADC_TESTMODE_ONE_ZERO_TOGGLE,
> + AN877_ADC_TESTMODE_OFF),
> + .test_mask_len = AN877_ADC_TESTMODE_ONE_ZERO_TOGGLE + 1,
> + .default_output_mode = AD9211_DEF_OUTPUT_MODE,
> + .vref_mask = AD9211_REG_VREF_MASK,
> + .has_dco = true,
> +};
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-12-03 12:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 12:20 [PATCH 0/2] " Tomas Melin
2025-12-03 12:20 ` [PATCH 1/2] dt-bindings: " Tomas Melin
2025-12-03 13:08 ` Nuno Sá
2025-12-03 12:20 ` [PATCH 2/2] iio: " Tomas Melin
2025-12-03 12:48 ` Andy Shevchenko [this message]
2025-12-03 13:33 ` Tomas Melin
2025-12-03 14:24 ` Andy Shevchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aTAxo5sM90vwgxTT@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=robh@kernel.org \
--cc=tomas.melin@vaisala.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®