From: Jonathan Cameron <jic23@kernel.org>
To: Piyush Patle <piyushpatle228@gmail.com>
Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Andreas Klinger <ak@it-klinger.de>,
Andy Shevchenko <andy@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>
Subject: Re: [PATCH v9 06/11] iio: adc: hx711: introduce hx711_chip_info structure
Date: Wed, 20 May 2026 11:23:38 +0100 [thread overview]
Message-ID: <20260520112338.22e9dcb0@jic23-huawei> (raw)
In-Reply-To: <20260518220228.63322-7-piyushpatle228@gmail.com>
On Tue, 19 May 2026 03:32:22 +0530
Piyush Patle <piyushpatle228@gmail.com> wrote:
> Add a per-variant static configuration structure and populate the IIO
> device fields from it at probe time.
>
> This is a preparatory change for adding support for more HX711-compatible
> hardware variants without duplicating the probe-time setup.
>
> No functional change for existing HX711 users.
>
> Signed-off-by: Piyush Patle <piyushpatle228@gmail.com>
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@intel.com>
> ---
> No code change from v8.
>
> Regarding the __counted_by_ptr() annotation on hx711_chip_info.channels:
> this annotation was introduced in include/linux/compiler_types.h in
> commit 4b8a2e8e09be ("compiler_types.h: Add __counted_by_ptr()") which
> landed in 6.12-rc1.
Seems unlikely. I'm seeing it landing in January this year. I'm guessing
you are looking at a backport to a stable tree maybe? That commit id
isn't in upstream.
> This tree is 6.17, so the macro is
Why are you on 6.17! This is targetting 7.2 so all we care about is whether
it was in the 7.1-rc1 or not. Meh doesn't matter as this text will get
dropped anyway when I merge.
> well-defined. Jonathan Cameron requested this annotation in his v7
> review; Sashiko's v8 bot flag was a false positive.
>
> Regarding the legacy platform_device probe path: the concern that
> probe could succeed without chip_info (returning a useless device) was
> acknowledged. Jonathan has indicated the current device_get_match_data()
> guard is acceptable, so no change was made.
>
> drivers/iio/adc/hx711.c | 41 ++++++++++++++++++++++++++++++++++++-----
> 1 file changed, 36 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/iio/adc/hx711.c b/drivers/iio/adc/hx711.c
> index 86d2a70dd3de..10ccc69f209b 100644
> --- a/drivers/iio/adc/hx711.c
> +++ b/drivers/iio/adc/hx711.c
> @@ -4,6 +4,8 @@
> *
> * Copyright (c) 2016 Andreas Klinger <ak@it-klinger.de>
> */
> +#include <linux/array_size.h>
> +#include <linux/dev_printk.h>
> #include <linux/err.h>
> #include <linux/kernel.h>
> #include <linux/module.h>
> @@ -74,6 +76,20 @@ static int hx711_get_scale_to_gain(const int *gain_scale, int scale)
> return -EINVAL;
> }
>
> +/**
> + * struct hx711_chip_info - per-variant static configuration
> + * @name: IIO device name
> + * @channels: channel specification array
> + * @num_channels: number of entries in @channels
> + * @iio_info: IIO info ops for this variant
> + */
> +struct hx711_chip_info {
> + const char *name;
> + const struct iio_chan_spec *channels __counted_by_ptr(num_channels);
> + unsigned int num_channels;
> + const struct iio_info *iio_info;
> +};
> +
> struct hx711_data {
> struct device *dev;
> struct gpio_desc *gpiod_pd_sck;
> @@ -81,6 +97,7 @@ struct hx711_data {
> int gain_set; /* gain set on device */
> int gain_chan_a; /* gain for channel A */
> int gain_scale[HX711_GAIN_MAX];
> + const struct hx711_chip_info *chip_info;
> struct mutex lock;
> /*
> * triggered buffer
> @@ -456,8 +473,16 @@ static const struct iio_chan_spec hx711_chan_spec[] = {
> IIO_CHAN_SOFT_TIMESTAMP(2),
> };
>
> +static const struct hx711_chip_info hx711_chip = {
> + .name = "hx711",
> + .channels = hx711_chan_spec,
> + .iio_info = &hx711_iio_info,
> + .num_channels = ARRAY_SIZE(hx711_chan_spec),
> +};
> +
> static int hx711_probe(struct platform_device *pdev)
> {
> + const struct hx711_chip_info *chip_info;
> struct device *dev = &pdev->dev;
> struct hx711_data *hx711_data;
> struct iio_dev *indio_dev;
> @@ -473,6 +498,12 @@ static int hx711_probe(struct platform_device *pdev)
>
> mutex_init(&hx711_data->lock);
>
> + chip_info = device_get_match_data(dev);
> + if (!chip_info)
> + return dev_err_probe(dev, -ENODEV, "missing driver data\n");
> +
> + hx711_data->chip_info = chip_info;
> +
> /*
> * PD_SCK stands for power down and serial clock input of HX711
> * in the driver it is an output
> @@ -534,11 +565,11 @@ static int hx711_probe(struct platform_device *pdev)
> hx711_data->data_ready_delay_ns =
> 1000000000 / hx711_data->clock_frequency;
>
> - indio_dev->name = "hx711";
> - indio_dev->info = &hx711_iio_info;
> + indio_dev->name = chip_info->name;
> + indio_dev->info = chip_info->iio_info;
> indio_dev->modes = INDIO_DIRECT_MODE;
> - indio_dev->channels = hx711_chan_spec;
> - indio_dev->num_channels = ARRAY_SIZE(hx711_chan_spec);
> + indio_dev->channels = chip_info->channels;
> + indio_dev->num_channels = chip_info->num_channels;
>
> ret = devm_iio_triggered_buffer_setup(dev, indio_dev,
> iio_pollfunc_store_time,
> @@ -555,7 +586,7 @@ static int hx711_probe(struct platform_device *pdev)
> }
>
> static const struct of_device_id of_hx711_match[] = {
> - { .compatible = "avia,hx711", },
> + { .compatible = "avia,hx711", .data = &hx711_chip },
> { }
> };
>
next prev parent reply other threads:[~2026-05-20 10:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 22:02 [PATCH v9 00/11] iio: adc: Add support for AVIA HX710B ADC Piyush Patle
2026-05-18 22:02 ` [PATCH v9 01/11] dt-bindings: iio: adc: hx711: clean up existing binding text Piyush Patle
2026-05-18 22:02 ` [PATCH v9 02/11] dt-bindings: iio: adc: hx711: add VSUP supply property Piyush Patle
2026-05-20 10:09 ` Jonathan Cameron
2026-05-24 2:42 ` Piyush Patle
2026-05-26 12:31 ` Jonathan Cameron
2026-05-18 22:02 ` [PATCH v9 03/11] dt-bindings: iio: adc: hx711: add RATE GPIO property Piyush Patle
2026-05-18 22:02 ` [PATCH v9 04/11] dt-bindings: iio: adc: hx711: add HX710B support Piyush Patle
2026-05-18 22:10 ` sashiko-bot
2026-05-19 17:21 ` Conor Dooley
2026-05-20 10:19 ` Jonathan Cameron
2026-05-24 2:45 ` Piyush Patle
2026-05-26 12:32 ` Jonathan Cameron
2026-05-18 22:02 ` [PATCH v9 05/11] iio: adc: hx711: move scale computation to per-device storage Piyush Patle
2026-05-18 22:02 ` [PATCH v9 06/11] iio: adc: hx711: introduce hx711_chip_info structure Piyush Patle
2026-05-18 22:30 ` sashiko-bot
2026-05-20 10:23 ` Jonathan Cameron [this message]
2026-05-18 22:02 ` [PATCH v9 07/11] iio: adc: hx711: pass trailing pulse count into hx711_read Piyush Patle
2026-05-18 22:02 ` [PATCH v9 08/11] iio: adc: hx711: split variable assignments in hx711_read and hx711_reset Piyush Patle
2026-05-20 10:24 ` Jonathan Cameron
2026-05-24 2:47 ` Piyush Patle
2026-05-18 22:02 ` [PATCH v9 09/11] iio: adc: hx711: localize loop iterators in hx711_read Piyush Patle
2026-05-18 22:02 ` [PATCH v9 10/11] iio: adc: hx711: pass iio_chan_spec to hx711_reset_read Piyush Patle
2026-05-18 22:41 ` sashiko-bot
2026-05-18 22:02 ` [PATCH v9 11/11] iio: adc: hx711: add support for HX710B Piyush Patle
2026-05-18 22:39 ` sashiko-bot
2026-05-20 10:31 ` Jonathan Cameron
2026-05-24 2:55 ` Piyush Patle
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=20260520112338.22e9dcb0@jic23-huawei \
--to=jic23@kernel.org \
--cc=ak@it-klinger.de \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=piyushpatle228@gmail.com \
--cc=robh@kernel.org \
/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