From: Subhajit Ghosh <subhajit.ghosh@vixtechnology.com>
To: Matt Ranostay <matt.ranostay@konsulko.com>
Cc: jic23@kernel.org, lars@metafoo.de, linux-kernel@vger.kernel.org,
linux-iio@vger.kernel.org
Subject: Re: [PATCH] iio: light: apds9960: Fix iio_event_spec structures
Date: Thu, 10 Nov 2022 22:45:49 +0800 [thread overview]
Message-ID: <b6ac2692-3152-dfc4-5388-7986042970f0@vixtechnology.com> (raw)
In-Reply-To: <CAJCx=g=qRd+WaCLOHwnEjg1Myg4Ng=PK0sxcGgEG9VT+VpondA@mail.gmail.com>
>> .type = IIO_EV_TYPE_THRESH,
>> .dir = IIO_EV_DIR_RISING,
>> - .mask_separate = BIT(IIO_EV_INFO_VALUE) |
>> - BIT(IIO_EV_INFO_ENABLE),
>> + .mask_separate = BIT(IIO_EV_INFO_VALUE),
>
> Probably more concise to use the following, and you won't need to add
> an additional item to the structs.
>
> .mask_separate = BIT(IIO_EV_INFO_VALUE),
> .mask_shared_by_type = BIT(IIO_EV_INFO_ENABLE),
>
Above is the first thing I tried.
Current implementation:
root@stm32mp1:~# ls -1 /sys/bus/iio/devices/iio:device0/events/
in_intensity_clear_thresh_falling_en
in_intensity_clear_thresh_falling_value
in_intensity_clear_thresh_rising_en
in_intensity_clear_thresh_rising_value
in_proximity_thresh_falling_en
in_proximity_thresh_falling_value
in_proximity_thresh_rising_en
in_proximity_thresh_rising_value
First method (Which you are suggesting):
.mask_separate = BIT(IIO_EV_INFO_VALUE),
.mask_shared_by_type = BIT(IIO_EV_INFO_ENABLE),
root@stm32mp1:~# ls -1 /sys/bus/iio/devices/iio:device0/events/
in_intensity_clear_thresh_falling_value
in_intensity_clear_thresh_rising_value
in_intensity_thresh_falling_en
in_intensity_thresh_rising_en
The above says all channels with with the type IIO_INTENSITY has
the same enable but we require this particular channel (in_intensity_clear)
regardless of direction to have the same enable.
Using mask_shared_by_dir and mask_shared_by_all does not provide the logical
attribute name.
This patch provides the below:
root@stm32mp1:~# ls -1 /sys/bus/iio/devices/iio:device0/events/
in_intensity_clear_thresh_either_en
in_intensity_clear_thresh_falling_value
in_intensity_clear_thresh_rising_value
in_proximity_thresh_either_en
in_proximity_thresh_falling_value
in_proximity_thresh_rising_value
Verified using iio_event_monitor:
root@stm32mp1:~# ./iio_event_monitor /dev/iio:device0
Event: time: 1647143384807582753, type: proximity, channel: 0, evtype: thresh, direction: either
Regards
Subhajit Ghosh
--
This email is confidential. If you have received this email in error please
notify us immediately by return email and delete this email and any
attachments. Vix accepts no liability for any damage caused by this email
or any attachments due to viruses, interference, interception, corruption
or unauthorised access.
next prev parent reply other threads:[~2022-11-10 14:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 10:12 [PATCH] iio: light: apds9960: Fix iio_event_spec structures Subhajit Ghosh
2022-11-10 13:29 ` Matt Ranostay
2022-11-10 14:45 ` Subhajit Ghosh [this message]
2022-11-11 2:50 ` Matt Ranostay
2022-11-11 7:04 ` Subhajit Ghosh
2022-11-11 11:10 ` Jonathan Cameron
2022-11-11 13:44 ` Subhajit Ghosh
2022-11-12 17:47 ` 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=b6ac2692-3152-dfc4-5388-7986042970f0@vixtechnology.com \
--to=subhajit.ghosh@vixtechnology.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.ranostay@konsulko.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