From: "Ardelean, Alexandru" <alexandru.Ardelean@analog.com>
To: "Bia, Beniamin" <Beniamin.Bia@analog.com>,
"jic23@kernel.org" <jic23@kernel.org>,
"lars@metafoo.de" <lars@metafoo.de>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"pmeerw@pmeerw.net" <pmeerw@pmeerw.net>,
"knaack.h@gmx.de" <knaack.h@gmx.de>,
"Hennerich, Michael" <Michael.Hennerich@analog.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"biabeniamin@outlook.com" <biabeniamin@outlook.com>
Subject: Re: [PATCH 1/3] iio: amplifiers: hmc425a: Add support for HMC425A step attenuator with gpio interface
Date: Tue, 14 Jan 2020 07:27:08 +0000 [thread overview]
Message-ID: <5925b4f1d47306ec4376a296a1146ff024239044.camel@analog.com> (raw)
In-Reply-To: <5ae63616-5749-da51-b0b2-85cdcaa948f3@metafoo.de>
On Mon, 2020-01-13 at 21:57 +0100, Lars-Peter Clausen wrote:
> [External]
>
> On 1/13/20 3:15 PM, Beniamin Bia wrote:
> [...]
> > +static int hmc425a_write(struct iio_dev *indio_dev, u32 value)
> > +{
> > + struct hmc425a_state *st = iio_priv(indio_dev);
> > + int i, *values;
> > +
> > + values = kmalloc_array(st->chip_info->num_gpios, sizeof(int),
> > + GFP_KERNEL);
> > + if (!values)
> > + return -ENOMEM;
> > +
> > + for (i = 0; i < st->chip_info->num_gpios; i++)
> > + values[i] = (value >> i) & 1;
> > +
> > + gpiod_set_array_value_cansleep(st->gpios->ndescs, st->gpios->desc,
> > + values);
>
> This API got changed a while ago in upstream, see
> https://github.com/analogdevicesinc/linux/commit/b9762bebc6332b40c33e03dea03e30fa12d9e3ed
>
> > + kfree(values);
> > + return 0;
> > +}
> [...]
> > +static int hmc425a_probe(struct platform_device *pdev)
> > +{
> [...]
> > +
> > + platform_set_drvdata(pdev, indio_dev);
>
> drvdata is never accessed, no need to set it.
>
> > + mutex_init(&st->lock);
> > +
> > + indio_dev->dev.parent = &pdev->dev;
> > + indio_dev->name = np->name;
>
> I know ADI likes to do this in its non upstream drivers, but the above
> is not IIO ABI compliant. The name is supposed to identify the type of
> the device, which means for this driver should be static "hmc425a".
> Maybe consider adding a field to the hmc425a_chip_info for this.
We've actually [recently] had a discussion about this internally regarding
the 'indio_dev->name'.
Maybe it's a good time to ask here (now).
A lot of our userspace stuff have been searching IIO devices via the 'name'
field in sysfs, which is the name assigned here.
That creates a problem when you have multiple devices with the same driver.
Which is why, one
So, then some questions would be:
Is a searching for IIO devices [in userspace] based on IIO device-name not
recommended? If not, what would be? Or what would be a better idea?
The ABI reads [hopefully I pulled up the right field]:
What: /sys/bus/iio/devices/iio:deviceX/name
KernelVersion: 2.6.35
Contact: linux-iio@vger.kernel.org
Description:
Description of the physical chip / device for device X.
Typically a part number.
The text in description is a bit open to interpretation, so I can't make an
assessment of what is correct.
In case there was a discussion about this, sorry for repeating some things
now.
>
> > + indio_dev->info = &hmc425a_info;
> > + indio_dev->modes = INDIO_DIRECT_MODE;
> > +
> > + return devm_iio_device_register(&pdev->dev, indio_dev);
> > +}
next prev parent reply other threads:[~2020-01-14 7:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 14:15 Beniamin Bia
2020-01-13 14:15 ` [PATCH 2/3] dt-bindings: iio: amplifiers: Add docs for HMC425A Step Attenuator Beniamin Bia
2020-01-13 20:41 ` Rob Herring
2020-01-13 14:15 ` [PATCH 3/3] MAINTAINERS: add entry for hmc425a driver Beniamin Bia
2020-01-13 20:57 ` [PATCH 1/3] iio: amplifiers: hmc425a: Add support for HMC425A step attenuator with gpio interface Lars-Peter Clausen
2020-01-14 7:27 ` Ardelean, Alexandru [this message]
2020-01-16 18:29 ` Jonathan Cameron
2020-01-14 7:16 ` Ardelean, Alexandru
2020-01-18 13:54 ` Jonathan Cameron
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=5925b4f1d47306ec4376a296a1146ff024239044.camel@analog.com \
--to=alexandru.ardelean@analog.com \
--cc=Beniamin.Bia@analog.com \
--cc=Michael.Hennerich@analog.com \
--cc=biabeniamin@outlook.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@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
all inboxes | Powered by JetHome®