From: Jonathan Cameron <jic23@kernel.org>
To: Shawn Guo <shengchao.guo@oss.qualcomm.com>
Cc: "David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Jishnu Prakash" <jishnu.prakash@oss.qualcomm.com>,
"Daniel Lezcano" <daniel.lezcano@kernel.org>,
"Danilo Krummrich" <dakr@kernel.org>,
"Dan Carpenter" <error27@gmail.com>,
"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
"Bartosz Golaszewski" <brgl@kernel.org>,
"Dhruvin Rajpura" <dhruvin.rajpura@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: adc: qcom-spmi-adc5-gen3: Allocate unique ADC_TM aux device IDs
Date: Sun, 18 Oct 2026 19:21:51 +0100 [thread overview]
Message-ID: <20261018192151.1115a40a@jic23-hlaptop> (raw)
In-Reply-To: <20261008031154.3440632-1-shengchao.guo@oss.qualcomm.com>
On Thu, 8 Oct 2026 11:11:54 +0800
Shawn Guo <shengchao.guo@oss.qualcomm.com> wrote:
> adc5_gen3_add_aux_tm_device() never sets the auxiliary device id, so
> every ADC5 Gen3 instance with at least one qcom,adc-tm channel tries
> to register the same device name. With ADC_TM channels on more than
> one PMIC, the second instance to probe fails:
>
> sysfs: cannot create duplicate filename '/bus/auxiliary/devices/qcom_spmi_adc5_gen3.adc5_tm_gen3.0'
> ...
> auxiliary qcom_spmi_adc5_gen3.adc5_tm_gen3.0: adding auxiliary device failed!: -17
> qcom-spmi-adc5-gen3 c400000.spmi:pmic@8:adc@7200: error -EEXIST: Failed to add auxiliary TM device
>
> The ADC probe then fails as a whole, so that PMIC loses both its IIO
> channels and its thermal zones. This shows up on Nord, which has
> thermistor channels on two PMAU0102 PMICs.
Fixes tag? Just replying to this thread is fine rather than sending
a v2 just for that.
>
> Allocate the id from a driver-wide IDA and release it from the
> auxiliary device release callback. The ADC_TM driver matches on the
> device name only, so the instance number does not affect binding.
>
> Assisted-by: LLM
> Signed-off-by: Shawn Guo <shengchao.guo@oss.qualcomm.com>
> ---
> drivers/iio/adc/qcom-spmi-adc5-gen3.c | 21 ++++++++++++++++++---
> 1 file changed, 18 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/iio/adc/qcom-spmi-adc5-gen3.c b/drivers/iio/adc/qcom-spmi-adc5-gen3.c
> index c68c6c5f6aca..f0b2544c1632 100644
> --- a/drivers/iio/adc/qcom-spmi-adc5-gen3.c
> +++ b/drivers/iio/adc/qcom-spmi-adc5-gen3.c
> @@ -15,6 +15,7 @@
> #include <linux/dev_printk.h>
> #include <linux/err.h>
> #include <linux/export.h>
> +#include <linux/idr.h>
> #include <linux/iio/adc/qcom-adc5-gen3-common.h>
> #include <linux/iio/iio.h>
> #include <linux/interrupt.h>
> @@ -608,7 +609,14 @@ static void adc5_gen3_delete_aux(void *data)
> auxiliary_device_delete(data);
> }
>
> -static void adc5_gen3_aux_device_release(struct device *dev) {}
> +static DEFINE_IDA(adc5_gen3_aux_ida);
> +
> +static void adc5_gen3_aux_device_release(struct device *dev)
> +{
> + struct auxiliary_device *adev = to_auxiliary_dev(dev);
> +
> + ida_free(&adc5_gen3_aux_ida, adev->id);
> +}
>
> static int adc5_gen3_add_aux_tm_device(struct adc5_chip *adc)
> {
> @@ -642,9 +650,16 @@ static int adc5_gen3_add_aux_tm_device(struct adc5_chip *adc)
>
> aux_device->n_tm_channels = adc->n_tm_channels;
>
> - ret = auxiliary_device_init(&aux_device->aux_dev);
> - if (ret)
> + ret = ida_alloc(&adc5_gen3_aux_ida, GFP_KERNEL);
> + if (ret < 0)
> return ret;
> + aux_device->aux_dev.id = ret;
> +
> + ret = auxiliary_device_init(&aux_device->aux_dev);
> + if (ret) {
> + ida_free(&adc5_gen3_aux_ida, aux_device->aux_dev.id);
> + return ret;
> + }
>
> ret = devm_add_action_or_reset(adc->dev, adc5_gen3_uninit_aux,
> &aux_device->aux_dev);
next prev parent reply other threads:[~2026-10-18 18:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 3:11 Shawn Guo
2026-10-08 9:58 ` Bartosz Golaszewski
2026-10-08 12:38 ` Jishnu Prakash
2026-10-18 18:21 ` Jonathan Cameron [this message]
2026-10-19 6:07 ` Shawn Guo
2026-10-19 6:05 ` Shawn Guo
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=20261018192151.1115a40a@jic23-hlaptop \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=brgl@kernel.org \
--cc=dakr@kernel.org \
--cc=daniel.lezcano@kernel.org \
--cc=dhruvin.rajpura@oss.qualcomm.com \
--cc=dlechner@baylibre.com \
--cc=error27@gmail.com \
--cc=jishnu.prakash@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=shengchao.guo@oss.qualcomm.com \
--cc=u.kleine-koenig@baylibre.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®