From: Jonathan Cameron <jic23@kernel.org>
To: Rodrigo Siqueira <rodrigosiqueiramelo@gmail.com>
Cc: Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
John Syne <john3909@gmail.com>,
linux-iio@vger.kernel.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] stagging:iio:meter: Add essential IIO API structures for ADE7854
Date: Sat, 21 Apr 2018 18:18:03 +0100 [thread overview]
Message-ID: <20180421181803.53addc6c@archlinux> (raw)
In-Reply-To: <cover.1524311298.git.rodrigosiqueiramelo@gmail.com>
On Sat, 21 Apr 2018 08:54:45 -0300
Rodrigo Siqueira <rodrigosiqueiramelo@gmail.com> wrote:
> This patchset aims to update ADE7854 by adding the required IIO API
> components. The first patch adds the iio_chan_spec for handling seven
> different registers (all of them with a similar behavior). The second
> patch appends the read_raw function defined by the IIO API. Finally, the
> third patch adds the write_raw function and remove the attributes used
> for handling the seven registers. This patchset has the contribution of
> John Syne, which was responsible for mapping the correct ABI name per
> element in the ADE7854; additionally, John provided codes that helped to
> shape these patches.
>
> Rodrigo Siqueira (3):
> stagging:iio:meter: Add iio_chan_spec
> stagging:iio:meter: Add ade7854_read_raw function
> stagging:iio:meter: Add ade7854_write_raw function
>
> drivers/staging/iio/meter/ade7854.c | 129 ++++++++++++++++++++--------
> 1 file changed, 94 insertions(+), 35 deletions(-)
>
Hi Rodrigo,
Please don't do it like this. The original discussion with John
involved the addition of an extra chunk of core logic so we would have
the ability to specify the channel without using extended_name.
Extended name is not intended to differentiate between channels (it
isn't in general enough to do so - though it works in this little
corner case of sysfs attributes like you have here).
So the plan is to add another field to the iio_chan_spec structure
to allow for the complexity we need. See the long discussions
over how we represent the myriad of channels in here.
If you need some pointers, feel free to ask but it may take
me a little while to put together a full description of what needs
doing.
I'll put a few more direct comments in the individual patches.
Thanks,
Jonathan
next prev parent reply other threads:[~2018-04-21 17:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-21 11:54 [PATCH 0/3] stagging:iio:meter: Add essential IIO API structures for ADE7854 Rodrigo Siqueira
2018-04-21 11:55 ` [PATCH 1/3] stagging:iio:meter: Add iio_chan_spec Rodrigo Siqueira
2018-04-21 17:20 ` Jonathan Cameron
2018-04-21 11:55 ` [PATCH 2/3] stagging:iio:meter: Add ade7854_read_raw function Rodrigo Siqueira
2018-04-21 17:22 ` Jonathan Cameron
2018-04-21 11:56 ` [PATCH 3/3] stagging:iio:meter: Add ade7854_write_raw function Rodrigo Siqueira
2018-04-21 17:26 ` Jonathan Cameron
2018-04-21 18:04 ` John Syne
2018-04-21 18:15 ` John Syne
2018-04-21 18:18 ` John Syne
2018-04-21 17:18 ` Jonathan Cameron [this message]
2018-04-23 23:42 ` [PATCH 0/3] stagging:iio:meter: Add essential IIO API structures for ADE7854 Rodrigo Siqueira
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=20180421181803.53addc6c@archlinux \
--to=jic23@kernel.org \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=john3909@gmail.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=rodrigosiqueiramelo@gmail.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;
as well as URLs for NNTP newsgroup(s).