From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: David Schiller <david.schiller@jku.at>
Cc: <linux-iio@vger.kernel.org>
Subject: Re: Questions about ad5933 driver
Date: Tue, 6 Jun 2023 11:30:13 +0100 [thread overview]
Message-ID: <20230606113013.00000530@Huawei.com> (raw)
In-Reply-To: <3e5653d1aec953e8aba8c00d073cd033a9f7a873.camel@jku.at>
On Tue, 6 Jun 2023 10:46:14 +0200
David Schiller <david.schiller@jku.at> wrote:
> Hi!
>
> I attempted to use the ad5933 impedance analyzer driver in combination
> with libiio.
>
> Trying to enumerate the local devices with "iio_info" leads to an error,
> which I traced down to the naming of the in_voltage_{real,imag}_* sysfs
> scan_elements nodes. The name modifiers "real" and "imag" are not valid
> sysfs symbols, it seems.
> The driver is in the staging directory, so I don't know if it has to
> conform to the general IIO sysfs ABI.
It 'should' but it doesn't which is part of the reason it's still in staging
after all these years.
>
> I worked around this by patching libiio, but I don't know if that's the
> correct approach.
Ideally clean up the driver. If you are willing that would be great, if not
would you be able to test changes made by someone else? You are first person
in years that I know has one! :) I can't remember how far this driver is
from being ready to move out of staging, but I can probably find some time
to do a thorough review of that in next few weeks.
That may require extra ABI definitions possibly including the real and imag
modifiers at which point your patch to libiio would be correct.
Jonathan
>
> What do you think?
>
> Best regards
> David
>
>
next prev parent reply other threads:[~2023-06-06 10:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 8:46 Questions about ad5933 driver David Schiller
2023-06-06 10:30 ` Jonathan Cameron [this message]
2023-06-06 10:51 ` David Schiller
2023-06-07 14:52 ` Jonathan Cameron
2023-06-13 10:37 ` David Schiller
2023-06-17 19:28 ` 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=20230606113013.00000530@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=david.schiller@jku.at \
--cc=linux-iio@vger.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