All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Hans de Goede <hdegoede@redhat.com>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
	Jeremy Cline <jeremy@jcline.org>,
	linux-iio@vger.kernel.org
Subject: [PATCH 0/1] iio: core: Copy iio_info.attrs->is_visible into iio_dev_opaque.chan_attr_group.is_visible
Date: Wed, 25 Nov 2020 09:46:05 +0100	[thread overview]
Message-ID: <20201125084606.11404-1-hdegoede@redhat.com> (raw)

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.

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.


             reply	other threads:[~2020-11-25  8:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-25  8:46 Hans de Goede [this message]
2020-11-25  8:46 ` [PATCH] iio: core: Copy iio_info.attrs->is_visible into iio_dev_opaque.chan_attr_group.is_visible 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
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=20201125084606.11404-1-hdegoede@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=jeremy@jcline.org \
    --cc=jic23@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.