From: Lars-Peter Clausen <lars@metafoo.de>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: Channel-less IIO events
Date: Mon, 24 Oct 2011 17:05:26 +0200 [thread overview]
Message-ID: <4EA57EB6.1020801@metafoo.de> (raw)
In-Reply-To: <4EA57547.3010804@cam.ac.uk>
On 10/24/2011 04:25 PM, Jonathan Cameron wrote:
> On 10/24/11 14:47, Lars-Peter Clausen wrote:
>> Hi,
>>
>> Some chips generate events which don't really map to a channel, but are
>> rather chip global. For example over-temperature events.
> That one is a channel.
>> Do you think this is something we should add support for or should we rather
>> use a dummy channel, which doesn't report any actual values, for propagating
>> the event?
> Yup, have a temp channel for that one. Conceptually you might have two chips
> that are otherwise identical but one has a readable temp channel, the other
> doesn't. Userspace that is interested only in events won't care about
> this difference. Also we want to report what the conditions are as if it were
> a channel we could read. We want to know at what temperature this occurs.
Ok, what should a read on such a channel return, an error value or just an
dummy value?
> [...]
>>
>> My idea for supporting channel-less events is to add a event_mask to struct
>> iio_info, which would be used just like a channels event_mask, but there
>> would be no index for the sysfs attributes and for events we would set the
>> event number to 0xffff.
> Could you give more examples? The temp one to my mind definitely needs a
> channel, perhaps others do not? I am not against in principal but not
> yet certain exactly when this would make sense...
over-temperature is the only one i've seen so far. but other could be
under-current or voltage for the whole chip.
Thanks
- Lars
next prev parent reply other threads:[~2011-10-24 15:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 13:47 Channel-less IIO events Lars-Peter Clausen
2011-10-24 14:25 ` Jonathan Cameron
2011-10-24 15:05 ` Lars-Peter Clausen [this message]
2011-10-24 15:12 ` 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=4EA57EB6.1020801@metafoo.de \
--to=lars@metafoo.de \
--cc=jic23@cam.ac.uk \
--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 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.