From: Jonathan Cameron <jic23@kernel.org>
To: "Pandruvada, Srinivas" <srinivas.pandruvada@intel.com>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: Presenting duplicate channels for hid sensor light
Date: Sun, 11 Dec 2016 15:02:36 +0000 [thread overview]
Message-ID: <3d5cb3c8-7931-b98a-185e-a06ce238ed7d@kernel.org> (raw)
In-Reply-To: <1481431720.3681.1.camel@intel.com>
On 11/12/16 04:48, Pandruvada, Srinivas wrote:
> Hi Jonathan,
>
> HID sensor defines common illuminance field which can be output from
> light sensor and color sensors. Currently we are presenting this as
> intensity.
> There are some user spaces expecting only illuminance attribute for
> reading this and getting request to add this.
> The only option I see is to add a duplicate channel.
>
> What do you think?
Hi Srinivas,
This isn't the first time we have run into this sort of issue.
As you say, presenting a duplicate channel is pretty much the only option as we can't break
userspace by removing the old one.
As long as it is actually in the right units etc for illuminance, feel free to add the
channel. If things get 'interesting' for buffered output it may be necessary to
only have one of them available via that interface. Obviously this could be worked around
but it is probably more trouble that it is worth to do so!
Jonathan
>
>
> Thanks,
> SrinivasN�����r��y���b�X��ǧv�^�){.n�+����{��*"��^n�r���z�\x1a��h����&��\x1e�G���h�\x03(�階�ݢj"��\x1a�^[m�����z�ޖ���f���h���~�mml==
>
prev parent reply other threads:[~2016-12-11 15:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-11 4:48 Presenting duplicate channels for hid sensor light Pandruvada, Srinivas
2016-12-11 15:02 ` Jonathan Cameron [this message]
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=3d5cb3c8-7931-b98a-185e-a06ce238ed7d@kernel.org \
--to=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=srinivas.pandruvada@intel.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).