From: Jonathan Cameron <jic23@kernel.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Jeremy Cline <jeremy@jcline.org>,
linux-iio@vger.kernel.org
Subject: Re: [PATCH 0/1] iio: core: Copy iio_info.attrs->is_visible into iio_dev_opaque.chan_attr_group.is_visible
Date: Sat, 5 Dec 2020 15:23:44 +0000 [thread overview]
Message-ID: <20201205152344.173e5b96@archlinux> (raw)
In-Reply-To: <2a20cf21-d483-d41e-6ff8-95ae23d230c2@redhat.com>
On Tue, 1 Dec 2020 13:28:47 +0100
Hans de Goede <hdegoede@redhat.com> wrote:
> Hi,
>
> On 11/25/20 9:46 AM, Hans de Goede wrote:
> > Hi All,
> >
> > I wrote this because I was planning on using is_visible in a driver's
> > attribute group myself (1). But in the end it looks like I'm going to
> > do things differently.
> >
> > This is still useful to have though, both for possible future use of
> > is_visible in driver's attribute groups as well as to make the current
> > usage of is_visible in adi-axi-adc.c actually work.
>
> Jonathan, any opinion / remarks on this one?
>
> FWIW since I no longer have plans to use is_visible in an iio-driver
> myself I'm fine with dropping this one, but:
>
> 1. Being able to use is_visible in the attr group of iio-drivers
> seems like a nice thing to have.
>
> 2. There is an existing use of is_visible in adi-axi-adc.c which currently is broken.
I was giving time for Alex, or others to sanity check the need for a fix
(well more specifically wether this one was the right one as clearly
a need!).
Anyhow, all sounds good. Giving timing I'll mark it as one I'll pick up
to go in after rc1 + stable.
I'm not totally sure on the fixes tag. Current patch will have to go on top
of 207c2d27a010 ("iio: core: move channel list & group to private iio device object")
but I don't think it worked before that either as we were still copying attributes
around, just to a different location.
Jonathan
>
> Regards,
>
> Hans
>
>
>
>
> > 1) I was planning to add an (optional) in_accel_location attribute which
> > would contain "lid" or "base" on 360 degree hinges (yoga) style 2-in-1s
> > with 2 accelerometers and where the kernel knows the location. But given
> > the recent discussion to use label-s for this for proximity sensors,
> > I believe that using label-s here makes more sense too. I will write
> > a patch-set for this when I can find / make some time for this.
> >
>
next prev parent reply other threads:[~2020-12-05 18:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 8:46 [PATCH 0/1] iio: core: Copy iio_info.attrs->is_visible into iio_dev_opaque.chan_attr_group.is_visible Hans de Goede
2020-11-25 8:46 ` [PATCH] " Hans de Goede
2020-12-01 14:42 ` Alexandru Ardelean
2020-12-01 12:28 ` [PATCH 0/1] " Hans de Goede
2020-12-05 15:23 ` Jonathan Cameron [this message]
2020-12-05 15:26 ` Hans de Goede
2020-12-05 15:50 ` Alexandru Ardelean
2020-12-13 12:21 ` 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=20201205152344.173e5b96@archlinux \
--to=jic23@kernel.org \
--cc=hdegoede@redhat.com \
--cc=jeremy@jcline.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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