From: Stefan Wahren <stefan.wahren-eS4NqCHxEME@public.gmane.org>
To: Jonathan Cameron <jic23-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Hartmut Knaack <knaack.h-Mmb7MZpHnFY@public.gmane.org>,
Lars-Peter Clausen <lars-Qo5EllUWu/uELgA04lAiVw@public.gmane.org>,
Peter Meerwald-Stadler
<pmeerw-jW+XmwGofnusTnJN9+BGXg@public.gmane.org>,
Marek Vasut <marex-ynQEQJNshbs@public.gmane.org>
Cc: Ksenija Stanojevic
<ksenija.stanojevic-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Alexandre Belloni
<alexandre.belloni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>,
Fabio Estevam <fabio.estevam-3arQi8VN3Tc@public.gmane.org>,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Torokhov
<dmitry.torokhov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH RFT 4/5] iio: mxs-lradc: disable only mapped channels in mxs_lradc_hw_stop
Date: Mon, 18 Apr 2016 08:36:48 +0200 [thread overview]
Message-ID: <57148080.4010200@i2se.com> (raw)
In-Reply-To: <571369AA.8060106-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Hi Jonathan,
Am 17.04.2016 um 12:47 schrieb Jonathan Cameron:
> On 14/04/16 16:48, Stefan Wahren wrote:
>> Disabling of the touchscreen IRQs is already done in
>> mxs_lradc_disable_ts. There is no need to disable them in
>> mxs_lradc_hw_stop again.
> We could do with a little more documentation in the driver on
> which bits in this register are doing what.
>
> The disable_ts deals with bits 22-24...
> The only other bit I think is ever used by the driver currently is
> 16 (channel 0).
>
> So whilst this change probably works, I'm not sure of the logic behind it.
> As far as I can tell your new clear is fine but in reality you could
> just clear (0x3f << 16) and get the same result (which would be clearer
> to my mind).
>
> The key think here is that we don't support the higher bits on i.mx28
> yet... Which are for button detection and threshold detection.
>
> Have I understood this correctly?
Yes, you are. I've have looked to long in the reference manual instead
of the code.
I've missed the point that virtual channel 6 and 7 are used in case of a
connected touchscreen.
I should use the member buffer_vchans for masking the enable IRQs.
Regards
Stefan
>
> Jonathan
> So we only need to care of the
prev parent reply other threads:[~2016-04-18 6:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1460648909-2657-1-git-send-email-stefan.wahren@i2se.com>
[not found] ` <1460648909-2657-3-git-send-email-stefan.wahren@i2se.com>
[not found] ` <570FF737.4050606@denx.de>
2016-04-17 10:13 ` [PATCH RFT 2/5] iio: mxs-lradc: move TS config into suitable function Jonathan Cameron
2016-04-17 12:19 ` Torokhov
[not found] ` <571361DD.1090001-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2016-04-18 6:26 ` Stefan Wahren
[not found] ` <570FF5AF.7010801@denx.de>
2016-04-18 6:17 ` [PATCH RFT 0/5] iio: mxs-lradc: fix leak and implement PM ops Stefan Wahren
[not found] ` <57147BEF.4070606-eS4NqCHxEME@public.gmane.org>
2016-04-18 10:44 ` Marek Vasut
[not found] ` <1460648909-2657-5-git-send-email-stefan.wahren@i2se.com>
[not found] ` <571369AA.8060106@kernel.org>
[not found] ` <571369AA.8060106-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2016-04-18 6:36 ` Stefan Wahren [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=57148080.4010200@i2se.com \
--to=stefan.wahren-es4nqchxeme@public.gmane.org \
--cc=alexandre.belloni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org \
--cc=dmitry.torokhov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=fabio.estevam-3arQi8VN3Tc@public.gmane.org \
--cc=jic23-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=knaack.h-Mmb7MZpHnFY@public.gmane.org \
--cc=ksenija.stanojevic-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=lars-Qo5EllUWu/uELgA04lAiVw@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=marex-ynQEQJNshbs@public.gmane.org \
--cc=pmeerw-jW+XmwGofnusTnJN9+BGXg@public.gmane.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 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).