From: Martin Kepplinger <martink@posteo.de>
To: Harinath Nampally <harinath922@gmail.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
knaack.h@gmx.de, lars@metafoo.de,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Greg KH <gregkh@linuxfoundation.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
Alison Schofield <amsfield22@gmail.com>
Subject: Re: [PATCH] iio: accel: Bugfix to enbale and allow different events to work parallely.
Date: Tue, 1 Aug 2017 17:50:11 +0200 [thread overview]
Message-ID: <e33e6345-c269-0faf-b98e-dd23fd5b936d@posteo.de> (raw)
In-Reply-To: <a5831c2d-58de-0ce8-67f3-95886063694b@gmail.com>
On 2017-08-01 05:08, Harinath Nampally wrote:
>> Thanks for doing that work. I have had it on my list for a long time
>> and you seem to fix it. Although I'd happily review and possibly test
>> it, unfortunately I can't do so before the week of August 21st.
>>
>> If this might go in quick, nothing will stop me from reviewing either,
>> so, whatever. Thanks again!
> Sure no problem, looking forward to your review comments.
> Actually I am planning to add Orientation events for FXLS8471Q, for
> that is it good idea to overload existing
> IIO_ROT channel type? Also thinking of adding 4 channel modifiers i.e
> portrait up/down, landscape left/right.
> Any suggestions are welcome. Thank you.
>
My only suggestion for adding all these chips' orientation features, is
to start the discussion independently from this driver. Are there other
device series that provide such an orientation interrupt? Is it worth
finding a representation in iio?
Additionally to portait up/down, landscape left/right there is
back/front facing, so you'd have 8 new channel modifiers.
If IIO_ROT is a current userspace "standard" to read for rotating the
screen, it may be worth discussing how to fit this in without new
modifiers. Would you have to make up fake angle values? Anything else
userspace already uses for getting the orientation?
But again, instead of replying here and going off topic, write up a
proposal and post it independently.
next prev parent reply other threads:[~2017-08-01 15:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 11:17 Harinath Nampally
2017-07-31 15:07 ` Martin Kepplinger
[not found] ` <CAAGUq_oD443x-Uq0FAZGQ8ietk9BO_Fjs7MYSNXrnR9Ogb+5tA@mail.gmail.com>
2017-08-01 3:08 ` Harinath Nampally
2017-08-01 15:50 ` Martin Kepplinger [this message]
2017-08-10 3:51 ` Harinath Nampally
2017-08-09 13:37 ` Jonathan Cameron
2017-08-10 3:22 ` Harinath Nampally
2017-08-09 13:58 ` Jonathan Cameron
2017-08-10 3:39 ` Harinath Nampally
2017-08-19 2:08 ` [PATCH] iio: accel: mma8452: code improvements to handle more than one event Harinath Nampally
2017-08-20 10:45 ` Jonathan Cameron
-- strict thread matches above, loose matches on Subject: below --
2017-07-31 1:17 [PATCH] iio: accel: Bugfix to enbale and allow different events to work parallely Harinath Nampally
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=e33e6345-c269-0faf-b98e-dd23fd5b936d@posteo.de \
--to=martink@posteo.de \
--cc=amsfield22@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=harinath922@gmail.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®